If the library files do not display in the directory path,
you must run a script to link them to the data source client software.
Before you begin
- The data source client software must be installed and configured
on the federated server.
- By default, the scripts issue all messages in English. To issue
messages in another language, one federated database must be configured
to use the code page for the non-English language.
- The required data source environment variables must be set.
Table 1. Data sources, scripts, and required environment variables| Data source |
Script |
Required environment variable |
|---|
| Informix® |
djxlinkInformix |
INFORMIXDIR |
| Sybase |
djxlinkSybase |
SYBASE, SYBASE_OCS |
| Teradata |
djxlinkTeradata |
COPLIB |
Procedure
- Open a UNIX command prompt, and enter
this command:
cd /opt/IBM/db2/V9.7/bin
- From the DB2® command line, enter these commands:
db2 disconnect all
db2stop
- Run the script for each data source that you want to access. See the table above for the names of the scripts.
- If you are installing a multi-partition environment, repeat
Steps 1 - 3 on each database instance.
- For each database instance, go to the directory install_dir/instance,
where install_dir is the DB2 installation
directory, and enter this command:
./db2iupdt instance_name
This
command updates the configuration of the instance and gives it access
to the data sources.
- For each database instance, display the file permissions
on the library files. Verify that the database instance owner has
the permission to read and run the files.
