Oracle Directory Integration and Provisioning Server Administration, 6 of 6

Troubleshooting the Oracle Directory Integration and Provisioning Server

This section contains these topics:

After you start the Oracle directory integration and provisioning server, you can verify that it is running by following these steps:

Verify that the process is running. On Unix, you do this by using the following command:
```
'ps -ef | grep odisrv'
```
On Windows, check to see if the process is shown in the task bar.
If the Oracle directory integration and provisioning server is not running, then review the $ORACLE_HOME/ldap/log/oidmon.log file to see the reason for not bringing up.
If the log file shows any database related errors:
1. Verify ORACLE_SID is set. If ORACLE_SID is not set, then set the value.
2. Verify that the connect string specified in ORACLE_SID is specified in the $ORACLE_HOME/network/admin/tnsnames.ora file.
If the log file shows such errors as invalid configset or server instance numbers, then specify valid values for those arguments.
If the server instance number and the configset number are correct, then look at the file $ORACLE_HOME/ldap/log/odisrv_xx.log where xx is the instance number of the instance started. If it indicates a registration error, then re-register the Oracle directory integration and provisioning server by using odisrvreg.
If no errors are indicated in step 4, then look at the file $ORACLE_HOME/ldap/log/odisrv_jvm_yyy.log, where yyy is the process identifier of the odisrv process that should have come up. Look for the file with the latest timestamp.

After you start the Oracle directory integration and provisioning server, you can verify that it is running by following these steps:

Verify that the process is running. On Unix, you do this by using the following command:
```
'ps -ef | grep odisrv'
```
On Windows, check to see if the process is shown in the task bar.
If it is not running, then look at the file $ORACLE_HOME/ldap/log/odisrv_xx.log where xx is the instance number of the instance started. If this log file indicates a registration error, then re-register the Oracle directory integration and provisioning server by using odisrvreg.
If no errors are indicated in step 2, then look at the file $ORACLE_HOME/ldap/log/odisrv_jvm_yyy.log, where yyy is the process identifier of the odisrv process which should have come up. Look for the file with the latest timestamp