Last updated on JULY 31, 2017
Applies to:JDBC - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
When using a TIMESTAMP WITH LOCAL TIMEZONE datatype, the conversion time of summer -> standard time and standard time -> summertime is returning unexpected results when reading the data from the database.
Here is a snippet of the test program to read the data:
When running the test program which writes and reads timestamps for 31.3.13 (day of conversion from winter to summer time) and for the 27.10.13 for each hour, the same value is expected to be displayed.
However, this is not seen and the read returns the following unexpected results:
TIMESTAMPLTZ: ' 2013-03-31 03:01:02. 123', expected: ' 2013-03-31 04:01:02. 123', desc: 'winter-> summer'
TIMESTAMPLTZ: ' 2013-10-27 03:01:02. 123', expected: ' 2013-10-27 02:01:02. 123', desc: 'summer-> winter'
TIMESTAMPLTZ: ' 2013-10-27 04:01:02. 123', expected: ' 2013-10-27 03:01:02. 123', desc: 'summer-> winter'
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms