Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Database Performance Analyzer (DPA) > DPA - Knowledgebase Articles > Connect to Oracle using name resolution

Connect to Oracle using name resolution

Table of contents
No headers

For DPA to connect to Oracle instances by name (tnsnames or LDAP), the following Oracle Network configuration (.ora) files are required (see file descriptions below):

    tnsnames.ora - required for tnsname resolution
    ldap.ora - required for LDAP name resolution
    sqlnet.ora - required if default domains are used
   
Note: DPA does not support Oracle Names (onames).

The files must be created in or copied to the following location:

    <ignite_install_directory>/iwc/tomcat/ignite_config/oracle_config

 

If the DPA server is running on a UNIX  or Linux computer, you can use symbolic links in place of the actual files.
   
The files may be added and modified while the DPA server is running. The new properties are used on subsequent connection attempts.

Property names in sqlnet.ora and ldap.ora must be upper case or lower case. Mixed case property names are not supported.

DPA supports changing the location of these files to a directory outside of the DPA installation. To use a different directory:

  1. Edit <ignite_install_directory>/iwc/tomcat/ignite_config/idc/system.properties</ignite_install_directory>
  2. Set the property com.confio.ignite.oracleConfigurationDirectory to the path of the desired file directory. Directories in the path must be delimited by a forward slash.  For example:
com.confio.ignite.oracleConfigurationDirectory=c:/mytnsnamesdir

Notes:

  • If the property does not exist in system.properties, you must add it. 
  • This directory must exist and be accessible by the DPA server process.
  • The DPA server must be restarted to recognize this change. 

 

sqlnet.ora
Two properties from this file are used by DPA. This file is not required unless a default domain is used for name resolution.

NAMES.DIRECTORY_PATH
Used to determine if name resolution should first be attempted using LDAP or TNSNAMES. The default is TNSNAMES. If the primary name resolution is LDAP, SolarWinds recommeneds that you add the sqlnet.ora file to the directory and set this property to (LDAP).

NAMES.DEFAULT_DOMAIN
If this property is set, all unqualified tnsnames are suffixed with this domain.

tnsnames.ora
This file is used to resolve a name as a tnsname alias. Included files (ifile property) are not supported. If NAMES.DEFAULT_DOMAIN property is specified in the sqlnet.ora file, all names are suffixed with this value before the name is resolved.

ldap.ora
This file is used to determine the LDAP server(s) and default admin context that should be used to resolve names through a directory service, such as OID.

At a minimum, the DIRECTORY_SERVERS property must be defined in this file.

This file must be present for DPA to resolve LDAP names.

Last modified

Tags

Classifications

Public