This section provides a summary of all the DB2 UDB universal database requirements.
The database must be at least version 8.2.2 (the same as version 8.1 with FixPak 9) or later.
The database must have a valid JDK path configured. To determine the JDK_PATH setting, use the following UDB command:
get dbm cfg
The database LOGARCHMETH1 configuration parameter must be set to LOGRETAIN. This enables archive logging in place of circular logging. To determine the LOGARCHMETH1 setting, use the following UDB command:
get db cfg for <db-alias>
The ODBC autocommit parameter must be turned on (automcommit=1). The ODBC autocommit parameter is specified in the DB2 call level interface (CLI) configuration file for the primary database. If the ODBC autocommit parameter is not turned on, a deadlock problem can occur.
On Windows, the file is: C:\IBM\sqllib\db2cli.ini
On UNIX, the file is:
$DB2DIR/cfg/db2cli.ini
where $DB2DIR is the path to the UDB client installation, or
$HOME/sqllib/db2cli.ini
where $HOME is the home directory of the UDB instance owner (for UDB server installation)
If you plan to use Replication Agent's log truncation feature, the database must have a minimum of 8KB user temporary table space for the truncation process.
The user ID you specify as the pds_username user must have either SYSADM or DBADM authority in order to access the primary database transaction log.
The UDB Administration Client shared libraries that Replication Agent links with must be 32-bit libraries—they cannot be 64-bit. If your UDB database is 64-bit, you must install Replication Agent on a different host machine with a 32-bit UDB Administration Client.
All the UDB environment variables must be set before you start the Replication Agent.
On Windows, the UDB server or client installation sets all necessary environment variables, so you need do nothing special.
On Unix or Linux, you must source the UDB db2cshrc (for C-shell) or the db2profile (for Bourne and Korn shells) script before starting the Replication Agent. These scripts are located in
$DB2DIR/cfg
where $DB2DIR is the path to the UDB client installation, or
$HOME/sqllib
where $HOME is the home directory of the UDB instance owner (for UDB server installation
