ODBC Administrator is not available on UNIX systems. On AIX, HP-UX, and Solaris, you must manually set environment variables for ODBC, and edit the odbc.ini file to configure the relational data source and OLAP Metadata Catalog, add a new driver or data source, or change the driver or data source. You can use the odbcconfig utility or your favorite editor to edit the odbc.ini file. You can also use odbcconfig to check environment settings. The odbcconfig utility is located in the ishome/bin directory.
To use the odbcconfig utility with DB2 Universal Database, the environment variable INSTHOME must be set to the DB2 Universal Database installation directory name, and exported. Use the odbcconfig utility to verify, add, or delete ODBC connections. See the Integration Server Administration Guide for more information.
To configure a data source in an odbc.ini file, you must add a name and description for the ODBC data source and provide the ODBC driver path, file name, and other driver settings in a separate section that you create for the data source name.
The DB2 OLAP Integration Server installation program installs a sample odbc.ini file in the ISHOME directory. The file contains generic ODBC connection and configuration information for supported ODBC drivers. Use the file as a starting point to map the ODBC drivers that you use to the relational data source and OLAP metadata catalog.
The procedure in this section shows you how to configure a data source by manually editing the odbc.ini file. You can also configure a data source using the odbcconfig utility. See the Integration Server Administration Guide for more information.
If you use a different file than the odbc.ini file, be sure to set the ODBCINI environment variable to the name of the file you use.
To add a data source to an odbc.ini file:
mydata=data source for analysisTo minimize confusion, the name of the data source should match the name of the database in the RDBMS.
[mydata]
Make sure that the ODBC driver file actually exists in the location you specify for the Driver= setting.
For more information about the odbc.ini file and the ODBC driver settings for each RDBMS, see the MERANT DataDirect Connect ODBC Reference in PDF format and the related Readme files in the $ISHOME/odbc/merant40/docs directory. For more information about native ODBC driver settings, refer to the installation documentation for your RDBMS native ODBC drivers.
Here is an example of how you might edit the odbc.ini file to connect to a relational data source, such as db2data on DB2 Universal Database (on AIX), using an IBM DB2 native ODBC driver.
Use the vi $ODBCINI command to edit the odbc.ini file and insert the following statements:
[ODBC Data Sources] db2data=DB2 Source Data on AIX ... [db2data] Driver=/home/db2inst1/sqllib/lib/db2.o Description=DB2 Data Source - AIX, native
The following example illustrates how you might edit the odbc.ini file to connect to a relational data source, such as ifxdata, on Informix Version 9 (on HP-UX), using a MERANT Version 4.0 ODBC driver:
[ODBC Data Sources] ifxdata=Informix 9 Source Data on HP-UX ... [ifxdata] Driver= /home/hyperion/essintegration/odbc/merant40/lib/ARinf17.sl Description=Informix9 ODBC Driver Database=ifxdata HostName=informixhost
The following example illustrates how you might edit the odbc.ini file to connect to a relational data source, oradata, on Oracle Version 8 (on Solaris), using a MERANT Version 4.0 ODBC driver:
[ODBC Data Sources] oradata=Oracle8 Source Data on Solaris ... [oradata] Driver= /home/hyperion/essintegration/odbc/merant40/lib/ARor817.so Description=my oracle source ServerName=OracleSID
ServerName=OracleSID must refer to the name of an Oracle database defined in the tnsnames.ora file. For more information, see the Oracle installation documentation.
Run ivtestlib to verify that the environment is set to run the correct ODBC driver file. For example, run ivtestlib and paste the path and file name that follow Driver= in the odbc.ini file that you have edited.