IBM 51 Troubleshooting Manual page 34

2. Identify the type of constraint, by specifying whether it is an object addition or
3. In the dbschema.sql file, search the ALTER TABLE constraint for the table that
4. If it is a primary key constraint, use the constraint statement and the object you
5. If it is a foreign key constraint, identify the second table and the value that is
IBM Tivoli Directory Server authentication problem determination: If you have
encountered an IBM Tivoli Directory Server authentication problem on the Tivoli
Intelligent Orchestrator server, follow these steps:
1. Check the IBM Tivoli Directory Server for root authentication:
2. Check the IBM Tivoli Directory Server for wasadmin authentication:
3. Check the tioldap user:
4. Check the tioldap authentication:
5. Check the tiointernal user:
6. Check the tioappadmin user:
7. If the encountered error is not related to either tioldap, tiointernal, or
22
Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide
Constraints are listed in the $TIO_HOME/sql/db2/dbschema.sql file as foreign
keys and primary keys.
an object removal.
interests you. Use the table name from the error message and the type of
constraint identified.
are inserting and look in the database to see whether an object with those
values already exists. If it does, change the object you are inserting so that to
make it unique.
involved in the constraint, and then delete the associated object that is
described by the constraint, and then you should be able to delete your object.
ldapsearch -v -h < ldapserver > -p 389 -D "cn=root"
-w <password> -b "dc=ibm,dc=com" cn=wasadmin
If it is a connection problem, refer to "IBM Tivoli Directory Server connection
verification" on page 20.
ldapsearch -v -h < ldapserver > -p 389 -D "cn=wasadmin,dc=ibm,dc=com"
-w <password> -b "dc=ibm,dc=com" cn=wasadmin
If it is an authentication problem, perform the following:
v Verify the user credentials
v Synchronize password using changePassword.sh
v Refer to "IBM Tivoli Directory Server connection verification" on page 20
ldapsearch -v -h < ldapserver > -p 389 -D "cn=wasadmin,dc=ibm,dc=com"
-w <password> -b "dc=ibm,dc=com" cn=tioldap
ldapsearch -v -h < ldapserver > -p 389 -D "cn=tioldap,dc=ibm,dc=com"
-w <password> -b "dc=ibm,dc=com" cn=tioldap
If it is an authentication problem, perform the following:
v Verify the user credentials
v Synchronize password using changePassword.sh
v Refer to "IBM Tivoli Directory Server connection verification" on page 20
ldapsearch -v -h < ldapserver > -p 389 -D "cn=wasadmin,dc=ibm,dc=com"
-w <password> -b "dc=ibm,dc=com" cn=tiointernal
ldapsearch -v -h < ldapserver > -p 389 -D "cn=wasadmin,dc=ibm,dc=com"
-w <password> -b "dc=ibm,dc=com" cn=tioappadmin
tioappadmin, compare the user output against ldap.ldif.