IBM Support

Installing and configuring the IBM® branded DataDirect® ODBC drivers with InfoSphere® Federation Server Version 9.x, 10.x

Question & Answer


Question

How can I install the IBM branded DataDirect ODBC driver which is included with the installation image of Information Server, the install image of InfoSphere Federation Server, and IBM ftp site ftp://public.dhe.ibm.com?

Cause

The IBM branded DataDirect ODBC driver is included with the install image of Information Server and InfoSphere Federation Server V9.7, V10.1 and V10.5, in addition to the IBM ftp site ftp://public.dhe.ibm.com. This driver is different than the driver included with Federation Server V9.5 (see the link in Related Information section at bottom of this document).

Answer

To get the IBM branded DataDirect ODBC driver package

For non-Windows platforms*, you can get the ODBC drivers package from the install image which is usually named as ODBC_FedServ_vervion_platform.tar.gz.

You can also acquire the ODBC driver package from the official ftp:



ftp://public.dhe.ibm.com/software/db2ii/downloads/odbc_driver/ODBC60-fs-v95-or-above-110531/isv95-or-above-odbc-aix64-fs-110531.tar.gz
ftp://public.dhe.ibm.com/software/db2ii/downloads/odbc_driver/ODBC60-fs-v95-or-above-110531/isv95-or-above-odbc-hpux64-fs-110531.tar.gz
ftp://public.dhe.ibm.com/software/db2ii/downloads/odbc_driver/ODBC60-fs-v95-or-above-110531/isv95-or-above-odbc-linux32-fs-110531.tar.gz
ftp://public.dhe.ibm.com/software/db2ii/downloads/odbc_driver/ODBC60-fs-v95-or-above-110531/isv95-or-above-odbc-linux390-fs-110531.tar.gz
ftp://public.dhe.ibm.com/software/db2ii/downloads/odbc_driver/ODBC60-fs-v95-or-above-110531/isv95-or-above-odbc-linuxamd64-fs-110531.tar.gz
ftp://public.dhe.ibm.com/software/db2ii/downloads/odbc_driver/ODBC60-fs-v95-or-above-110531/isv95-or-above-odbc-solaris64-fs-110531.tar.gz

*NOTE: IBM branded DataDirect ODBC drivers for Federation Server V9.5 on AIX and zLinux/Linux390 platforms from the install image are not available now. The only way that you can get the driver is from the ftp site shown above.



To install the driver using GUI mode

1. Go to an operating system command prompt and enter:

gunzip file_name.tar.gz

2. Enter:

tar -xvf file_name.tar

3. Enter:

./odbcsetup.bin

4. Follow the instructions to complete the installation.
5. Configure the odbc.ini file.

To install the driver using silent mode

1. Generate a response file odbc.rsp contained the following two lines:  

    -G licenseAccepted=true
    -P wsodbc.installLocation="
/usr/opt/ibm/WSII/odbc"
   
Notes:
  • licenseAccepted=true indicate you accept the license
  • wsodbc.installLocation will set the location where you want to install ODBC branded driver.    

2. Go to an operating system command prompt and enter:

./odbcsetup.bin -options odbc.rsp -silent  

3. Configure the odbc.ini file.

To install the driver version 7.1.6 or above

1. Untar the package to install.

Example:
$ mkdir -p /opt/odbc
$ tar -zxvf odbc716-IFS-v97-to-v105-linuxamd64-161115.tar.gz -C /opt/odbc

2. Configure the odbc.ini file.

To configure the odbc.ini file

After you install the ODBC driver, configure the system information file, which is usually named odbc.ini.

The following sample odbc.ini file shows how to configure the ODBC driver client for Microsoft SQL Server:

odbc.ini (assuming the ODBC driver clients are installed at /usr/opt/ibm/WSII/odbc )
[ODBC data sources]
mssqlserver=Microsoft SQL Server 2000

[ODBC]
Trace=0
TraceDll=/usr/opt/ibm/WSII/odbc/lib/odbctrac.so
InstallDir=/usr/opt/ibm/WSII/odbc
quotedID=yes

[Microsoft SQL Server]
Driver=/usr/opt/ibm/WSII/odbc/lib/VMmsss22.so
Description=Microsoft SQL Server Driver for AIX
Database=
database_name
Address=
ip_addr,port_number

"VMmsss22.so"** is the name of the Microsoft SQL Server Wire Protocol driver.

**NOTE: The name for the IBM branded ODBC driver are usually composed by three part:

Branded name (first two letters) + Data source special name + driver version(last two numbers) + file suffix(.so or .a)

For example:
1. VMmsss22.so/VMmsss23.so/VMmsss24.so
VM is branded odbc driver for DB2 V9.7 or later version
msss is for Microsoft SQL Server data source
22 is for branded odbc driver version which is branded from Datadirect 5.2
23 is for branded odbc driver version which is branded from Datadirect 5.3
24 is for branded odbc driver version which is branded from Datadirect 6.0
.so is file suffix.

