OVD Adapters to AD with MS DNS Auto Discovery Fail at OVD Server Restart. Log Errors: OVD-60008 / Error in instantiating <DN>. [[ java.lang.NullPointerException / OVD-60231 / Cannot load adapters. [[ java.lang.NullPointerException
(Doc ID 2623431.1)
Last updated on JANUARY 13, 2020
Applies to:Oracle Virtual Directory - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
Oracle Virtual Directory (OVD) 11g 220.127.116.11.0 with several Microsoft (MS) Active Directory (AD) adapters configured with Microsoft DNS auto-discovery.
[Note: OVD is also configured for TLS as per: OVD 11g and libOVD Support For TLSv1.0, TLSv1.1, TLSv1.2 (Doc ID 2043227.1).]
OVD adapter binding is inconsistent on service restart.
During OVD server startup, the configured adapters are failing to initialize in an inconsistent manner.
The primary symptom is that the 'Data Browser' > 'Client View' is intermittently showing a different set of available adapters, with some adapters appearing after some OVD server restarts yet missing after other restarts, noting that all adapters do not successfully start together.
Also, OVD takes a very long time to stop, and subsequent startups do sometimes fail with OVD-60216 requiring another stop and start cycle.
OVD log errors:
After further testing, found that disabling the Microsoft DNS Auto Discovery option completely, i.e. set it from "Microsoft" to "No", resolves the problem. However, the auto discovery is essential to allowing OVD to identify multiple hosts when connecting.
The same scenario works on a smaller scale environment with fewer adapters.
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