My Oracle Support Banner

MSS Failure at End of Year Date Change During Summertime in Southern Hemisphere (Doc ID 2112558.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Oracle Communications MetaSolv Solution - Version 6.2.1 and later
Information in this document applies to any platform.

Symptoms

CURRENT BEHAVIOR

Recurring failure in MSS system during Summer Time at the end of year.

After the day 12/31 the system started to present times out of sync, even with the settings recommended by Oracle for Summertime.

Oracle need to provide the right system parameter during the summer time, so that the problem does not recur every change of year.

EXPECTED BEHAVIOR

Summertime should be presented normally on the Trouble Tickets

STEPS

The issue can be reproduced with the following steps:
1. Having MSS environment configured for a Southern Hemisphere Time Zone changes in Summertime
2. Observe transition from Dec/31 to Jan/01 particularly for Trouble Ticket Open Time and Log Entry time
3. MSS is displaying results which are off by one hour
4. Database shows the stored time in GMT/UTC off by one hour, too.

BUSINESS IMPACT

The issue causes problems and confusion with the flow of activities for the Trouble Tickets.


Changes

 End of year calendar change for the next year.

Cause

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
Symptoms
 CURRENT BEHAVIOR
 EXPECTED BEHAVIOR
 STEPS
 BUSINESS IMPACT
Changes
Cause
Solution
 RESOLUTION
 PRE-REQUISITE
 
RELEASES PRIOR TO MSS 621.B1067
References


This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.