2. FRmsss21.so
FR is branded odbc driver for DB2 V9.1
msss is for Microsoft SQL Server data source
21 is for branded odbc driver version which is branded from Datadirect 5.1
.so is file suffix.


Running the example application

The product is shipped with a small C application, named example. This application is installed in the example subdirectory in the product installation directory. See the readme file in the example directory for an explanation of how to build and use this application.***

To run the example application, you should make sure the ODBCINI environment variable points to the location of the odbc.ini file and the following environment variables include the ODBC driver library path.

AIX:
  • LIBPATH, includes the directory /usr/opt/ibm/WSII/odbc/lib

HP-UX®:
  • SHLIB_PATH (32-bit and 64-bit) or LD_LIBRARY_PATH (64-bit), includes the directory /usr/opt/ibm/WSII/odbc/lib

Linux® and Solaris®:
  • LD_LIBRARY_PATH, includes the directory /usr/opt/ibm/WSII/odbc/lib

***NOTE: When you run the example, you might see the following warning message:

Warning:
[DataDirect][ODBC SQL Server Driver][SQL Server]The DataDirect ODBC driver you are attempting to access has been provided to you by IBM Corporation for exclusive use with IBM Information Server.  You are not licensed to use this driver with any application other than IBM Information Server.  If you would like to purchase a driver for some other use, please call 800-876-3101 or visit DataDirect at www.datadirect.com NetConn: 100

This error is expected because you are only licensed to use this driver with IBM software and not any other application including the example application.

Why am I get QEWSD property in the odbc.ini****

The DataDirect ODBC driver will put a QEWSD property in the odbc.ini if:
  • Expired license file
  • Wrong license file
  • No license file

****NOTE: If you use ODBC wrapper with IBM Branded DataDirect ODBC driver in V9.1 , V9.5 GA or V9.5 fixpack 1, you will see above problems too because ODBC wrapper was not enabled to support the Driver. Starting from WebSphere Federation Server V9.5 fixpack 2 and later version, the ODBC wrapper began to support IBM branded DataDirect ODBC driver , you should upgrade to fixpak 2 or later version in order to avoid such problem.


ReadmeODBC.txt which shipped with IBM branded ODBC driver installer is not applicable for Federation Server

The new readme file for Federation Server will be shipped with later version of IBM branded ODBC driver installer. You can also get the readme file from the following link:

ftp://public.dhe.ibm.com/software/db2ii/downloads/odbc_driver/readmeODBCforIFS.txt


Some typical errors which are caused by incorrect "InstallDir" in odbc.ini

When you are using Microsoft SQL Server Wire Protocol driver "VMmsss2x.so" in branded DataDirect® ODBC driver version 5.2, 5.3 or 6.0, please make sure to set the "InstallDir" configuration entry correctly in odbc.ini. The install directory should be the immediately superior directory of "lib" directory which contain "VMsss2x.so" library file. An improper "installDir" value will result in following typical errors which may have confusing phenomena.
  • Create nickname fails with error message:
    SQL1415N The statement was compiled for diagnostic purposes only and has not been executed
  • Select character column which contains extended Latin character fails with error message:
    SQL1822N Unexpected error code "20451" received from data source "XXXXX", Associated text and tokens are "20451". SQLSTATE=560B


Note for updating IBM branded DataDirect ODBC driver

IBM branded DataDirect ODBC driver version 6.0 or later can be used in both WebSphere Federation Server V9.5 and V9.7, when you decide to download and install new version of branded ODBC driver, please make sure to remove elder version and clean up original installDir, beacuse new installation will install at same place by default and won't cover elder files, that will cause some unexpected errors like HANG during later use.


Special Recommendation for new Connect for ODBC SQL Server Wire Protocol driver "VMsqls2x.so"

"VMsqls2x.so" is a new driver DataDirect released, which has much more features than the Connect for ODBC SQL Server Legacy Wire Protocal driver "VMmsss2x.so".

We highly recommend the use of new SQL Server Wire Protocol driver unless your application has a requirement for using the Legacy driver, especially when connecting to Microsoft SQL Server 2008 or later version. New driver has already been shipped in branded driver package, you can find it under InstallDir/lib directory, to use new driver, you just need to update your odbc.ini and db2dj.ini file, replace the original "VMmsss2x.so" setting to "VMsqls2x.so".

[{"Product":{"code":"SS2K5T","label":"InfoSphere Federation Server"},"Business Unit":{"code":"BU001","label":"Analytics Private Cloud"},"Component":"Data Sources and Wrappers - Microsoft SQL Server","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"}],"Version":"9.7;10.1;10.5","Edition":""},{"Product":{"code":"SS2K5T","label":"InfoSphere Federation Server"},"Business Unit":{"code":"BU001","label":"Analytics Private Cloud"},"Component":"Data Sources and Wrappers - Microsoft SQL Server","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"}],"Version":"9.5;9.7","Edition":""}]

Document Information

Modified date:
16 June 2018

UID

swg21307359