How to Setup LDAP Client Naming Resolution Failover Timeout Against OID - If OID1 is Busy, Quickly Try OID2.
Last updated on DECEMBER 06, 2016
Applies to:Oracle Internet Directory - Version 10.1.4 and later
Oracle Net Services - Version 10.1.0.2 and later
Information in this document applies to any platform.
The Oracle Internet Directory (OID) servers may be inaccessible due to high CPU load. The server load is not the result of any OID process; but rather, a problem with another program on the server which may cause some of the servers to become unresponsive. This in turn can cause issues accessing OID naming lookups with applications and desktops.
The goal is to determine a way to set up a time limit on accessing OID node1, so that if a result is not returned, the client will then attempt OID node2 instead.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms