How to Setup LDAP Client Naming Resolution Failover Timeout Against OID - If OID1 is Busy, Quickly Try OID2.
(Doc ID 1671486.1)
Last updated on JANUARY 31, 2020
Applies to:
Oracle Net Services - Version 10.1.0.2 to 10.2.0.2.0 [Release 10.1 to 10.2]Oracle Internet Directory - Version 10.1.4 to 10.2.0.1 [Release 10gR3 to 10g]
Information in this document applies to any platform.
Goal
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.
Solution
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
| Goal |
| Solution |
| References |