Table of Contents

Search

  1. Preface
  2. Using the Designer
  3. Working with Sources
  4. Working with Flat Files
  5. Working with Targets
  6. Mappings
  7. Mapplets
  8. Mapping Parameters and Variables
  9. Working with User-Defined Functions
  10. Using the Debugger
  11. Viewing Data Lineage
  12. Comparing Objects
  13. Managing Business Components
  14. Creating Cubes and Dimensions
  15. Using the Mapping Wizards
  16. POWERCENTERHELP
  17. Datatype Reference
  18. Configure the Web Browser

Connectivity for Relational Sources

Connectivity for Relational Sources

To import a source definition, you must be able to connect to the source database from the client machine using a properly configured ODBC data source or gateway. You may also require read permission on the database object.
When you create an ODBC data source, you must also specify the driver that the ODBC driver manager sends database calls to. The following table shows the recommended ODBC drivers to use with each database:
Database
ODBC Driver
Requires Database
Client Software
IBM DB2
IBM ODBC driver
Yes
Informix
DataDirect 32-bit closed ODBC driver
No
Microsoft Access
Microsoft Access driver
Yes
Microsoft Excel
Microsoft Excel driver
Yes
Microsoft SQL Server
Microsoft SQL Server ODBC driver
No
Oracle
DataDirect 32-bit closed ODBC driver
No
Sybase ASE
DataDirect 32-bit closed ODBC driver
No
SAP HANA
SAP HANA ODBC driver
Yes
Teradata
Teradata ODBC driver
n/a
When you use a third-party ODBC data source to import a source definition, the Designer might display a message indicating that the third-party driver is not listed in powrmart.ini. The Designer attempts to import source definition metadata using a driver that is shipped with PowerCenter. If the third-party provides a driver to import metadata, configure powrmart.ini.
For example, if Vendor A provided a driver named
vendoraodbc.dll
, you can add an entry under the ODBCDLL heading based on the specified database:

    Vendor A = pmodbc.dll

    Vendor A = extodbc.dll

In the example, the Designer directly interacts with the system ODBC drivers to use the ODBC data source. The system ODBC drivers internally interacts with the third-party ODBC driver,
vendoraodbc.dll
.
The following table lists a sample database dependent entry to use with the PMODBC.ini system ODBC driver:
Database
Entry
MySQL
MYSQL = PMODBC.DLL
PowerExchange
PWX = PMODBC.DLL
dBase 4
dBASE IV = PMODBC.DLL
Visual FoxPro
Visual FoxPro = PMODBC.DLL
Sybase IQ
Adaptive Server IQ = PMODBC.DLL
Lotus Notes
Lotus Notes = PMODBC.DLL


Updated June 25, 2018