LAGREPORT

Valid for

Manager

Description

LAGREPORTMINUTES and LAGREPORTHOURS determine the interval at which Manager checks lag for Extract and Replicat processing.

For example, LAGREPORTHOURS 1 reports lag every hour. If the lag is greater than the time specified by LAGCRITICAL, Manager reports the LAG as critical, otherwise, it reports the lag as an informational message. LAG is not reported if the values are below the threshold set with the LAGINFO parameter.

If LAG is being reported from Extract or Replicat, that it is “Running but has not checkpointed” in the specified time using either LAGCRITICAL or LAGINFO, you should send the process a STATUS command from GGSCI, and take the appropriate action depending on the reply. Do not stop the process.

Examples:

• A Reply of Process is suspended, waiting for Resume command is the result of an EVENTACTION triggering a SUSPEND and waiting for a GGSCI RESUME.

• A reply of Retrying open error 11 on file is waiting for someone to create the missing target file for a Replicat to continue.

• A reply of status: Waiting for more audit or Records so far in current transaction is almost certainly working correctly; possibly waiting on a large transaction.If the problem persists and you are not sure how to resolve it, contact Oracle GoldenGate support.

Syntax

LAGREPORTMINUTES minutes | LAGREPORTHOURS hours

minutes

The reporting interval, in minutes, as in: LAGREPORTMINUTES 5.

hours

The reporting interval, in hours, as in: LAGREPORTHOURS 1.