Troubleshooting Oracle Directory Integration Platform

20-42 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management 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 the Oracle Virtual 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 Issues involving TNSNAMES.ORA, TAF configuration, and related issues. Solution See the Oracle Database High Availability Overview manual. Problem When you run SSLServerConfig.sh for component OVD, sometime it fails with an error similar to this: Enter password for weblogic: Enter your keystore name [ovdks1.jks]: Checking the existence of ovdks1.jks in the OVD... Failed to configure your SSL server wallet Please check scratchaime1edgfaidmrootCAkeystoresovdks_check.log for more information In the log file, you see an error message like this: Problem invoking WLST - Traceback innermost last: File scratchaime1edgfaidmrootCAkeystoresovdovdssl-check.py, line 8, in ? File iostream, line 182, in cd File iostream, line 1848, in raiseWLSTException WLSTException: Error occured while performing cd : Attribute oracle.as.ovd:type=component.listenersconfig.sslconfig,name=LDAP SSL Endpoint,instance=ovd_inst1,component=ovd1 not found. Use lsa to view the attributes Solution The problem is intermittent.To work around the issue, re-run the script.

20.6.3 Troubleshooting Oracle Directory Integration Platform

This section describes some common problems that can arise with Oracle Directory Integration Platform and the actions you can take to resolve the problem. Problem The instance is not working properly. Managing Enterprise Deployments 20-43 Solution Check the respective log of the instance. For example, if the instance deployed in WLS_ODS1 is not running, then check the WLS_ODS1-diagnostic.log file. Problem Exceptions similar to the following are seen in Managed Server log files running the Oracle Directory Integration Platform application during an Oracle RAC failover: RuntimeException: [2008-11-21T00:11:10.915-08:00] [WLS_ODS] [ERROR] [] [org.quartz.impl.jdbcjobstore.JobStoreTX] [tid: 25] [userId: anonymous] [ecid: 0000Hqy69UiFW7V6u3FCEH199aj0000009,0] [APP: DIP] ClusterManager: Error managing cluster: Failed to obtain DB connection from data source schedulerDS: java.sql.SQLException: Could not retrieve datasource via JNDI url jdbcschedulerDS java.sql.SQLException: Cannot obtain connection: driverURL = jdbc:weblogic:pool:schedulerDS, props = {EmulateTwoPhaseCommit=false, connectionPoolID=schedulerDS, jdbcTxDataSource=true, LoggingLastResource=false, dataSourceName=schedulerDS}.[[ Nested Exception: java.lang.RuntimeException: Failed to setAutoCommit to true for pool connection AuthenticationException while connecting to OID: [2008-11-21T00:12:08.812-08:00] [WLS_ODS] [ERROR] [DIP-10581] [oracle.dip] [tid: 11] [userId: anonymous] [ecid: 0000Hqy6m54FW7V6u3FCEH199apO000000,0] [APP: DIP] DIP was not able to get the context with the given details {0}[[ javax.naming.AuthenticationException: [LDAP: error code 49 - Invalid Credentials] Most of the exceptions are related to the scheduler or LDAP, for example: 1. Could not retrieve datasource via JNDI url jdbcschedulerDS java.sql.SQLException. 2. javax.naming.AuthenticationException: [LDAP: error code 49 - Invalid Credentials] Solution During an Oracle RAC failover, exceptions are seen in the Managed Server log files running the Oracle Directory Integration Platform application. These errors are thrown when the multi data sources configured on the WebLogic Server platform try to verify the health of the Oracle RAC database instances during failover. These are innocuous errors and can be ignored. The Oracle Directory Integration Platform application recovers and begin to operate normally after a lag of one or two minutes. For an Oracle RAC failover, there is no Oracle Directory Integration Platform down time if one instance is running at all times.

20.6.4 Troubleshooting Oracle Directory Services Manager