Troubleshooting Oracle Internet Directory High Availability

8-44 Oracle Fusion Middleware High Availability Guide ldapbind -h oid_host -p 389 -D cn=orcladmin -q ldapbind -h oid_host -p 389 -D cn=orcladmin -q ldapbind -h oid.mycompany.com -p 389 -D cn=orcladmin -q 4. Use the srvctl command to start the database instance: srvctl start instance -d db_unique_name -i inst_name_list

8.3.6 Troubleshooting Oracle Internet Directory High Availability

This section provides information that can help you troubleshoot Oracle Internet Directory high availability issues: ■ Log files for Oracle Internet Directory are found in the following directory: ORACLE_INSTANCE diagnosticslogOID ■ The order in which log files should be examined when troubleshooting is: 1. oidmon-xxx.log 2. oidldapd01-xxxx.log 3. oidldapd01s-xxxx.log ■ This section shows some of the error messages that may be related to high availability, and their meaning: Error : ORA-3112, ORA-3113 errors in the log file Cause : one of the database node is down, OID connects again to surviving node. Action : See why database node went down or Oracle process got killed Error : Failing Over...Please stand by in the log file Cause : OID server received a notification from the Oracle process that one of the database node is down. OID will connect to the surviving node. If the failover is successful you would see this message: Failover ended...resuming services. If the failover was not successful, you would see these errors: a. Tried 10 times, now quitting from failover function... b. Bad Failover Event: Note: See the Configuring Your Environment section of Oracle Fusion Middleware Reference for Oracle Identity Management for a list of the environment variables you must set before using the ldapbind command. Note: The -q option above prompts the user for a password. LDAP tools have been modified to disable the options -w password and -P password when the environment variable LDAP_PASSWORD_ PROMPTONLY is set to TRUE or 1. Use this feature whenever possible. Configuring High Availability for Identity Management Components 8-45 c. Forcing Failover abort as setting of DB parameters for the session failed If high availability event notification is enabled, you would see a message similar to the following: HA Callback Event Thread Id: 8 Event type: 0 HA Source: OCI_HA_INSTANCE Host name: dbhost1 Database name: orcl Instance name: orcl1 Timestamp: 14-MAY-09 03.25.24 PM -07:00 Service name: orcl.us.oracle.com HA status: DOWN - TAF Capable If TAF is disabled, HA status will be shown as DOWN. Action : See why database node went down. Error : Time Difference of at least 250 sec found between node1 and node2. Cause : There is time difference between the two nodes Action : Synchronize the system time. Error : Node= did not respond for configured d times, Failing over... Cause : One of the OID nodes oidmon is not responding. Action : See if the node is alive or OIDMON process is running. For more information about troubleshooting Oracle Internet Directory, see Oracle Fusion Middleware Administrators Guide for Oracle Internet Directory.

8.3.7 Additional Oracle Internet Directory High Availability Issues