My Oracle Support Banner

Model Build Patches are Failing With Errors Refering to Jumpers That Do Not Exist (Doc ID 2884801.1)

Last updated on JULY 22, 2022

Applies to:

Oracle Network Management for Utilities - DMS - Version 2.4.0.1.0 to 2.5.0.2.0 [Release 2.4 to 2.5]
Oracle Utilities Network Management System - Version 2.4.0.1.0 to 2.5.0.2.0 [Release 2.4 to 2.5]
Information in this document applies to any platform.

Symptoms

On : 2.4.0.1.0 version, Data Model

After services were up for a month, model build patches started to fail and they were referencing objects with jumper aliases.
Checking the database confirmed that those jumper objects did not exist in the model.
Restarting MBService fixed the issue.


If a model edit fails, it should not be kept in memory.

The issue can be reproduced at will with the following steps:

  1. Run these commands:
    Action any.MBService relog
    Action any.MBService dump
    grep MEMManager ~/logs/MBS*
  2. Make note of how many model edit entries it indicates
  3. Launch Web Workspace, sign in and get authority over all zones
  4. Place an Inline Jumper on a conductor
  5. Remove the Inline Jumper
  6. Run these commands:
    Action any.MBService dump
    grep MEMManager ~/logs/MBS* | tail -1
  7. The number of model edits stored in memory will have increased by one, even though it was removed.
  8. Restart MBService
    Action any.MBService restart
  9. After it has finished initializing, run these commands:
    Action any.MBService dump
    grep MEMManager ~/logs/MBS*
  10. The number of model edits stored in memory will match the number in step 1

 

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
 Workaround
 Fix Description
 Migration
References


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