MBService Fails to Detect Dependency of Nested Jumpers
Last updated on FEBRUARY 23, 2018
Applies to:Oracle Utilities Network Management System - Version 184.108.40.206 to 220.127.116.11.0 [Release 1.12 to 2.3]
Oracle Network Management for Utilities - DMS - Version 18.104.22.168 to 22.214.171.124.0 [Release 1.12 to 2.3]
Information in this document applies to any platform.
On : 126.96.36.199 version, Web Workspace
MBService can fail to detect dependencies of nested model edits, this can result in orphan conductors appearing in the map
The issue can be reproduced at will on an OPAL model with the following steps:
1. Place an inline jumper.
2. Place an inline jumper on BOTH of the new conductors created by the first jumper.
3. Select the first jumper and use the control tool to remove it.
The jumper gets removed.
4. Remove the both remaining jumpers.
The conductor segments from the original jumper are visible again.
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