IBM DB2 Requirements
Observe these requirements for IBM DB2 for Linux, Unix, and Windows.
Replication Agent and a DB2 Server on Different Machines
If the Replication Agent for UDB software is installed on a different host machine from the DB2 server, you must install the DB2 Administration Client on the same host machine as the Replication Agent.
Repositioning in the Log
The Replication Agent uses the value of the LTM locator received from the primary Replication Server to determine where to begin looking in the DB2 transaction log for transactions to be sent to the Replication Server.
Character Case of Database Object Names
Database object names must be delivered to the primary Replication Server in the same format as specified in replication definitions; otherwise, replication fails. For example, if a replication definition specifies a table name in all lowercase, then that table name must appear in all lowercase when it is sent to the primary Replication Server by the Replication Agent.
Format of Origin Queue ID
Each record in the transaction log is identified by an origin queue ID that consists of 64 hexadecimal characters (32 bytes). The format of the origin queue ID is determined by the Replication Agent instance and varies according to the primary database type.
DB2 Datatype Compatibility
Replication Agent for UDB processes transactions and passes data to the primary Replication Server. The primary Replication Server uses the datatype formats specified in the replication definition to receive the data from Replication Agent for UDB.
Replication Server set autocorrection Command
The Replication Server set autocorrection command prevents failures that would otherwise be caused by missing or duplicate rows in a replicated table.
Large Identifiers
Replication Agent for UDB supports UDB 9.5 large identifiers—authorization ID, column, and schema names up to 128 bytes long.
Compression
Replication Agent for UDB supports value compression—tables created with the VALUE COMPRESSION clause—and row compression.