DB2 10.5 for Linux, UNIX, and Windows

Creating the SYSTOOLS.REPL_MQT_LATENCY table

To share the replication latency information between IBM® InfoSphere® Change Data Capture and a DB2® server, you must create this table in every DB2 database in which shadow tables are used.

Before you begin

Ensure that you can log in into the DB2 server as db2-cdc-user.

About this task

Replication latency is the amount of time that it takes to apply a transaction against a source table to the corresponding shadow table.

By creating the SYSTOOLS.REPL_MQT_LATENCY table, InfoSphere CDC can update the replication latency in this table to help the DB2 optimizer determine whether a query can be routed to shadow tables and take advantage of BLU Acceleration.

Procedure

To create the SYSTOOLS.REPL_MQT_LATENCY table:

Log in the DB2 server as db2-cdc-user.
Connect to the db2-database-name database as follows:
```
db2 CONNECT TO db2-database-name
```

Call the SYSPROC.SYSINSTALLOBJECTS procedure as follows:

db2 "CALL SYSPROC.SYSINSTALLOBJECTS('REPL_MQT', 'C',
       CAST (NULL AS VARCHAR(128)), CAST (NULL AS VARCHAR(128)))"

Verify that the latency table was created successfully by issuing the following command:
```
db2 LIST TABLES FOR SCHEMA SYSTOOLS
```
Optional: To avoid inadvertent changes to the SYSTOOLS.REPL_MQT_LATENCY table, ensure that db2-cdc-user is the only user that has write access to it.