CROSS-REFERENCE TO RELATED APPLICATION

This application is related to the following co-pending and commonly-assigned patent application:U.S. Utility patent application Ser. No. 15/281,607, filed on Sep. 30, 2016, by Pravin K. Kedia et al., entitled “ACL BASED OPEN TRANSACTIONS IN REPLICATION ENVIRONMENT,”;

which application is incorporated by reference herein.

BACKGROUND

The present invention relates generally to the field of data replication, and more particularly, to the reporting of latency values in a data replication environment.

In today's competitive markets, many companies provide data replication tools with their database management systems (DBMS). These data replication tools are used to replicate data from a source data store to one or more target data stores on a close to real-time basis.

However, there is a need for improved methods for measuring the latency involved in the replication, from the perspective of both the source and target data stores.

SUMMARY

The invention provided herein has a number of embodiments useful, for example, in implementing a computer-implemented method, system and computer program product for performing a dynamic rollover of source and target latency in a replication environment, by: parking one or more tables of a source data store being replicated to a target data store; identifying open transactions, which are in-progress and not completed, where the parked tables affect the source and target latency; and calculating the source and target latency for the identified open transactions. Thereafter, the identified open transactions may be skipped or ignored, and any subsequent changes for the parked tables need not be replicated to the target data store.

Identifying the open transactions may comprise identifying the open transactions where only the parked tables are in-scope tables. Identifying the open transactions may also comprise identifying the open transactions where the parked tables are in-scope tables and the identified open transactions were initiated by one or more users with a determined minimum privilege to perform at least one of an insert, update or delete operation against the parked tables.

The source latency shows a difference in time between when at least one of an insert, update or delete operation for the identified open transaction was written to a transaction log and when the operation was read from the transaction log for replication to the target data store.

The target latency shows a difference in time between when at least one of an insert, update or delete operation for the identified open transaction was written to a transaction log and when the operation was applied to the target data store.

