Issue With OTM UTC.GET_UTC_DATE

(Doc ID 741678.1)

Last updated on SEPTEMBER 08, 2016

Applies to:

Oracle Transportation Management - Version: 5.5 to 5.5 - Release: 5.5 to 5.5
Information in this document applies to any platform.
Checked for relevance on 16-Apr-2010

Symptoms

-- Problem Statement:
On OTM 5.0 using 9.2.0.8 Oracle Database & OTM Version 5.5 using Oracle Database Version 10g, Find that the database function UTC.get_local_date does not take into account, the new Daylight Savings Time (DST) change for Australia that is coming into effect on the first Sunday of October 2008

EXPECTED BEHAVIOR
Expect that the OTM database function uses the Oracle JVM or takes the correct DST changes that
comes into effect the first Sunday of October 2008 as against the last Sunday of October that was
the case until 2007

-- Steps To Reproduce:
The issue can be reproduced at will with the following steps:
1. Run the query using the function utc.get_local_date as follows
SELECT utc.get_local_date with the parameters for this function
2. See that the values come up with the DST changes for Australia only for the last sunday of
Australia

-- Business Impact:
The issue has the following business impact:
Due to this issue, users reports using this function will be affected and will show a time that is
off by an hour

Cause

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