One of the popular questions from OOW was how to deal with large number of databases and how to manage client connection information that is stored in TNSNAMES.ORA without actually maintaining individual TNSNAMES.ORA files. So I thought I would answer it here as well.
As you probably know TNSNAMES.ORA is the file the database client uses to translate things like:
sqlplus hr@ORCL
into an actual database connection (which means things like knowing what hostname and port to connect to).
In 9i the database added a feature to lookup this information via a proprietary service called the Names Service (though I think OID was also an option). This was deprecated in 10g so that it could be managed via LDAP. And by LDAP that meant OID though you could use Active Directory if you met a proper set of conditions (covered in the docs but I will likely cover it here in the future as well).
10g docs can be found here.
11g docs can be found here.
« This Is Why You Need Adaptive Access Control | Main | Broader Look at Kerberos, Active Directory and Oracle Products »
Simplify Managing TNSNAMES.ORA
Search All Blogs
Google Search
About This Entry
This page contains a single entry from the blog posted on November 21, 2007 10:03 AM.
The previous post in this blog was This Is Why You Need Adaptive Access Control.
The next post in this blog is Broader Look at Kerberos, Active Directory and Oracle Products.
Many more can be found on the main index page or by looking through the archives.
Comments (1)
Hi Mark,
Oracle Names was introduced in Oracle8 Release 8.0.4. It was part of the OCP certification in 8 and 8i. In 9i, however, ldap was the prefered method. ldap was possible with 8i already with either Active Directory, Novell Directory Services or Oracle Internet Directory.
I have used LDAP with Sun Directory Server + Oracle Virtual Directory too. Not sure if it is supported
Posted by Laurent Schneider | November 21, 2007 12:42 PM
Posted on November 21, 2007 12:42