IBM DB2 Universal Database Requirements

This section provides a summary of all the IBM DB2 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 JDK_PATH should point to a 32-bit JDK for all platforms except HP Itanium. For HP Itanium, the JDK_PATH should point to a 64-bit JDK.

• 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>
  

• The UDB 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.

  • On Windows, the file is:

    %DB2DIR%\sqllib\db2cli.ini

    Here, %DB2DIR% is the path to the UDB client installation

  • On UNIX, the file is one of the following:

    • $DB2DIR/cfg/db2cli.ini

      Here, $DB2DIR is the path to the UDB client installation

    • $HOME/sqllib/cfg/db2cli.ini

      Here, $HOME is the home directory of the UDB instance owner (for UDB server installation)

• If you plan to use the Replication Agent log truncation feature, the database must have a user temporary system-managed tablespace with a page size of at least 8KB. This space requirement also applies to the Replication Agent initialization process.

• 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 IBM DB2 Universal Database CLI driver to connect to the primary UDB database. For UNIX, the DB2 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. The 32-bit versions of the driver libraries are located in the <library_path>/sqllib/lib32 directory. For all Replication Agent platforms except HP Itanium, the library path environment variable must point to 32-bit libraries, not to 64-bit libraries. The exact name of the library path environment variable depends on the operating system:

  • For Solaris and Linux, the library path variable is named LD_LIBRARY_PATH.

  • For HP-UX, the library path variable is named SHLIB_PATH.

  • For AIX, the library path variable is named LIBPATH.

  • For Windows, the library path variable is named PATH.

  • 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 one of the following paths:

    • $DB2DIR/cfg

      Here, $DB2DIR is the path to the UDB client installation

    • $HOME/sqllib

      Here, $HOME is the home directory of the UDB instance owner (for UDB server installation)