The JDBC driver for DB2 Universal Database is incorporated in the DB2 Administration Client.
The DB2 JDBC driver is effectively a JDBC/ODBC
bridge. For each primary database, you must configure an ODBC data
source name (DSN) in the DB2 client software.
If the Sybase Replication Agent is installed on the same host machine as the DB2 Universal Database primary data server, a separate DB2 client is not required for connectivity.
If the Replication Agent host machine is not the same as the DB2 Universal Database host, you must install the DB2 Administration Client on the Replication Agent host machine.
For information on installing the DB2 Administration Client on your Replication Agent host machine, see the IBM publication, DB2 Universal Database and DB2 Connect, Installation and Configuration Supplement.
To set up a JDBC driver for DB2 Universal Database
servers
When you install a DB2 client on a UNIX platform, you need to source db2cshrc to correctly set all required DB2 environment variables.
Add the following to the .login file of the user account that starts and stops the Replication Agent instance:
source /path_name/sqllib/db2cshrc
where path_name is the path where you installed the DB2 client. You must log out and log back in for this change to take effect, or issue the command source .login after the change.
When you install a DB2 client on Windows 2000 or 2003,
the installation program automatically modifies all required environment variables.
For each primary database (regardless of platform), you must configure an ODBC data source name (DSN) in the DB2 client software. Make a note of the database name and datasource name when you configure the data source.
Be sure to record the database name and datasource name in these Replication Agent configuration parameters:
pds_database_name – ODBC database name
pds_datasource_name – ODBC datasource name
