![]() ![]() So it reads the file tnsnames.ora in the same directory. If LDAP does not have that entry, it uses the second method as listed in NAMES.DIRECTORY_PATH, which is tnsnames. (If the client insists on the secure LDAPS connection, it knows the port to connect to is 636.) Since the example given above has ldap listed first, it reads the ldap.ora file, where the client is instructed to contact Oracle LDAP server (a.k.a OID server) at port 389 for detailed connection info. When the Oracle client needs the detailed connection information from a connect identifier, it first checks the NAMES.DIRECTORY_PATH directive in sqlnet.ora. For example, %oracle_home% could be C:\oracle\product\11.2.0\client_1 or D:\app\oracle\product\12.1.0\db, etc.) (The %string% notation here, taken from an environment variable, points to a Windows folder. ![]() ![]() These two files should be under %oracle_home%\network\admin on Windows ( $ORACLE_HOME/network/admin on Linux or UNIX), unless %tns_admin% (or $TNS_ADMIN) environment variable is set, which points to the directory where the two files are checked first. NAMES.DIRECTORY_PATH=(ldap,tnsnames,ezconnect)ĭIRECTORY_SERVERS=:389:636ĭEFAULT_ADMIN_CONTEXT="dc=example,dc=com" This note is more about using ldap.ora, on the condition that a company-wide Oracle OID i.e. tools or applications) can use the short connect identifier with sqlnet.ora and either tnsnames.ora or ldap.ora. In most cases, the preferred way is to use a short connect identifier.Ī connect identifier is simply an alphanumeric string, such as orcl, prod1. There're two ways to set up a connection to an Oracle database: using a short connect identifier (some call it connection string), and fully specifying the connection details. ![]() Practical Guide to Setting Up Oracle Connection ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |