Troubleshooting Oracle Internet Directory

20-40 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management 1. Route the LDAP traffic from OIDHOST1 and OVDHOST1 to OIDHOST2 and OVDHOST2. 2. Bring down the Oracle Internet Directory or Oracle Virtual Directory server on the host on which you are applying the patch OIDHOST1 or OVDHOST1. 3. Apply the Oracle Internet Directory patch or Oracle Virtual Directory patch on the host. 4. Start the Oracle Internet Directory or Oracle Virtual Directory server on the host. 5. Test the patch. 6. Route the traffic to OIDHOST1 or OVDHOST1 again. 7. Verify the applications are working properly. 8. Route the LDAP traffic on OIDHOST2 and OVDHOST2 to OIDHOST1 and OVDHOST1. 9. Bring down the Oracle Internet Directory or Oracle Virtual Directory server on the host on which you are applying the patch OIDHOST2 or OVDHOST2. 10. Apply the Oracle Internet Directory patch or Oracle Virtual Directory patch on the host. 11. Start the Oracle Internet Directory or Oracle Virtual Directory server on the host. 12. Test the patch. 13. Route the traffic to both hosts on which the patch has been applied OIDHOST1 and OIDHOST2, or OVDHOST1 and OVDHOST2.

20.6 Troubleshooting

This section describes how to troubleshoot common issues that can arise with the Identity Management enterprise deployment described in this manual. This section contains the following topics: ■ Section 20.6.1, Troubleshooting Oracle Internet Directory ■ Section 20.6.2, Troubleshooting Oracle Virtual Directory ■ Section 20.6.3, Troubleshooting Oracle Directory Integration Platform ■ Section 20.6.4, Troubleshooting Oracle Directory Services Manager ■ Section 20.6.5, Troubleshooting Oracle Access Manager 11g ■ Section 20.6.6, Troubleshooting Oracle Identity Manager ■ Section 20.6.7, Troubleshooting Oracle Identity Federation

20.6.1 Troubleshooting Oracle Internet Directory

This section describes some common problems that can arise with Oracle Internet Directory and the actions you can take to resolve the problem. Problem The Oracle Internet Directory server is not responsive. When the load balancing router is configured to send an ICMP message to the LDAP SSL port for monitoring, the Oracle Internet Directory server starting SSL negotiation sometimes hangs, and thus it is required that the load balancing router not use ICMP messages for monitoring the LDAP SSL port. Managing Enterprise Deployments 20-41 Solution Use an alternative such as TCP or the LDAP protocol itself. Also, monitoring the LDAP non-SSL port is sufficient to detect LDAP availability. Problem The SSOLDAP Application connection is lost to Oracle Internet Directory server Solution Verify the load balancing router timeout and SSOApplication timeout configuration parameter. The SSOLDAP application timeout value should be less than LBR IDLE time out. Problem The LDAP application is receiving LDAP Error 53 DSA Unwilling to Perform. When one of the database nodes goes down during the middle of the LDAP transaction, the Oracle Internet Directory server sends error 53 to the LDAP client Solution To see why the Oracle Internet Directory database node went down, see the Oracle Internet Directory logs in this location: ORACLE_INSTANCE diagnosticslogsOIDoidldapd01s.log Problem Issues involving TNSNAMES.ORA, TAF configuration, and related issues. Solution See the Oracle Database High Availability Overview manual.

20.6.2 Troubleshooting Oracle Virtual Directory