Testing ODBC on UNIX Systems

On UNIX systems, you must manually inspect the configuration files for ODBC or use an data source utility to perform thorough testing. These configuration files include the login scripts that set the environment variables for ODBC and the odbc.ini file. See the documentation for the data source or the ODBC driver.

To inspect the login script files:

Log on to the computer that runs Integration Server as the user who starts the Integration Server software.
In the current home directory, find the main login script file (typically, .profile for Korn Shell and Bourne Shell users, .login for C Shell users) and open it in a text editor.
Note:
The primary login script file may be named differently, depending on the UNIX operating system and the system administrator.
Check the main login script file for the inclusion of the Integration Services script (is.sh or is.csh).
If one of these scripts is included in the main login script, make sure that the inclusion of the script file name follows the syntax for executing a script file within another script, and that the script file is specified with a complete directory path. See Correcting ODBC Problems.
Note:
If you make a change to the login scripts, log out and then log back on to reset the environment variables.
After completing the preceding steps, test the connection by following the steps listed in Testing the Integration Services Console Connection to Essbase Server.
If you cannot make a connection, proceed to Testing the Integration Server Connection to the Data Source.

To inspect the odbc.ini file:

Log on to the computer that runs Integration Server as the user who starts the Integration Server software.
To determine the location of the odbc.ini file, type
```
echo $ODBCINI 
```
If this command does not display a file name and directory location, then you have not included the Integration Services script in the login script for the user. See Correcting Integration Server Problems.
Move to the directory specified by $ODBCINI and open the odbc.ini file with a text editor.
Ensure that you are using the exact file name and directory that you have set. For example, type vi $ODBCINI to display the file name and path of the $ODBCINI environment variable.
Check that the name of the data sources you are using with Integration Services are listed in the ODBC Data Sources section; for example:
```
[ODBC Data Sources]TBC_MD=
Essbase Integration Services sample catalog
TBC=Essbase Integration Services sample database
```

For each data source, check that there is a section starting with the name listed in the ODBC Data Sources section, enclosed in brackets; for example:

For Oracle:

[myoracle]
Driver=
  products/common/ODBC/Merant/6.0/Drivers/ARor819.so
Description=my oracle source
ServerName=mytnsServerName

For IBM DB2:

[TBC_MD]
Driver=
  products/common/ODBC/Merant/6.0/Drivers/ARdb219.so
Description=DB2 database for sample testing

Within the section for each data source, verify that an ODBC driver file is specified.
1. Make sure that the driver file exists by exiting the text editor and attempting to get a directory listing for that file; for example:
```
ls /home/db2inst1/sqllib/lib/db2.so
```
2. If the file is listed, use ivtestlib (32-bit) or ddtestlib (64-bit) to check the actual name and location of the driver, then make the appropriate changes to the odbc.ini file.
  Tip:
  Copy the directory and file name for the driver from the odbc.ini file and paste it into an ls command.
Within the section for each data source, verify that the database name, computer name, and other required information are specified.
See Correcting ODBC Problems.