Setting the SRS rule autoERT to "no" Causes Other Rules to Get Bypassed
(Doc ID 2826391.1)
Last updated on DECEMBER 10, 2021
Applies to:
Oracle Utilities Network Management System - Version 2.4.0.0.0 to 2.5.0.1.0 [Release 2.4 to 2.5]Oracle Network Management for Utilities - DMS - Version 2.4.0.0.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.0.0 version, Web Workspace
ACTUAL BEHAVIOR
---------------
When configuring ERTs, the SRS rule autoERT was set to "no". When that was done, it resulted in the specific settings for these other rules to be ignored:
'minimumERT', 'updateERTsWithCrews', 'recalculateERTsOnRepredictOnly', 'recalculateFromRepredictTime' and 'stormmanUseCrewInfo'
Expected
Setting the autoERT to "no" should not impact the settings for the other rules.
The issue can be reproduced at will with the following steps in the Configuration Assistant
- Configured specific values for the mentioned SRS rules and specifically set the autoERT to "yes"
- Recache JMService
- run Action any.JMService dump rules
- Review the output in the JMService log to verify the rule settings
- Change autoERT to "no"
- Again recache JMService
- run Action any.JMService dump rules
- Review the output in the JMService log to verify the rule settings are now not what is expected.
Changes
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 |
| Changes |
| Cause |
| Solution |
| Fix Description |
| Migration |
| Suggested Test |
| References |