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: 8.1.7.4.0
This problem can occur on any platform.
All connections using LDAP naming resolution from version 8i fail

Symptoms

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

OID server test on port 389 is found

nnflilc: Opening sync conn to test:389 
nnflalc: entry 
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

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms