LAGCRITICAL
Valid for
Manager
Description
Use LAGCRITICALCSECS, LAGCRITICALSECONDS, LAGCRITICALMINUTES, or LAGCRITICALHOURS to specify the time interval at which Extract or Replicat processing lag is reported to the event log as a critical message. For example, LAGCRITICALMINUTES 5 specifies a reporting interval of five minutes. Likewise, LAGCRITICALSECONDS 20 specifies a reporting interval of 20 seconds; LAGCRITICALHOURS 2 specifes two hours.
When using a LAGCRITICAL parameter, specify LAGREPORT to determine how often the lag times are evaluated and reported.
Syntax
LAGCRITICALCSECScsecs[,process_typegroup_name] [,IGNORETASKS|REPORTTASKS] [,IGNORESTOPPED|REPORTSTOPPED]| LAGCRITICALSECONDSseconds[,process_typegroup_name] [,IGNORETASKS|REPORTTASKS] [,IGNORESTOPPED|REPORTSTOPPED]| LAGCRITICALMINUTESminutes[,process_typegroup_name] [,IGNORETASKS|REPORTTASKS] [,IGNORESTOPPED|REPORTSTOPPED]| LAGCRITICALHOURShours[,process_typegroup_name] [,IGNORETASKS|REPORTTASKS] [,IGNORESTOPPED|REPORTSTOPPED]
-
csecs -
The reporting interval in centiseconds, as in
LAGCRITICALCSECS50. -
seconds -
The reporting interval, in seconds, as in
LAGCRITICALSECONDS10. -
minutes -
The reporting interval, in minutes, as in
LAGCRITICALMINUTES5. -
hours -
The reporting interval, in hours, as in
LAGCRITICALHOURS1. -
process_typegroup_name -
Specifies the process for which the lag will be reported.
-
IGNORETASKS|REPORTTASKS -
By default the task groups are not reported.
By adding the
REPORTTASKSoption, the lag information will be reported forSOURCEISFILEandSPECIALRUNgroups, toggle off withIGNORETASKS. -
IGNORESTOPPED|REPORTSTOPPED -
By default no information is printed for a group in a
STOPPEDstate. By adding theREPORTSTOPPEDoption, lag information will be reported, to toggle off withIGNORESTOPPED.