Application Termination Using Failover OID Server for LDAP Naming
(Doc ID 360975.1)
Last updated on JANUARY 21, 2025
Applies to:
Oracle Net Services - Version 9.0.1.0 to 10.2.0.2 [Release 9.0.1 to 10.2]Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Gen 2 Exadata Cloud at Customer - Version N/A and later
Oracle Cloud Infrastructure - Exadata Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 19.16.0.0.0 and later
Information in this document applies to any platform.
Symptoms
Client 9.2.0.4
Database 9.2.0.6
OID 10.1.2.1.0 & Database 10.1.4.2.0
Some C applications programs generated by Pro*C lose their connection after a few minutes when using a failover LDAP Server during name resolution.
In LDAP.ORA, customer has:
DIRECTORY_SERVERS = (<oid_hostname1>:389:636,<oid_hostname2>:389:636,<oid_hostname3>:389:636)
If the OID Server, '<oid_hostname1>' is available and used for name resolution by the C applications programs, the application works fine.
However, if '<oid_hostname1>' is not available and the next OID '<oid_hostname2>' is used for name resolution by the C applications program, the connect string is resolved and the application is able to connect to the database, but after 15min the application is terminated.
The issue was verified setting Oracle Net tracing on the client. The resultant file showed the client connection being closed after 15 minutes after the Net Service Name is request was resolved using the second LDAP server, <oid_hostname2>.com:389.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |