Table of Contents

Search

  1. Preface
  2. Installation Overview
  3. Installing MDM Registry Edition
  4. Post-Installation Tasks
  5. Troubleshooting
  6. Upgrading MDM Registry Edition
  7. Uninstalling MDM Registry Edition

Installation and Configuration Guide

Installation and Configuration Guide

Step 3. Define an ODBC Data Source

Step 3. Define an ODBC Data Source

You must define an ODBC data source on the Search Server to connect to Oracle. The
MDM Registry Edition
components access the database through ODBC except the
MDM Registry Edition
Table Loader, which directly loads data into the database. You must create ODBC data sources for each database that you plan to access.
To define an ODBC data source, open the
odbc.ini
file that you can find in the
<MDM Registry Edition Installation Directory>\bin
directory, and add or update the following database entries:
[<Service Name>] driver = <ODBC Driver> server = <Native Database Service> ServerName = <Oracle Database Instance> [connect_attributes = <Keyword1=Value1;Keyword2=Value2;…>] [connect_attr_only = <Text1>]
Configure the following parameters:
Service Name
Service name that
MDM Registry Edition
uses to refer to the database service.
ODBC Driver
Name of the ODBC driver that communicates with the database. The driver name does not include the directory path.
Use one of the following values:
  • On Windows.
    sqora32.dll
  • On UNIX.
    libsqora.so
Native Database Service
Name of the database service that you configure in the database.
Oracle Database Instance
Name of the database instance. The
MDM Registry Edition
installer uses the same value as that of the database service.
Keywords
List of connection string keywords that
MDM Registry Edition
uses to generate a connection string that establishes a connection with the database server.
The format uses the following values:
  • Keywords
    . Optional. Connection string keywords that your ODBC driver supports. If you enable the
    connect_attr_only
    parameter, the specified values override the database source definitions and creates the connection string based only on the specified values. If you do not include the
    connect_attr_only
    parameter,
    MDM Registry Edition
    uses the specified values and the database source definitions to create the connection string.
  • Text1
    . Optional. Indicates whether to use only the connection string keywords or the connection string keywords along with other data source definitions to create the connection string. Enter any text, such as
    Yes
    , to use only the keywords specified in the
    connection_attributes
    parameter to create the connection string. If you want to use the specified keywords with other database source definitions, do not add the
    connect_attr_only
    parameter to the
    odbc.ini
    file.
The following sample configuration indicates to use only the specified connection string keywords to create the connection string:
[o12clx6] ServerName = o12clx6.cbr driver = sqora32.dll server = o12clx6.cbr connect_attributes = UID=James;DSN=Orcl;PWD=secret; connect_attr_only = yes
You can use the following environment variables instead of configuring the connection string keywords in the
odbc.ini
file:
  • SSA_USE_SQLDRIVERCONNECT_ATTRIBUTES
  • SSA_USE_SQLDRIVERCONNECT_ATTRIBUTES_ONLY
For more information about these environment variables, see the
Informatica
MDM Registry Edition
Operations Guide
.
You can find a sample configuration file,
odbc.ini.ori
, in the following directory:
  • On Windows.
    <MDM Registry Edition Installation Directory>\bin
  • On UNIX.
    <MDM Registry Edition Installation Directory>/bin
If you use multiple databases, add the database entries for each database. For example:
[oraclesrc] driver = ssaoci9.dll server = oraclesrc [oracletgt] driver = ssaoci9.dll server = oracletgt