ODBC data sources 2

Database drivers 3
Supported data sources 4
Configuring the ODBC driver and the ODBC data source name 5
Configuring the ODBC data source in a parallel processing environment 7
Configuring access to ODBC data sources
There are no special installation requirements for the ODBC connector . However,
Before you can use the ODBC connector in a job, you need to configure database
drivers, driver managers, and data source names.
1. Database drivers
You must install and configure database drivers and at least one driver manager
before you can use the ODBC connector.
2. Supported data sources
Before the ODBC connector can open a table or file to read and write data, a
connection must be defined to the data source that contains that table or file.
3. Configuring the ODBC driver and the ODBC data source name
To access ODBC data sources from InfoSphere® Information Server, you must
configure the ODBC driver and the ODBC data source name (DSN) definitions.
Parent topic:Configuring access to data sources

2
Database drivers
You must install and configure database drivers and at least one driver manager
before you can use the ODBC connector.
Supported drivers are included with the installation of the product. The default
installation directory is install_home/Server/branded_odbc. The DataDirect Connect
for ODBC for SQL Server Legacy Wire Protocol driver (VMmsss00.so and
VMmsss00.dll) is now deprecated. Use the DataDirect Connect for ODBC for SQL
Server Wire Protocol driver (VMsqls00.so and VMsqls00.dll) instead.
The following drivers have limitations or special configuration requirements when
you use them with the ODBC connector:
- IBM® Text File Driver
- Supported data types. Only Numeric, Date, and VarChar are supported.
- Unsupported runtime data types. The following runtime data types are not
supported:
- Bit
- Binary
- LongNVarChar
- LongVarBinary
- LongVarChar
- NChar
- NVarChar
- Time
- Timestamp
- SQL Server driver
- Large objects (LOBs) by reference. You cannot pass them by reference with
this driver. You must transfer them inline.
- SQL Server native driver
- Transfer large objects (LOBs) by reference. You cannot pass them by
reference with this driver. You must transfer them inline.
- SQL Server wire driver
- Transfer large objects (LOBs) by reference. You cannot pass them by
reference with this driver. You must transfer them inline.
- View design-time data. To view design-time data that contains spaces, you
must select the quoted identifiers check box on the Advanced tab of the driver
setup window.

Parent topic:Configuring access to ODBC data sources

Next topic:Supported data sources

3
Supported data sources
Before the ODBC connector can open a table or file to read and write data, a
connection must be defined to the data source that contains that table or file.
To be a supported data source, the ODBC connector must be able to perform read,
write, and lookup SQL statements and to exchange data between external data
sources and the IBM® InfoSphere® DataStage® data sets. You must also define
names for each data sources that are specific to the operating system, driver
manager, and driver.
For the ODBC connector, the ODBC driver manager establishes the connection. To
establish your data sources, the following requirements must be met:
- The driver and driver manager must be installed on the system where the
connector is installed and running. The data source can be on a remote system.
You can connect to multiple data sources.
- For parallel jobs, the driver and driver manager must be installed on every node
the ODBC connector runs.
You can connect to only one ODBC driver manager at a time.
When you configure the driver manager and you are logged into the IBM
InfoSphere DataStage and QualityStage® Designer, you can see a list of data
source names in the Data source property by clicking the Data source button. If you
are working in a design environment that is not connected to the server, you can
type a value in the Data source property.

Parent topic:Configuring access to ODBC data sources

Previous topic:Database drivers

Next topic:Configuring the ODBC driver and the ODBC data source name

4
Configuring the ODBC driver and the ODBC data
source name
To access ODBC data sources from InfoSphere® Information Server, you must
configure the ODBC driver and the ODBC data source name (DSN) definitions.
Before you begin
- Install client libraries.
- Test the connection to the ODBC data source.
- On 64-bit Windows computers, make sure that you run the 32-bit version of the
Microsoft ODBC Data Source Administrator
C:\Windows\SysWOW64\odbcad32.exe, as InfoSphere Information Server is a 32-
bit application. If you run the 64-bit version of the ODBC administrator application,
the Netezza connector cannot to locate the specified data source name. If the
ODBC administrator application is not accessible through the File menu by default,
use the Windows Explorer to access the application.
Procedure
1. Configure the ODBC DSN definitions:Table 1. Configuring the ODBC data source
name definitions

Operating System Procedure

UNIX or Linux Set the ODBCINI environment
variable to point to the .odbc.ini
file. The.odbc.ini file contains
the ODBC DSN definitions.
Note: The ODBCINI
environment variable is set in
the dsenv script automatically
as part of the InfoSphere
Information Server installation
process.
Microsoft Windows The DSN definitions are
managed by the ODBC driver
manager application included
with the operating system. The
ODBC DSN definitions must be
configured as System DSN
definitions in the ODBC data
source Administrator. The
ODBCINI environment variable
is not applicable on Microsoft
Windows.

2. Add the path to the directory that contains the client libraries to the library path
environment variable. The default path for client libraries is as follows:
- On Windows, C:\IBM\InformationServer\ODBCDrivers. On the Microsoft
Windows, the ODBC driver manager library is provided by the operating system.
The location of the ODBC driver manager is automatically included in the PATH
environment variable.
5
 - On Linux and UNIX, /opt/IBM/InformationServer/Server/branded_odbc/lib. The
ODBC driver manager is included with InfoSphere Information Server

3. On UNIX and Linux computers, to restart the server engine and the ASB Agent,
enter the following command:cd Install_directory/Server/DSEngine/bin
./uv -admin -stop

./uv -admin -start

cd Install_directory/ASBNode/bin

. ./NodeAgents_env_DS.sh

./NodeAgents.sh stopAgent

./NodeAgents.sh start

- Configuring the ODBC data source in a parallel processing environment

You can configure the ODBC data source in a parallel processing environment
with one conductor node and multiple player nodes.
Parent topic:Configuring access to ODBC data sources
Previous topic:Supported data sources

Related tasks
- Setting the library path environment variable

Related information
- Configuring ODBC access (AIX HP-UX Linux)
- Configuring ODBC access (Microsoft Windows)

6
Configuring the ODBC data source in a parallel
processing environment
You can configure the ODBC data source in a parallel processing environment with
one conductor node and multiple player nodes.
Before you begin
- Install client libraries.
Procedure
1. Add the path to the directory that contains the client libraries to the library path
environment variable.
2. Copy the following directory from the conductor node to all computer nodes:
- On Windows, C:\IBM\InformationServer\ODBCDrivers.
- On Linux and UNIX, /opt/IBM/InformationServer/Server/branded_odbc/lib.

3. Copy the .odbc.ini file from the conductor node to all computer nodes.
4. On UNIX and Linux computers, to restart the server engine and the ASB Agent,
enter the following command:cd Install_directory/Server/DSEngine/bin
./uv -admin -stop

./uv -admin -start

cd Install_directory/ASBNode/bin

. ./NodeAgents_env_DS.sh

./NodeAgents.sh stopAgent

./NodeAgents.sh start

Parent topic:Configuring the ODBC driver and the ODBC data source name