My Oracle Support Banner

Time Zone Name Invalid After Upgrading From MDM 2.1.0 SP3 To MDM 2.2.0 SP2 (Doc ID 2444237.1)

Last updated on MARCH 15, 2019

Applies to:

Oracle Utilities Meter Data Management - Version 2.2.0.2.0 and later
Information in this document applies to any platform.

Goal

On : 2.2.0.2.0 version, System Wide

Time Zone Name invalid after upgrading from MDM 2.1.0 SP3 to MDM 2.2.0 SP2

In 2.1, a time zone "JST" was configured. The 'Time Zone Name' used is 'Japan'. During MDM 2.1.0 SP3, 'Japan' time zone name exists, and we are able to use this as Time Zone Name for our JST Time Zone. However, after upgrading to MDM 2.2.0 SP2, the Time Zone Name 'Japan' is not valid anymore.

The timezone class used by MDM 2.1 and 2.2 seems be different. In 2.1, we use the standard Timezone class from JDK. But in 2.2, we seems use the timezone class from JODA. I checked the timezone list of JODA, it seems be much shorter than standard JDK's timezone list. Please share to Prod Dev to confirm whether this is the cause of issue and what's the resolution if our project want to keep the original timezone code/name.
 

Solution

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
Goal
Solution
References


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