Choosing a Database Connection Method for Oracle Databases

Oracle Connection Naming Methods

Datical DB connects to Oracle databases through the Oracle JDBC driver using any of the following three Oracle connection naming methods:

Easy Connect Naming (EZCONNECT)
Local Naming (TNSNAMES)
Directory Naming (LDAP)

Easy Connect Naming (EZCONNECT)

The easy connect naming method enables clients to connect to an Oracle database server by using a TCP/IP connect string consisting of a host name and optional port and service name: The easy naming method requires no configuration.

Local Naming (TNSNAMES)

The local naming method stores net service names and their connect descriptors in a localized configuration file named tnsnames.ora.

Directory Naming (LDAP)

The directory naming method stores connect identifiers in a centralized LDAP-compliant directory server to access a database service.

Configuring Oracle Connection Naming Methods in Datical

Connection Method	Summary of DbDef Configuration Requirements
EZCONNECT	Provides a direct connection with the properties configured. Configure the DbDef with the following properties: Connection Type=BASIC Hostname Port SSID or Service Name
TNSNAMES	Provides a connection using a service definition in the tnsnames.ora file. The service definition provides all user and database connection properties. Configure the DbDef as follows TNS Alias - Provide the name of the service definition that you create in the tnsnames.ora file. You also provide the following on the Datical DB host: Environment variables Configuration files
SSL through Oracle Wallet (uses TNSNAMES)	Provides a secure SSL connection using a configuration of your Oracle Wallet feature. Configure the DbDef as follows TNS Alias - Provide the name of the service definition that you create in the tnsnames.ora file. You also provide the following on the Datical DB host: Configuration files Environment variables Notes You cannot use the Datical Accelerator for Oracle in projects or DbDefs where you are using Oracle Wallet for secure connections. (Note that the optional accelerator/compression driver was only available with versions 7.15 or lower. It has been deprecated for versions 7.16 and higher.)
LDAP	Provides a connection through an LDAP service. You set up connection information on the LDAP server, then configure Datical DB to use it. Configure the DbDef as follows TNS Alias - Provide the name of the service definition that you define on the LDAP server. You also provide the following on the Datical DB host: Configuration files Environment variables Notes You cannot use the Datical Accelerator for Oracle in projects or DbDefs where you are using an LDAP connection. (Note that the optional accelerator/compression driver was only available with versions 7.15 or lower. It has been deprecated for versions 7.16 and higher.)

Sharing Connection Configuration Files

A Datical DB project defines a set of DbDefs that make up your release pipeline.

If the connection method for each database is the same, you can share connection files. For example, you can share a set of TNSNAMES connections by placing all of the service definitions in the same tnsnames.ora file.

Have only one tnsnames.ora file placed on the Datical DB host.
Create all service definitions in that tnsnames.ora file.

If the connection method for each database is different, you may need to create configuration directories for each step.

/datical/oracle_ref_tnsnames
/datical/oracle_dev_tnsnames
/datical/oracle_qa_ldap
/datical/oracle_prod_ssl

Testing the Connection

See Testing Oracle Connections