How to Resolve "Problem running command JDBCSaveCommand on datastore" Exception (Doc ID 2130658.1)

Last updated on MAY 16, 2016

Applies to:

Oracle Network Management for Utilities - DMS - Version 1.12.0.3 and later
Oracle Utilities Network Management System - Version 1.12.0.3 and later
Information in this document applies to any platform.

Symptoms

After updating to NMS 1.12.0.3, the custom datastore, DS_ACCT_STRG, fails to write the updated value to the underlying table.

A function to update an accounting string was created using a JDCBDatatStore class. The datastore associated to this does not appear to be functioning properly since the installation of the 1.12.0.3 service pack.

When we go to toggle Storm Mode, the datastore (DS_ACCT_STRG) should populate the current Accounting String, which it is not.
When you change the accounting string in the form and click the Start Storm button, this should then save the value to the table ACCOUNTING_STRING.current_value; this is resulting in a client error popup and logging this error:

2016-04-05 13:07:41,699 [pool-2-thread-14] ERROR com.splwg.oms.jbot.adapter.JDialogAdapter: Problem running command JDBCSaveCommand on datastore DS_ACCT_STRG
com.splwg.oms.jbot.JBotException: Problem running command JDBCSaveCommand on datastore DS_ACCT_STRG
at com.splwg.oms.jbot.command.JDBCSaveCommand.execute(JDBCSaveCommand.java:69)
at com.splwg.oms.jbot.JBotCommand.executeCommand(JBotCommand.java:361)
at com.splwg.oms.jbot.CommandProcessor.processCommand(CommandProcessor.java:162)
at com.splwg.oms.jbot.CommandProcessor.processPackage(CommandProcessor.java:275)
at com.splwg.oms.jbot.adapter.JBotAdapter$1.run(JBotAdapter.java:659)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.IllegalArgumentException
at com.splwg.oms.ejb.session.Session.executeUpdate(Session.java:593)
at com.splwg.oms.ejb.session.Session.executeUpdates(Session.java:521)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)



When the NMS application is started, the datastore (DS_ACCT_STRG) should populate the current Accounting String, which it is not.
When you change the accounting string in the form and click the Save button, this should then save the value to the table ACCOUNTING_STRING.current_value.  Instead it is resulting in a client error popup and log error.


Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms