My Oracle Support Banner

Timezone Atlantic/Jan-Mayen is incorrectly mapped in the JDBC driver's (Doc ID 1433486.1)

Last updated on AUGUST 09, 2023

Applies to:

JDBC - Version to [Release 11.2]
Information in this document applies to any platform.


The timezone Atlantic/Jan-Mayen is mapped to 335 in The
database stores this timezone as 1421. Hence, there is an inconsistency
between the database value and the value mapped in JDBC. Other timezones
like Europe/London for example are stored in the database as 369 and mapped
correctly in JDBC as 369.

Consider a java program which retrieves a timestamp from a database
table column of data type "timezone with timestamp". The column holds a
timestamp with timezone Atlantic/Jan_Mayen. The java program then gets 1421
by performing some calculations on the 12th and 13th bytes of the column
value. It then tries to get the corresponding timezone name from, but a null value is returned because there is no mapping for




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.