Time Zone change caused Trouble Ticket Events to be logged one hour ahead
Last updated on JANUARY 08, 2017
Applies to:Oracle Communications MetaSolv Solution - Version 6.0.10 to 6.2.1 [Release 6.0.10 to 6.2.0]
Information in this document applies to any platform.
Trouble Ticket events logs.
Issue can hit from any part of the MSS application that keeps log with timestamps in GMT format.
Article reviewed for currency on 1/08/2017.
Even though MSS system was updated with new Time Zone information, and everything seemed to be running properly, there was a problem with the date/time stamp in the Trouble Tickets events log, it indicated events one hour ahead of the "correct time" entered at the MSS client workstation. Example: if an event is created by a user at 13h05, MetaSolv would show 14h05.
Why is the timestamp for TT events recorded as one hour ahead of real time?
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