Last updated on MARCH 08, 2017
Applies to:JDBC - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 11.2]
Information in this document applies to any platform.
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
ZONEIDMAP.java, but a null value is returned because there is no mapping for
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms