Installation for Data Engineering

10.5.3
- 10.5.7
- 10.5.6
- 10.5.5.1
- 10.5.5
- 10.5.4
- 10.5.2
- 10.4.1
- 10.4.0

Back Next

Configuring Native Connectivity

You can configure native connectivity to an IBM DB2 database to increase performance.

The following steps provide a guideline for configuring native connectivity. For specific instructions, see the database documentation.

To configure connectivity on the machine where the Data Integration Service, PowerCenter Integration Service, or PowerCenter Repository Service process runs, log in to the machine as a user who can start a service process.

Set the DB2INSTANCE, INSTHOME, DB2DIR, and PATH environment variables.

The UNIX IBM DB2 software always has an associated user login, often db2admin, which serves as a holder for database configurations. This user holds the instance for DB2.

DB2INSTANCE
. The name of the instance holder.

Using a Bourne shell:

$ DB2INSTANCE=db2admin; export DB2INSTANCE

Using a C shell:

$ setenv DB2INSTANCE db2admin

INSTHOME
. This is db2admin home directory path.

Using a Bourne shell:

$ INSTHOME=~db2admin

Using a C shell:

$ setenv INSTHOME ~db2admin>

DB2DIR
. Set the variable to point to the IBM DB2 CAE installation directory. For example, if the client is installed in the /opt/IBM/db2/V9.7 directory:

Using a Bourne shell:

$ DB2DIR=/opt/IBM/db2/V9.7; export DB2DIR

Using a C shell:

$ setenv DB2DIR /opt/IBM/db2/V9.7

PATH
. To run the IBM DB2 command line programs, set the variable to include the DB2 bin directory.

Using a Bourne shell:

$ PATH=${PATH}:$DB2DIR/bin; export PATH

Using a C shell:

$ setenv PATH ${PATH}:$DB2DIR/bin

Set the shared library variable to include the DB2 lib directory.

The IBM DB2 client software contains a number of shared library components that the Data Integration Service, PowerCenter Integration Service, and PowerCenter Repository Service processes load dynamically. Set the shared library environment variable so that the services can find the shared libraries at run time.

The shared library path must also include the Informatica installation directory

(server_dir)

Set the shared library environment variable based on the operating system.

The following table describes the shared library variables for each operating system:

Operating System	Variable
Linux	LD_LIBRARY_PATH
AIX	LIBPATH

For example, use the following syntax for Linux:

Using a Bourne shell:

$ LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$HOME/server_dir:$DB2DIR/lib; export LD_LIBRARY_PATH

Using a C shell:

$ setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:$HOME/server_dir:$DB2DIR/lib

For AIX:

Using a Bourne shell:

$ LIBPATH=${LIBPATH}:$HOME/server_dir:$DB2DIR/lib; export LIBPATH

Using a C shell:

$ setenv LIBPATH ${LIBPATH}:$HOME/server_dir:$DB2DIR/lib

Edit the .cshrc or .profile to include the complete set of shell commands. Save the file and either log out and log in again or run the source command.

Using a Bourne shell:

$ source .profile

Using a C shell:

$ source .cshrc

If the DB2 database resides on the same machine on which the Data Integration Service, PowerCenter Integration Service, or PowerCenter Repository Service process runs, configure the DB2 instance as a remote instance.

Run the following command to verify if there is a remote entry for the database:

DB2 LIST DATABASE DIRECTORY

The command lists all the databases that the DB2 client can access and their configuration properties. If this command lists an entry for “Directory entry type” of “Remote,” skip to step 7.

If the database is not configured as remote, run the following command to verify whether a TCP/IP node is cataloged for the host:

DB2 LIST NODE DIRECTORY

If the node name is empty, you can create one when you set up a remote database. Use the following command to set up a remote database and, if needed, create a node:

db2 CATALOG TCPIP NODE <nodename> REMOTE <hostname_or_address> SERVER <port number>

Run the following command to catalog the database:

db2 CATALOG DATABASE <dbname> as <dbalias> at NODE <nodename>

For more information about these commands, see the database documentation.

Verify that you can connect to the DB2 database. Run the DB2 Command Line Processor and run the command:

CONNECT TO <dbalias> USER <username> USING <password>

If the connection is successful, clean up with the

CONNECT RESET

TERMINATE

command.

Connecting to an IBM DB2 Universal Database

Download Guide

Watch

Comments

Communities

Knowledge Base

Success Portal

0 COMMENTS

We’d like to hear from you! Log in to comment.

Rename Saved Search

Table of Contents

Installation for Data Engineering

Installation for Data Engineering

Configuring Native Connectivity

Configuring Native Connectivity