IBM InfoSphere Federation Server, Version 10.5

Preparing the federated server to access Microsoft SQL Server data sources (Linux, UNIX)

On federated servers that run Linux or UNIX, the federated server must be able to access Microsoft SQL Server data sources. To prepare the federated server, you must verify the settings in the odbc.ini file, create symbolic links, and test the connection to Microsoft SQL Server data sources.

Procedure

Verify that the odbc.ini file is updated on the federated server. If the odbc.ini file does not exist on the federated server, you can create it in a text editor. Consult the documentation from the ODBC client vendor for information about the odbc.ini file.
Remember: Place the odbc.ini file or a copy of this file in the home directory of the DB2® instance owner to ensure that it can be accessed if the instance owner is not the root user.
Verify that the path to the odbc.ini is in the ODBCINI environment variable.
From an operating system command prompt, issue the following command:
```
export ODBCINI=$HOME/.odbc.ini
```

Create the appropriate symbolic links:

Federated server operating system Step

Federated server operating system	Step
Linux	Create the following symbolic links depending on the ODBC driver you install, for example: `ln -s $DJX_ODBC_LIBRARY_PATH/.. /locale/usr/local/locale ln -s $DJX_ODBC_LIBRARY_PATH/libodbcinst.so/ usr/lib/libodbcinst.so` Examples For the IBM Branded DataDirect ODBC driver: You create symbolic links for version 5.3, as follows: `ln -s $DJX_ODBC_LIBRARY_PATH/ libVMicu23.so /usr/lib/libVMicu23.so` You create the symbolic link for version 5.3, as follows: `ln -s $DJX_ODBC_LIBRARY_PATH/ libVMicu23.so /usr/lib/libVMicu23.so` For the DataDirect Technologies Connect for ODBC driver: You can create the symbolic link for version 6.0, as follows: `ln -s $DJX_ODBC_LIBRARY_PATH/libivicu24.so/ usr/lib/libivicu24.so` You create the symbolic link for version 7.1, as follows: `ln -s $DJX_ODBC_LIBRARY_PATH/libivicu27.so/ usr/lib/libivicu27.so` If you do not create the symbolic link, the CREATE WRAPPER MSSQLODBC3 statement might fail with the following error message: `SQL10013N The specified library name could not be loaded.`
Solaris	Create the following symbolic link: `ln -s $DJX_ODBC_LIBRARY_PATH/../ locale $HOME/sqllib/locale` where $HOME is the home directory of the DB2 instance owner.

Linux

Create the following symbolic links depending on the ODBC driver you install, for example:

ln -s $DJX_ODBC_LIBRARY_PATH/..
/locale/usr/local/locale 

ln -s 
$DJX_ODBC_LIBRARY_PATH/libodbcinst.so/
usr/lib/libodbcinst.so

Examples

For the IBM Branded DataDirect ODBC driver:
- You create symbolic links for version 5.3, as follows:
```
ln -s $DJX_ODBC_LIBRARY_PATH/
libVMicu23.so /usr/lib/libVMicu23.so
```
- You create the symbolic link for version 5.3, as follows:
```
ln -s $DJX_ODBC_LIBRARY_PATH/
libVMicu23.so /usr/lib/libVMicu23.so
```
For the DataDirect Technologies Connect for ODBC driver:
- You can create the symbolic link for version 6.0, as follows:
```
ln -s 
$DJX_ODBC_LIBRARY_PATH/libivicu24.so/
usr/lib/libivicu24.so
```
- You create the symbolic link for version 7.1, as follows:
```
ln -s 
$DJX_ODBC_LIBRARY_PATH/libivicu27.so/
usr/lib/libivicu27.so
```
If you do not create the symbolic link, the CREATE WRAPPER MSSQLODBC3 statement might fail with the following error message:
```
SQL10013N The specified library 
name could not be loaded.
```

Solaris

Create the following symbolic link:

ln -s $DJX_ODBC_LIBRARY_PATH/../
locale $HOME/sqllib/locale

where $HOME is the home directory of the DB2 instance owner.

The following table lists the name of library for each ODBC driver version.

Table 1. ODBC driver versions
ODBC driver version	Library name
5.3	libodbcinst.so libVMicu23.so
6.0	libodbcinst.so libVMicu24.so
7.1	libodbcinst.so libVMicu27.so

Install the ODBC drivers. For information on how to download and install the ODBC drivers, see Installing ODBC drivers.

What to do next

After you complete this task, you can set the environment variables.

Feedback