On federated servers that run Linux or UNIX, there are
two methods to access ODBC data source, namely DSN connection mode
and DSN-less connection mode. For DSN connection mode, to prepare
the federated server, you must verify the settings in the odbc.ini file,
and test the connection to ODBC data sources. For DSN-less connection
mode, you can configure the driver path by specifying the "DRIVER=" keyword
in a file named odbcinst.ini. The file odbcinst.ini must exist when
an ODBC wrapper works.
Procedure
- Verify that the odbc.ini(for DSN mode)
and odbcinst.ini (for DSN-less mode, configured
by default for type 1 data sources) files have been updated on the
federated server. If the files do not exist, you can create them in
a text editor. Consult the documentation from the ODBC client vendor
for information about the odbc.ini and odbcinst.ini files.
- Configure the ODBC client.
Consult the documentation from the ODBC client
vendor for instructions on how to configure the ODBC client.
- If the client is RedBrick, verify that the appropriate
symbolic links are created. In the following symbolic links, ODBC_CLIENT_DIR
is the directory where the ODBC client is installed.
| Federated server operating system |
Step |
| Linux |
Create the following symbolic links:ln -s $ODBC_CLIENT_DIR/../locale /usr/local/locale
ln -s $ODBC_CLIENT_DIR/libodbcinst.so /usr/lib/libodbcinst.so
|
| Solaris |
Create the following symbolic link:ln -s $ODBC_CLIENT_DIR/../locale $HOME/sqllib/locale
$HOME
is the home directory of the Db2 instance owner. |
What to do next
After you complete this task, you can register the wrapper.