Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Identity Resolution 10.5
  • All Products

Table of Contents

Search

  1. Preface
  2. Introduction
  3. Installation
  4. Design
  5. Operation

User Guide

User Guide

Back Next

Configuring an ODBC Data Source

Configuring an ODBC Data Source

If you use a database to source data, Data Clustering Engine requires an ODBC API to access the database. During the run time, the database access layer of Database Clustering Engine tries to load an appropriate ODBC driver for each database type. You must create ODBC data sources for each database that you plan to access.

Oracle

Data Clustering Engine uses the following custom ODBC drivers for Oracle instead of the Oracle ODBC driver.
  • On Windows:
    ssaoci9.dll
  • On UNIX:
    libssaoci9.so
When you install Data Clustering Engine, the installer updates the
odbc.ini
 file in the
<Data Clustering Engine Installation Directory>\bin
 directory on Windows or
<Data Clustering Engine Installation Directory>/bin
 directory on UNIX. The
odbc.ini
 file contains the following entries, and you can edit them based on your requirement: 
[<Service Name>]
driver = <ODBC Driver>
server = <Native Database Service>
Configure the following parameters:
Service Name
Service name that Data Clustering Engine uses to refer to the database service.
ODBC Driver
Name of the ODBC driver, which is
ssaoci9.dll
 on Windows and
libssaoci9.so
 on UNIX. The driver name does not include the directory path.
In Data Clustering Engine versions earlier than 9.5.2, you can also use the
ssadriver
 parameter on Windows or the
ssaunixdriver
 parameter on UNIX instead of the
driver
 parameter. The
ssadriver
 and
ssaunixdriver
 parameters are deprecated, and Informatica recommends that you use the
driver
 parameter.
Native Database Service
Name of the database service that you configure in the database.
You can find a sample configuration file,
odbc.ini.ori
, in the following directory:
  • On Windows:
    <Data Clustering Engine Installation Directory>\bin
  • On UNIX:
    <Data Clustering Engine Installation Directory>/bin
When you use
ssaoci9.dll
 driver with Oracle Database Client 10g, the connectivity test might fail on UNIX environments. The
ssaoci9.dll
 driver is linked with
libclntsh.so.9.0
, which is not distributed with Oracle 10g. This issue causes the connectivity test failure. Oracle adds symbolic links to redirect requests for older versions of a library to the current version. Oracle provides this backward compatibility only to the minor versions of its release. To overcome this problem, identity the appropriate Oracle library directory such as
lib
,
lib32
, or
lib64
, and add the symbolic link as follows: 
cd $ORACLE_HOME/lib32
ln -s ./libclntsh.so libclntsh.so.9.0

Microsoft SQL Server

  1. Open the
    odbc.ini
     file that you can find in the
    <Data Clustering Engine Installation Directory>\bin
     directory, and add or update the following entries: 
    [<Service Name>]
DataSourceName = <ODBC DSN>
driver = <ODBC Driver>
server = <Native Database Service>
    Configure the following parameters:
    Service Name
    Service name that Data Clustering Engine uses to refer to the database service.
    ODBC DSN
    Data Source Name. If you do not specify any value, it defaults to the service name.
    ODBC Driver
    Name of the ODBC driver that communicates with the database. The driver name does not include the directory path. You can also use the Microsoft SQL Server Native Client as the ODBC driver.
    Enter one of the following values:
    • sqlsrv32
       for any supported version of Microsoft SQL Server
    • sqlncli
       for Microsoft SQL Server 2005
    • sqlncli10
       for Microsoft SQL Server 2008
    • sqlncli11
       for Microsoft SQL Server 2012
    In Data Clustering Engine versions earlier than 9.5.2, you can also use the
    ssadriver
     parameter instead of the
    driver
     parameter. The
    ssadriver
     parameter is deprecated, and Informatica recommends that you use the
    driver
     parameter.
    Native Database Service
    Name of the database service that you configure in the database.
    You can find a sample configuration file,
    odbc.ini.ori
    , in the
    <Data Clustering Engine Installation Directory>\bin
     directory.
  2. Open the ODBC Data Source Administrator by performing the following tasks:
    1. On the
      Start
       menu, click
      Control Panel
      .
    2. In
      Control Panel
      , click
      Administrative Tools
      .
    3. In
      Administrative Tools
      , click
      Data Sources (ODBC)
      .
  3. On the
    User DNS
     tab or
    Service DNS
     tab, click
    Add
    .
  4. Select
    SQL Server
     or
    SQL Server Native Client
    , and click
    Finish
    .
  5. Follow the instructions in the Wizard, and ensure that you enter the following values:
    • Specify a data source name. Ensure that the data source name matches the data source name that you specify in the
      odbc.ini
       file.
    • Select the Microsoft SQL Server authentication and provide the user credentials that you created.
    • Specify a default database.
    • Ensure that you do not select the
      Use regional settings when outputting currency, numbers, dates and times
       check box.
    If you want to use the Windows authentication to connect to Microsoft SQL Server, set the SSA_DB_WINDOWS_AUTHENTICATION environment variable to Yes.

IBM DB2 UDB

  1. Open the
    odbc.ini
     file that you can find in the
    <Data Clustering Engine Installation Directory>\bin
     directory on Windows or
    <Data Clustering Engine Installation Directory>/bin
     on UNIX, and add or update the following entries: 
    [<Service Name>]
DataSourceName = <ODBC DSN>
driver = <ODBC Driver>
server = <Native Database Service>
    Configure the following parameters:
    Service Name
    Service name that Data Clustering Engine uses to refer to the database service.
    ODBC DSN
    Data Source Name. If you do not specify any value, it defaults to the service name.
    ODBC Driver
    Name of the ODBC driver. The driver name does not include the directory path. Enter one of the following values:
    • db2cli
       on Windows
    • db2
       on UNIX
    • libdb2.a(shr.o)
       on 32-bit AIX environments
    • libdb2.a(shr_64.o)
       on 64-bit AIX environments
    In Data Clustering Engine versions earlier than 9.5.2, you can also use the
    ssadriver
     parameter on Windows or
    ssaunixdriver
     parameter on UNIX instead of the
    driver
     parameter. The
    ssadriver
     and
    ssaunixdriver
     parameters are deprecated, and Informatica recommends that you use the
    driver
     parameter.
    Native Database Service
    Name of the database service that you configure in the database.
    You can find a sample configuration file,
    odbc.ini.ori
    , in the following directory:
    • On Windows:
      <Data Clustering Engine Installation Directory>\bin
    • On UNIX:
      <Data Clustering Engine Installation Directory>/bin
  2. Open the ODBC Data Source Administrator by performing the following tasks:
    1. On the
      Start
       menu, click
      Control Panel
      .
    2. In
      Control Panel
      , click
      Administrative Tools
      .
    3. In
      Administrative Tools
      , click
      Data Sources (ODBC)
      .
  3. On the
    User DNS
     tab or
    Service DNS
     tab, click
    Add
    .
  4. Select
    IBM DB2 ODBC DRIVER
    , and click
    Finish
    .
  5. Follow the instructions in the Wizard, and ensure that you enter the following values:
    • Specify a data source name. Ensure that the data source name matches the data source name that you specify in the
      odbc.ini
       file.
    • Specify a default database.
0 COMMENTS
We’d like to hear from you!