OVD Adapters Stop Working, Bind errors, - Internal is not visible
(Doc ID 1926116.1)
Last updated on NOVEMBER 25, 2019
Applies to:
Oracle Virtual Directory - Version 11.1.1.6.0 and laterInformation in this document applies to any platform.
Symptoms
The adapters stop working with no apparent reason. If a ldapsearch or ldapbind is performed directly against the backend ldap servers then the information is returned with no problems
The following errors can be found in the OVD diag logs:
[2014-09-13T08:58:33.112-04:00] [octetstring] [TRACE:32] [] [com.octetstring.vde.router.RoutingHandler] [tid: xx] [ecid: <ECID>] [SRC_CLASS: com.octetstring.vde.util.VDELogger] [SRC_METHOD: dump] Adapter#<AD_ADAPTER1> - Internal is not visible
[2014-09-13T08:58:33.113-04:00] [octetstring] [TRACE:32] [] [com.octetstring.vde.router.RoutingHandler] [tid: xx] [ecid: <ECID>] [SRC_CLASS: com.octetstring.vde.util.VDELogger] [SRC_METHOD: dump] Adapter#<AD_ADAPTER2> - Internal is not visible
[2014-09-13T08:58:33.113-04:00] [octetstring] [TRACE:32] [] [com.octetstring.vde.router.RoutingHandler] [tid: xx] [ecid: <ECID>] [SRC_CLASS: com.octetstring.vde.util.VDELogger] [SRC_METHOD: dump] Adapter#<AD_ADAPTER3> - Internal is not visible
....
Changes
Change made to adapters
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 |