Time is Not Correct on Events Coming from a Disaster Recovery System
(Doc ID 2462671.1)
Last updated on JUNE 02, 2024
Applies to:
Oracle Utilities Network Management System - Version 1.12.0.3 and laterOracle Network Management for Utilities - DMS - Version 1.12.0.3 and later
Information in this document applies to any platform.
Goal
What determines the timezone that Workagenda reports times under?
While testing a disaster recovery server that is located in a different time zone, it was observed that the reported event times were not being set correctly.
** Note that for the disaster recovery system, all components are in a different time zone (1 hour earlier in mountain time zone) than where the operator is located.
For example:
User in Central Time zone logs an outage at 1:00 PM (1300) central time.
Using SqlDeveloper or similar to query the database, it is noted that the time for the job shows as 1200.
The user then views the new event in WorkAgenda and sees also that the start time is 1200.
It is expected that since the call was logged at 1300 Central, the start time would be 1300 and not 1200.
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 |