Use LAG REPLICAT to determine a true lag time between Replicat and the trail. LAG REPLICAT estimates the lag time more precisely than INFO REPLICAT because it communicates with Replicat directly rather than reading a checkpoint position.

For Replicat, lag is the difference, in seconds, between the time that the last record was processed by Replicat (based on the system clock) and the timestamp of the record in the trail.

If the heartbeat functionality is enabled, you can view the associated lags. A DBLOGIN is required to view the heartbeat lag.

From 21c onward, the DB_UNIQUE_NAME is displayed if it exists for a remote database, otherwise the DB_NAME value is displayed.

GGSCI Syntax

LAG EXTRACT [, group_name[threadID]name]
[, GLOBAL]

group_name[threadID]

The name of:

• A Replicat group or a wildcard (*) to specify multiple groups. For example, T* shows lag for all Replicat groups whose names begin with T.

• A thread of a coordinated Replicat, identified by its full name. For example, repe003 shows lag for thread 3 of coordinated Replicat repe.

GLOBAL

Displays the lags in the GG_LAGS view.

Examples

LAG REPLICAT *

LAG REPLICAT *repe*