Bug #63685 MySQL does not recognize timezone offset UTC +14:00
Submitted: 8 Dec 2011 21:38 Modified: 9 Dec 2011 4:58
Reporter: J DR Email Updates:
Status: Verified Impact on me:
Category:MySQL Server: Options Severity:S3 (Non-critical)
Version:5.5.19 OS:Any (Mac OS X, Vista 32-bit Home Premium)
Assigned to: CPU Architecture:Any
Tags: line islands, OFFSET, timezone, UTC

[8 Dec 2011 21:38] J DR
MySQL does not accept the timezone offset UTC+14:00 as a valid value for the time_zone server setting. This is the UTC offset of the Pacific/Kiritimati time zone. The maximum accepted offset currently appears to be +13:00.

I am aware that MySQL can be told about timezone identifiers, but this requires them to be explicitly installed and the user may not have administrative access to the running instance (e.g. on a shared host).

Or, in my case, they may be feeding PHP's date('P') output into a "SET time_zone = 'xxx';" query and encountering an unexpected failure.

How to repeat:
SET time_zone = '+14:00';
> Error #1298 - Unknown or incorrect time zone: '+14:00'

Suggested fix:
Make MySQL aware of the existence of +14:00 UTC time zones.
[9 Dec 2011 4:58] Valeriy Kravchuk
Thank you for the problem report. Verified on Mac OS X also:

mysql> SET time_zone = '+14:00';
ERROR 1298 (HY000): Unknown or incorrect time zone: '+14:00'
mysql> SET time_zone = '+13:00';
Query OK, 0 rows affected (0.01 sec)
[3 Oct 2013 5:26] Salman Ali
Same thing happening on Ubuntu 12.04 LTS. Is there anyone who sorted this out on Ubuntu or any other Linux distro?
[5 Jan 2017 14:54] Michael Devery
No update on this? It's still a problem for me on 5.6.29

SELECT DATE(CONVERT_TZ(NOW(),'+00:00', '+14:00'));

returns null