Getting DAMAGE.DB_ERROR in Web Workspace Client Logs While Saving a Damage Report
(Doc ID 2946103.1)
Last updated on MAY 15, 2023
Applies to:
Oracle Network Management for Utilities - DMS - Version 2.5.0.2.0 and laterOracle Utilities Network Management System - Version 2.5.0.2.0 and later
Information in this document applies to any platform.
Symptoms
On : 2.5.0.2.0 version, Web Workspace
Getting DAMAGE.DB_ERROR in client logs while saving the damage report.
This error appears in the java console :
2023-04-24 04:29:18,352 ERROR com.splwg.oms.jbot.adapter.JBotAdapter: com.splwg.oms.jbot.JBotException: ToolMethodCommand.execute failed: tool = "com.splwg.oms.client.damage.DamageAssessment", method name = "saveDamageReport"
com.splwg.oms.jbot.JBotException: ToolMethodCommand.execute failed: tool = "com.splwg.oms.client.damage.DamageAssessment", method name = "saveDamageReport"
at com.splwg.oms.jbot.command.ToolMethodCommand.execute(ToolMethodCommand.java:61) ~[nms_client.jar:?]
at com.splwg.oms.jbot.JBotCommand.executeCommand(JBotCommand.java:616) ~[nms_client.jar:?]
at com.splwg.oms.jbot.CommandProcessor.processCommand(CommandProcessor.java:163) ~[nms_client.jar:?]
at com.splwg.oms.jbot.CommandProcessor.processPackage(CommandProcessor.java:297) ~[nms_client.jar:?]
at com.splwg.oms.jbot.adapter.JBotAdapter$1.run(JBotAdapter.java:1171) [nms_client.jar:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) [?:1.8.0_251]
at java.util.concurrent.FutureTask.run(Unknown Source) [?:1.8.0_251]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_251]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_251]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_251]
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_251]
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0_251]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0_251]
at java.lang.reflect.Method.invoke(Unknown Source) ~[?:1.8.0_251]
at com.splwg.oms.jbot.command.ToolMethodCommand.execute(ToolMethodCommand.java:56) ~[nms_client.jar:?]
... 9 more
Caused by: com.splwg.oms.framework.exception.OmsClientException: DAMAGE.DB_ERROR
The managed server was reporting a missing sequence:
2023-04-28 06:01:02,144 ERROR DAMAGE:
Internal Exception: java.sql.SQLSyntaxErrorException: ORA-02289: sequence does not exist
Error Code: 2289
Call: SELECT DAMAGE_ASSETS_SEQ.NEXTVAL FROM DUAL
Query: ValueReadQuery(sql="SELECT DAMAGE_ASSETS_SEQ.NEXTVAL FROM DUAL")
org.eclipse.persistence.exceptions.DatabaseException:
Internal Exception: java.sql.SQLSyntaxErrorException: ORA-02289: sequence does not exist
The issue can be reproduced at will on a system missing the DAMAGE_ASSETS_SEQ sequence, with the following steps:
- Fill out a Damage Assessment as normal. Do not save it.
- Enable debug on the managed server
a. In the Weblogic Console, under Environments/Servers, click on NMS_1
b. Click on the Debug tab
c. Expand the Weblogic node
d. Expand the JDBC node
e. Expand the Sql node
f. Click in the box for "DebugJDBCSQL"
g. Press the Enable button near the top of the screen - Immediately after pressing the Enable button, press the Save button in the Damage Assessment window.
- As soon as the error dialog appears, disable the debug
a. In the Weblogic Console, under Environments/Servers, click on NMS_1
b. Click on the Debug tab
c. Expand the Weblogic node
d. Expand the JDBC node
e. Expand the Sql node
f. Click in the box for "DebugJDBCSQL"
g. Press the Disable button near the top of the screen - Check both the client log and the last several managed server log and out files
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 |
References |