This section provides a summary of all the UDB 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. The JDK_PATH configuration parameter should 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 the following UDB command:
get dbm cfg
A 64-bit IBM UDB instance requires a 64-bit JDK, and
a 32-bit UDB instance requires a 32-bit JDK.
If Replication Agent is installed on Solaris, AIX or HP Itanium, a 64-bit UDB instance must be configured. This can be a server or client instance.
The database LOGARCHMETH1 configuration parameter must be set to LOGRETAIN or DISK:<path>. Here, <path> is a directory to which logs are archived. 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>
On a Windows system, the UDB connectivity autocommit parameter must be turned on (automcommit=1). The autocommit parameter is specified in the UDB 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
Here, %DB2DIR% is the path to the UDB client installation.
To initialize Replication Agent without error, the database must have a table space created with the following characteristics:
The table space should be a user temporary table space. By default, user temporary table spaces are not created when a database is created.
The table space 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 UDB environment variables must be set before you start the Replication Agent. Replication Agent uses the UDB CLI driver to connect to the primary UDB database. For UNIX, the driver is contained in libdb2.so, libdb2.sl, or libdb2.a, depending on the operating system. For Windows, the UDB driver is contained in db2cli.dll. Replication Agent also uses UDB 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 32-bit and 64-bit versions of the libraries are located in the $HOME/sqllib/lib32 and $HOME/sqllib/lib64 directories, respectively, where $HOME is the home directory of the UDB instance owner. If Replication Agent is installed on AIX, Solaris, or HP Itanium, the library path environment variable must point to the 64-bit libraries. For Windows and Linux, 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 UDB server or client installation sets all necessary environment variables. 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 at $HOME/sqllib, where $HOME is the home directory of the UDB instance owner (for a UDB client or server instance).
