Learn about known issues and workarounds for Replication Agent that are specific to IBM DB2 Universal Database (UDB).
| CR# | Description |
|---|---|
| 707544 |
Replication Agent error occurs when character cases in the primary database marked object definition and the ltl_character_case property do not match. Workaround: Set use_rssd property to true. |
| 702840 |
A Replication Agent for IBM DB2 UDB system message on resume after ra_locator zero conveys that the truncation point has been moved to the end, instead of describing that the truncation point has been moved to the beginning of the log. Workaround: None. |
| 700501 |
Replication Agent for UDB now recommends using the IBM DB2 Universal Database JDBC driver for database connectivity. Workaround: Change the
pds_connection_type value to
UDBJDBC.
Note: Upgrade from an earlier release to
15.7.1 automatically changes the connection type to
UDBJDBC.
|
| 700485 |
The lr_read_buffer_size default value of 16K is too small, frequently resulting in DB2 SQL error 2650 and reason code 8, which maps to this error:The buffer is not of sufficient size to store a log record. Workaround: Increase the read buffer size to at least 64K. |
|
Error occurs if the library path contains two colons. For HP, if SHLIB_PATH contains two colons (::) with no intervening directory, you see this error message when you resume Replication Agent: java.lang.NoClassDefFoundError
Workaround: Add a line to the
$SYBASE/RAX-15_5/bin/ra.sh script to source
your UDB instance’s db2profile (which does not
have the same problem as the db2cshrc). For
example, if your UDB instance directory is
“/home/db2inst1”, edit your Replication
Agent script to add
/home/db2inst1/sqllib/db2profile:
elif [ $os = HP-UX ] then . /home/db2inst1/sqllib/db2profile SRVR=-server SHLIB_PATH=$ASA_LIB:$RAX_DIR/lib/hpux:$SHLIB_PATH export SHLIB_PATH |