RE: Use of OID for name resolution

From: Yong Huang <>
Date: Thu, 22 Oct 2009 14:31:10 -0700 (PDT)
Message-ID: <>

Thanks! Now we can say OID is indeed an overkill.

That "cool" feature was accidentally found by my coworker. She did that for a long time without realizing it's undocumented (actually I didn't look hard in documentation). I verified it from 9iR2 up to 11gR1, using both OID and ONAMES. But since it's undocumented, we probably shouldn't do it in production unless for some quick and dirty work.

Yong Huang

  • On Thu, 10/22/09, Bobak, Mark <> wrote:

Wow! I didn't know you could do that!

Very cool! (Learn something new every day!)

And yes, I just tested, and it works.

[oracle_at_fv360eval201 ~]$ tnsping prd1

TNS Ping Utility for Linux: Version - Production on 22-OCT-2009 16:35:15

Copyright (c) 1997, 2009, Oracle. All rights reserved.

Used parameter files:

Used LDAP adapter to resolve the alias
[oracle_at_fv360eval201 ~]$ cat $ORACLE_HOME/network/admin/ldap.ora
# LDAP.ORA Network Configuration File: /oracle/product/9.2.0/network/admin/ldap.ora # Generated by Oracle configuration tools.

DEFAULT_ADMIN_CONTEXT = "" DIRECTORY_SERVERS= (dtgoid.aa1.pqe:3838) <<========== This is my tnsManager server!

[oracle_at_fv360eval201 ~]$ sqlplus system

SQL*Plus: Release Production on Thu Oct 22 16:35:44 2009

Copyright (c) 1982, 2009, Oracle. All rights reserved.

Enter password:

Connected to:
Oracle Database 11g Enterprise Edition Release - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options

Session altered.

SYSTEM_at_xmldb64> select db_link from dba_db_links;

no rows selected

SYSTEM_at_xmldb64> select * from dual_at_prd1;


So, yes, it works. I guess it makes sense. I don't think Oracle knows the difference between a real OID server and a tnsManager server.


Received on Thu Oct 22 2009 - 16:31:10 CDT

Original text of this message