Oracle Clients Cannot Resolve Service Names in AD After OracleContext is Created
(Doc ID 361528.1)
Last updated on JANUARY 20, 2025
Applies to:
Oracle Net Services - Version 9.2.0.1.0 to 10.2.0.1.0 [Release 9.2 to 10.2]Oracle Database - Enterprise Edition - Version 19.12.2.0.0 and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Gen 2 Exadata Cloud at Customer - Version N/A and later
Oracle Cloud Infrastructure - Exadata Cloud Service - Version N/A and later
Microsoft Windows (32-bit)
Microsoft Windows (32-bit)
Symptoms
After successfully creating an OracleContext and adding a Net Service name via NetMgr, client applications still cannot use AD to resolve their service name.
ORA-12154 : TNS could not resolve the connect identifier specified
A tnsping might yield: TNS-03505: Failed to resolve name
An anonymous search using ldapsearch against the OracleContext fails, but when the search is performed with credentials it retrieves the data.
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 |
| Cause |
| Solution |