Connections from 8i Using LDAP Naming Resolution Fail with TNS-3505
(Doc ID 550616.1)
Last updated on JANUARY 26, 2008
Applies to:Oracle Net Services - Version: 220.127.116.11.0
This problem can occur on any platform.
All connections using LDAP naming resolution from version 8i fail
Connections from Oracle version 8i (8.1.7.x), using LDAP naming resolution fail with TNS-03505 Failed to resolve name
Using version 9.2 or later version, using same OID server and LDAP entry works fine
Oracle Net Client trace for sqlplus scott/tiger@orcl shows
nnflilc: Opening sync conn to test:389
nnflalc: bind call returns
Query directory for entry orcl in under context dc=uk,dc=oracle,dc=com
nnflrne: Quering the directory for distinguished name cn=orcl,cn=OracleContext,dc=uk,dc=oracle,dc=com
orcl entry is not found
nnfun2a: address for name "orcl" not found
The entry orcl is not a type orclnetdescstring but aliasedobjectname
This can be confirmed by using Oracle Directory Manager (ODM) and navigating to the entry in the context. This will show objectclass: orclNetServiceAlias
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process, and therefore has not been subject to an independent technical review.|