IBM 51 manual Debug

2005-05-02 10:24:11,123 ERROR [Servlet.Engine.Transports : 2] (Location.java:506) webui.Location:

Error Code = COPCOM093EdcmSqlException

ERROR MESSAGE = COPCOM093E The JDBC driver caused an SQL exception.

1.NESTED EXCEPTION: MESSAGE = [IBM][CLI Driver][DB2/6000] SQL0532N A parent row cannot be deleted

because the relationship "DB2INST1.RECOMMENDATION_REQUEST.SQL050324085328960" restricts the deletion.

SQLSTATE=23504 DETAILS: DB2INST1.RECOMMENDATION_REQUEST(POOL_ID) -> DB2INST1.SPARE_POOL(POOL_ID) IP = 9.3.127.47

THREAD = Servlet.Engine.Transports : 2

STACK TRACE ==> com.thinkdynamics.kanaha.datacentermodel.DataCenter- SystemException: COPCOM093E The JDBC driver caused an SQL exception....

2.Determine whether there is a root cause shortly above the error.

3.Use the logged error or the root cause to research your problem.

4.If a solution is still not found, try matching the error with the following keywords: LTPA, LDAP, authentication, credential, token. If a match is found, go to “IBM Tivoli Directory Server authentication problem determination” on page 22.

5.If no match is found, try matching the error with the following keywords: constraint, DB2, SQL, relationship, row, table. If a match is found, go to “DB2 Universal Database error problem determination” on page 21.

6.If no match is found, check the WebSphere Application Server SystemOut.log file for errors. For more information, go to “WebSphere Application Server error problem determination” on page 23.

Running workflows: The following steps are required for troubleshooting workflows:

1.Try running a noop workflow. If you cannot run the noop workflow, the deployment engine is not running. Restart Tivoli Intelligent Orchestrator.

2.Try running workflows as logical device operations.

vIf you cannot run workflows as logical device operations, check if errors are encountered against a particular object.

vIf no errors are encountered against a particular object, check if errors occur while running the workflow. If such errors are found, go to “Running commands on managed servers.”

vIf no errors occur while running the workflow, search the Tivoli Intelligent Orchestrator Knowledge Base. If the error is documented on the knowledge base, follow the resolution using the knowledge entry.

vIf the error cannot be found on the knowledge base, contact Support. For more information, refer to Appendix B, “Support information,” on page 225.

3.Verify if the faulty workflow is associated with a data center model object.

vIf the workflow is associated with a data center model object, go to“Running commands on managed servers.”

vIf the workflow is not associated with a data center model object, associate it with a data center model object.

Running commands on managed servers: The following steps are required for troubleshooting executing commands on managed servers:

1.Try isolating the error using the log info statements, or set the log level to

DEBUG.

2.Try a simplified command such as uname -a against the managed server.

3.If trying a simplified command works, try running a command using the command line interface:

Chapter 2. Problem determination essentials for Tivoli Intelligent Orchestrator 25