My Oracle Support Banner

MBService Fails to Detect Dependency of Nested Jumpers (Doc ID 2363196.1)

Last updated on MARCH 25, 2019

Applies to:

Oracle Utilities Network Management System - Version 1.12.0.3 to 2.3.0.1.0 [Release 1.12 to 2.3]
Oracle Network Management for Utilities - DMS - Version 1.12.0.3 to 2.3.0.1.0 [Release 1.12 to 2.3]
Information in this document applies to any platform.

Symptoms

On : 1.12.0.3 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.

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
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.