My Oracle Support Banner

NMS Clients Lock Up When Model Build is Halted and Map is Deleted (Doc ID 2948169.1)

Last updated on MAY 15, 2023

Applies to:

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

Symptoms

On : 2.4.0.1.0 version, NMS Infrastructure

During regular operations, model builds were halted (via "Action any.MBService haltbuild").
This is supposed to prevent all non-model-edit builds from being processed.


However, during the course of regular operations, a map was deleted (via the ces_delete_map.ces script), and a device in that map was operated.
This caused the NMS system to lock up.  There were several warnings in the managed server out file:


2023-05-03 08:03:34,476  WARN session.Agent: org.omg.CORBA.TIMEOUT: Response timed out after: '180000' milliseconds.  vmcid: 0x0  minor code: 0 completed: Maybe
org.omg.CORBA.TIMEOUT: Response timed out after: '180000' milliseconds.
...
at com.ces.corba.CES._InterSysStub.getDeviceInfo(_InterSysStub.java:298) ~[nms_common.jar:?]

2023-05-03 08:04:31,243  WARN session.Agent: org.omg.CORBA.TIMEOUT: Response timed out after: '180000' milliseconds.  vmcid: 0x0  minor code: 0 completed: Maybe
org.omg.CORBA.TIMEOUT: Response timed out after: '180000' milliseconds.
...
at com.splwg.oms.ejb.session.InterSysProxy.getDeviceInfo(InterSysProxy.java:131) [cesejb.jar:?]



MBService should not lock any database rows on a halted build.


The issue can be reproduced at will with the following steps on any OPAL system:

In xterm 1:
Action any.MBService haltbuild
ces_delete_map.ces 2022.mad

In xterm 2 simulate a device op:
ISQL.ces

update network_components set number_ops = number_ops+1 where h_cls =126 and
h_idx =1204 and death is null;

The update will hang.

In xterm 3:
Action any.MBService resumebuild

In xterm 1:
the delete map will finish

In xterm 2:
(the update will complete)
rollback;

In xterm 1:
cd ~/data/patches
cp done/2022.mb .
Patch -diff 2022.mb
rm 2022.mb


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
 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.