IBM 51, Troubleshooting Manual

Page: 33 / 248

c. If the
ldapsearch
search returns a
connection error
, start a Telnet session
and try to connect to the IBM Tivoli Directory Server using the port number
389.
d.
If communication can be established with a Telnet session between the IBM
Tivoli Directory Server and Tivoli Intelligent Orchestrator, check the IBM
Tivoli Directory Server administrative password.
4. Search the knowledge bases and, if necessary, contact Support. For more
information, refer to Appendix B, “Support information,” on page 225.
WebSphere Application Server configuration verification: The following steps
are required:
1.
Check the
SystemOut.log
file for errors. For more information, refer to
“Problem determination using SystemOut.log” on page 14.
2. Verify the components in the WebSphere administrative console. If there are
missing components, search the knowledge bases and, if necessary, contact
Support. For more information, refer to Appendix B, “Support information,” on
page 225.
Tivoli Intelligent Orchestrator runtime problem determination
The runtime problem determination process for Tivoli Intelligent Orchestrator can
be divided into component-based problem determination, and task-based problem
determination. Depending on the type of error you are encountering, you must
determine where to start the problem determination process.
v
“Component-based problem determination”
v
“Task-based problem determination” on page 23
Component-based problem determination
This is the base level of problem determination in the Tivoli Intelligent
Orchestrator runtime environment. After you isolate the problem to a specific
component, you can then refer to that component problem determination method,
as follows:
v
“DB2 Universal Database error problem determination”
v “DB2 Universal Database constraint problem determination”
v
“IBM Tivoli Directory Server authentication problem determination” on page 22
v
“WebSphere Application Server error problem determination” on page 23
DB2 Universal Database error problem determination: If you have encountered
a DB2 Universal Databaseerror, follow these steps:
1.
If it is a DB2 Universal Database connection problem, refer to “DB2 Universal
Databaseconfiguration verification” on page 18.
2. If it is a constraint error or exception, refer to “DB2 Universal Database
constraint problem determination.”
3. If the problem you have encountered is neither a connection problem nor a
constraint error or exception, search the knowledge bases for the keyword error
and, if necessary, contact Support. For more information, refer to Appendix B,
“Support information,” on page 225.
DB2 Universal Database constraint problem determination:
If you have
encountered a DB2 Universal Database constraint error or exception, follow these
steps:
1. Using the error message you have received, identify the DB2 Universal
Database table with the constraint.
Chapter 2. Problem determination essentials for Tivoli Intelligent Orchestrator
21