Replication Intrusions and Impacts on the DB2 UDB

The performance and operation of the DB2 UDB primary data servers in an SAP replication system may be affected by the transaction log.

You must set the LOGARCHMETH1 configuration parameter to LOGRETAIN or DISK:<path>, where <path> is the directory to which the logs are archived. To determine the current LOGARCHMETH1 setting, use the following UDB command:
```
get db cfg for <db-alias>
```
Replication requires a before and after image of each row that is changed. When you mark a primary table for replication, the Replication Agent for UDB sets the table’s DATA CAPTURE option to DATA CAPTURE CHANGES. As the number of tables marked for replication increases, so does the space requirement for the DB2 UDB transaction log.
The primary database must have a user temporary system managed tablespace with a page size of at least 8KB.