Customers Getting Moved to Upstream Outage When Nested Outage is Restored
(Doc ID 2881588.1)
Last updated on JULY 06, 2022
Oracle Utilities Network Management System - Version 126.96.36.199.0 to 188.8.131.52.0 [Release 2.4] Information in this document applies to any platform.
On : 184.108.40.206.0 version, Web Workspace
Operators discovered situation where customers in a downstream nested outage were being pulled into an upstream outage even though the downstream customers have an earlier deenergization time. This happens both with and without the fixOverlappingDeviceOutages SRS rule enabled.
It was expected that the nested outage should have a non-zero customer count.
How to Repeat:
1. Set configuration rule 'restoreNestedOutage' to 'no'. 2. Open a device to create an RDO. 3. Open a device upstream from the created RDO. Another RDO is created and nested relationship is created between the created events. 4. Close the outage device in deenergized area (the device opened on step 2).
Expected result: the device closes, both RDO events remain unchanged.
5. Close the other outage device (the device opened on step 3).
Expected result: the device closes, both RDO events are restored and number of affected customers remains unchanged for both events.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!