Troubleshooting OUI / DCM / OC4J JDBC Connection Problems Due To Issues With LDAP Connect Strings
(Doc ID 840038.1)
Last updated on AUGUST 03, 2020
Oracle Fusion Middleware - Version 220.127.116.11.0 to 10.1.4.3.0 [Release AS10g to AS10gR3] Information in this document applies to any platform.
Oracle Application Server 10g Enterprise Edition - Version: 18.104.22.168.0 to 10.1.2.3.0
When performing Application Server 9.0.4 or 10.1.2 installations, some of the configuration assistants are java classes connecting to a database.
These configuration assistants will use JDBC thin to connect to the database and some of them will look up the connect string using LDAP. This is because the Metadata Repository stores the connect string information in an attribute called orclnetdescstring in the cn=<database name>,cn=OracleContext OID entry.
Similarly, when the dcm-daemon process starts up in a database based infrastructure environment the connection to the database is performed using JDBC and the connect string is resolved using LDAP.
The OC4J_SECURITY instance also creates JDBC connections where the connect string is resolved using LDAP, so if we have problems initializing an OC4J_SECURITY connection pool we can use this note to troubleshoot the root cause of the problem.
The purpose of this guide is to troubleshoot the different components involved in these JDBC connections.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!