Asia Data

Since a mirror table can only be updated asynchronously, there is always a difference between the timeliness of the data in the original tables and the data in the mirror tables. This difference is recorded in a system table that is permanently updated by CDC: SYSTOOLS.REPL_MQT_LATENCY [5] . The table SYSTOOLS.REPL_MQT_LATENCY must be created manually for each database with mirror tables using this procedure call:

CALL SYSPROC.SYSINSTALLOBJECTS('REPL_MQT', 'C', 'SYSTOOLSPACE', NULL);
In the above example, the brazil telegram screening table is stored in the table area SYSTOOLSPACE (3rd parameter), in which other system-related objects are also defined.

SYSTOOLS.REPL_MQT_LATENCY contains only one record with the columns:

COMMIT_POINT
Time of the last commit operation after which the changes to mirror tables were replicated (in seconds since January 1, 1970).
This is the starting time at which the value for the second column DELAY_OFFSET is generated.
DELAY_OFFSET
The number of seconds between the time the source table data is read and the last COMMIT of changes to the mirror table.
To determine the timestamp of the last refresh operation, the value of DELAY_OFFSET must be subtracted from the COMMIT_POINT time.