IBM DB2 Requirements

Observe these requirements for IBM DB2 for Linux, Unix, and Windows.

The database must be version 9.1, 9.5, or 9.7.
If you have a UDB client instance and a UDB server instance on different machines, the client and server must be of the same UDB version.
The database must have a valid JDK path configured. The JDK_PATH configuration parameter must contain the full path to the directory above the bin directory, which contains the java executable. To determine the database manager JDK_PATH setting, use this DB2 command:
```
get dbm cfg
```
Note: A 64-bit IBM DB2 instance requires a 64-bit JDK, and a 32-bit DB2 instance requires a 32-bit JDK.
If Replication Agent is installed on a Linux or UNIX host, you must configure a client or server 64-bit DB2 instance.
The database LOGARCHMETH1 configuration parameter must be set to LOGRETAIN or DISK:<path>, where <path> is a directory to which logs are archived. This enables archive logging in place of circular logging. To determine the LOGARCHMETH1 setting, use this DB2 command:
```
get db cfg for <db-alias>
```
On a Windows system, the DB2 connectivity autocommit parameter must be turned on (automcommit=1). The autocommit parameter is specified in the DB2 call level interface (CLI) configuration file for the primary database. If the autocommit parameter is not turned on, a deadlock problem can occur. The path to the CLI configuration file is:

%DB2DIR% \sqllib\db2cli.ini

where %DB2DIR% is the path to the DB2 client installation.
To initialize Replication Agent without error, the database must have a tablespace created with these characteristics:
- The tablespace should be a user temporary tablespace. By default, user temporary tablespaces are not created when a database is created.
- The tablespace must be a system-managed space (SMS).
- The PAGESIZE parameter must be set to 8192 (8 kilobytes) or greater.
The user ID you specify as the pds_username user must have either SYSADM or DBADM authority to access the primary database transaction log.
All the DB2 environment variables must be set before you start the Replication Agent. Replication Agent uses the DB2 CLI driver to connect to the primary DB2 database. For UNIX, the driver is contained in libdb2.so, libdb2.sl, or libdb2.a, depending on the operating system. For Windows, the DB2 driver is contained in db2cli.dll. Replication Agent also uses DB2 API libraries to read the transaction log. The library path environment variable must therefore be set for Replication Agent to load the correct driver and API libraries at runtime.

For UNIX and Linux, the 64-bit versions of the libraries are located in the $HOME/sqllib/lib64 directory, where $HOME is the home directory of the DB2 instance owner. If Replication Agent is installed on Linux or UNIX, the library path environment variable must point to the 64-bit libraries. For Windows, the library path environment variable must point to the 32-bit libraries.

The exact name of the library path environment variable depends on the operating system. For Linux, the library path variable is named LD_LIBRARY_PATH. For Windows, the library path variable is named PATH.

On Windows, the DB2 server or client installation sets all necessary environment variables. On UNIX or Linux, you must source the DB2 db2cshrc (for C-shell) or the db2profile (for Bourne and Korn shells) script before starting the Replication Agent. These scripts are located at $HOME/sqllib, where $HOME is the home directory of the DB2 instance owner (for a DB2 client or server instance).