NMS Does not Save Begin Time And Restore Time With Exactly the Same Values
(Doc ID 2812679.1)
Last updated on OCTOBER 06, 2021
Applies to:
Oracle Utilities Network Management System - Version 2.4.0.1.0 to 2.5.0.1.0 [Release 2.4 to 2.5]Oracle Network Management for Utilities - DMS - Version 2.4.0.1.0 to 2.5.0.1.0 [Release 2.4 to 2.5]
Information in this document applies to any platform.
Symptoms
On : 2.4.0.1.0 version, Web Workspace
NMS does not save a Begin Time and Restore Time with exactly the same values
When updating a Begin Time and a Restore Time to the same time, NMS will act like it saves and produces no error message.
If you close out the event and re-open it, you will see the times did not actually update and the post-completion log does not accurately update.
Steps to Reproduce:
1) Open a Completed Event.
2) Update the Begin Time and Save
3) Update the Restored Time and Save
4) Close the Event
5) Reopen the Event and check the times and Post-Completion Log
This is an issue because you can not enter SECONDS in the NMS UI. When you update the times, they are both going through with 00 for seconds. NMS apparently does not accept Began and Restore times with exactly the same HOUR and MINUTE but does not give you an error when you try to save, it just does not save it. There is also no ability to enter the SECONDS field through the UI.
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 |
| Cause |
| Solution |
| Fix Description |
| Migration |
| References |