Model Build Patches are Failing With Errors Refering to Jumpers That Do Not Exist
(Doc ID 2884801.1)
Last updated on JULY 22, 2022
Oracle Network Management for Utilities - DMS - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 2.4 to 2.5] Oracle Utilities Network Management System - Version 126.96.36.199.0 to 188.8.131.52.0 [Release 2.4 to 2.5] Information in this document applies to any platform.
On : 184.108.40.206.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:
Run these commands: Action any.MBService relog Action any.MBService dump grep MEMManager ~/logs/MBS*
Make note of how many model edit entries it indicates
Launch Web Workspace, sign in and get authority over all zones
Place an Inline Jumper on a conductor
Remove the Inline Jumper
Run these commands: Action any.MBService dump grep MEMManager ~/logs/MBS* | tail -1
The number of model edits stored in memory will have increased by one, even though it was removed.
Restart MBService Action any.MBService restart
After it has finished initializing, run these commands: Action any.MBService dump grep MEMManager ~/logs/MBS*
The number of model edits stored in memory will match the number in step 1
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!