Application Termination Using Failover OID Server for LDAP Naming
Last updated on JULY 13, 2007
Applies to:Oracle Net Services - Version: 220.127.116.11
This problem can occur on any platform.
OID 10.1.2.1.0 & Database 10.1.4.2.0
Some C applications programs generated by Pro*C lose connection after a few minutes when using a failover LDAP Server during name resolution.
In LDAP.ORA, customer has:
DIRECTORY_SERVERS = (oidsrv1.us.oracle.com:389:636,oidsrv2.us.oracle.com:389:636,oidsrv3.us.oracle.com:389:636)
If the OID Server, 'oidsrv1.us.oracle.com' is available and used for name resolution by the C applications programs, the application works fine.
However, if 'oidsrv1.us.oracle.com' is not available and the next OID 'oidsrv2.us.oracle.com' 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, oidsrv2.us.oracle.com:389.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms