My Oracle Support Banner

Upgraded From 2.4.0.0 to 2.4.0.1.x. System is Unstable and JDBC Using All Connections (Doc ID 2857651.1)

Last updated on JANUARY 18, 2024

Applies to:

Oracle Utilities Network Management System - Version 2.4.0.1.0 to 2.5.0.2.0 [Release 2.4 to 2.5]
Oracle Network Management for Utilities - DMS - 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.

Goal

Upgrade from 2.4.0.0 to the latest 2.4.0.1.x patch bundle.

System is very unstable as far as performance goes.  Users experiencing slowness and  inability to log in.  This behavior comes and goes. 

The JDBC read/write connection in the Weblogic managed server is also showing that is is using all of the connections that are allocated to it.  Increasing the maximum connections does not resolve the issue. 

An AWR report shows that this SQL statement was taking far too long to run:

update SWMAN_SHEET set NUMBER_OF_STEPS = :1 where SEQ_SHEET_ID = :2

 


Error while user was trying to log in
jar:file:/C:/Users/nms7/AppData/Roaming/.nms/cache/_/oms.corp.dom_7012/nmslib/nms_config.jar!/version.xml
socket: 8899
java.lang.reflect.UndeclaredThrowableException
at com.sun.proxy.$Proxy32.executeSQLQuery(Unknown Source)
at com.splwg.oms.client.sql.corba.DBSConnection.executeQuery(DBSConnection.java:54)
at com.splwg.oms.client.sql.corba.DBSPreparedStatement.executeQuery(DBSPreparedStatement.java:25)
at com.splwg.oms.client.BaseEnvironmentManager.setAppUser(BaseEnvironmentManager.java:938)
at com.splwg.oms.client.login.LoginHelper.loginSucceeded(LoginHelper.java:452)
at com.splwg.oms.client.login.LoginHelper.performLogin(LoginHelper.java:380)
at com.splwg.oms.client.login.EnterSystemCommand.execute(EnterSystemCommand.java:49)
at com.splwg.oms.jbot.JBotCommand.executeCommand(JBotCommand.java:420)
at com.splwg.oms.jbot.CommandProcessor.processCommand(CommandProcessor.java:161)
at com.splwg.oms.jbot.CommandProcessor.access$100(CommandProcessor.java:31)
at com.splwg.oms.jbot.CommandProcessor$ProcessCommandTask.run(CommandProcessor.java:403)
at com.splwg.oms.client.util.ClientThreadPool$ContextRunnable.run(ClientThreadPool.java:177)
at java.awt.event.InvocationEvent.dispatch(Unknown Source)
 

Root cause is that there is an audit process for model edits and switching sheets that occurs on login.  This is triggered by checking the SWMAN_PATCHES.patch_time value.   This date had not changed since the initial go-live of the system, was resulting in a audit of every model edit against every active switch sheet step to evaluate whether the model edit impacts the step.   This is possibly a bug that the date had not been updated after previous audit checks.

Solution

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