LDAP Naming Permissions Issue: Resolution Fails with ORA-12154 TNS: Failed to resolve service name
(Doc ID 559286.1)
Last updated on FEBRUARY 19, 2019
Applies to:Oracle Net Services - Version 10.2.0.1 to 18.104.22.168 [Release 10.2 to 12.2]
Information in this document applies to any platform.
This problem would most likely occur on a Unix client as it arises when the client has inadequate permissions on the $ORACLE_HOME.
10g LDAP naming resolution fails with ORA-12154, when the operating system owner making the connection is not the owner of the Oracle Software. When using operating system user who does own the oracle software, then the same net service name resolution works fine.
TNSping can fail with TNS-3505: Failed to resolve name
Oracle Net client trace shows the failure OID discovery function failed with code 89
nnflobc: initialized new connection ctx 111280
nnflgetnlpactx: NLPA context successfuly initialized
nnfloiddisco: OID discovery function failed with code 89
nnflgcp: can't get config parameter DIRECTORY_SERVER_TYPE
nnflobc: directory server type is 4096
nnflgcp: can't get config parameter PRIMSVR_CONNRETRY_EXPTIME
nnflgcp: can't get config parameter DEFAULT_ADMIN_CONTEXT
nnflgcp: can't get config parameter DIRECTORY_CONNECT_METHOD
nnflgcp: can't get config parameter DIRECTORY_SERVERS
nnflpsl: can't get server'
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