Filter
Top Products
v On Windows, launch Task Manager and check the Processes window.
v On UNIX, run the following command to list all DB2 Universal
Databaseprocesses: db2_local_ps
The
required DB2 Universal Database processes include:
v db2fmd
v db2dasrrm
v db2fmcd
v db2wdog
v db2sysc
v db2ckpwd
v db2gds
v db2syslog
v db2ipccm
v db2tcpcm
v Db2resync
v db2srvlst
v db2agent (LDAP)
v db2fmp
v db2agent (TIOINTER)
v db2loggr (TC)
v db2loggw (TC)
v db2dlock (TC)
v db2pfchr
v db2pclnr
v db2event
4. Check the db2diag.log file for errors. The file is located in the following
directory:
v On Windows: <DB2_Instance_Home_Directory>
v On UNIX: <instance-owner-home>/sqllib/db2dump
5.
Search the knowledge bases and, if necessary, contact Support. For more
information, refer to Appendix B, “Support information,” on page 225.
IBM Tivoli Directory Server verification
The verification requires these steps:
1. Ensure that the IBM Tivoli Directory Server database was successfully created.
Check the ldapcfg.stat file to see the syntax used at the time of the database
creation. The file is located in the following directory:
v On Windows: C:\IBM\ldap\tmp
v On UNIX: /usr/ldap/tmp
You
should see an output similar to the following:
v Windows:
C:\IBM\ldap\bin\ldapcfg -n -a db2inst1 -w password -d LDAP -l
C: -c -f C:\IBM\ldap\tmp\ldapcfg.dat
v UNIX:
/usr/ldap/bin/ldapcfg -n -a db2inst1 -w th1nk -d ldap -l
/home/db2inst1 -c -f /usr/ldap/tmp/ldapcfg.dat
2. Ensure that the IBM Tivoli Directory Server was successfully started:
a. Verify whether the IBM Tivoli Directory Server database was successfully
started, using the ibmdirctl command line utility:
ibmdirctl -D cn=root -w <password> status
The ibmdirctl command is located in the following directory:
v On Windows: C:\IBM\ldap\bin
v On UNIX: /usr/ldap/bin
Note:
To be able to use the ibmdirctl command, the IBM Directory
Administrator service must be running.
Chapter 2. Problem determination essentials for Tivoli Intelligent Orchestrator 11