CA DLP Tuesday Tip: Oracle Service Names

Discussion created by devan05 Employee on Jun 19, 2012
Latest reply on Jun 20, 2012 by Chris_Hackett
CA (DLP) DataMinder r14.1 Configuring DLP to run on Oracle with a Service Name posted by Andrew Devine Snr. support Engineer 19 June 2011

This article focuses on settings relevant to CA (DLP) DataMinder. For specific information relating to configuring Oracle please refer to the vendor specific documentation.

By Default CA (DLP) DataMinder is deployed with Oracle using a SID (Oracle system identifier). A SID is the unique name that identifies your DB instance, however Oracle 8i onwards introduced an alternative connectivity method - Service Names.

A Service name is the TNS (Transparent Network Substrate) alias which allows a database to register itself with listener (in tnsnames.ora) allowing clients to remotely connect to DB Instance via a more friendly name if desired (The SID and Service Name could be the same).

The SID referenced in the deployment of CA (DLP) DataMinder is not hard coded as this allows the DB to relocated if necessary. Please refer to to the earlier article ("CMS Config Changes For A Relocated Database") posted in this community forum for more information.

The CA (DLP) DataMinder database connectivity settings are defined in the MS Windows registry in the following key;

HKLM\SOFTWARE\ComputerAssociates\CA DATAMINDER\Current Version\Properties

Or for earlier versions of CA DLP

HKLM\SOFTWARE\ComputerAssociates\CA DLP\Current Version\Properties

as well as the %wgninstalldir%\system\ file. Below is an example of the file using the SID

db.DataLocation=C:\\Documents and Settings\\All Users\\Application Data\\CA\\CA DATAMINDER\\Data

(Note: Although populated the db.SchemaLocation parameter is ignored for Oracle).

If Oracle is configured to run with a service Name, the registry should be updated to reflect the specifics as well as replacing the SID parameter with the ServiceName parameter in the connection string, example below;


CA Strongly advises that all systems and settings are backed up before undertaking configuration changes and where possible configuration changes are trialed in a test environment before being introdcued into production.