How to Create an OGG Lag Report Every 30 Minutes Instead of Every 10 Minutes. (Doc ID 1364816.1)

Last updated on DECEMBER 22, 2013

Applies to:

Oracle GoldenGate - Version 10.4.0.112 and later
Information in this document applies to any platform.

Goal

How can the frequency for which report lag information is written to the event log be changed?

Here is an example of a parameter file:

> cat mgr.prm
PORT 7810
--Forces manager to restart extract, datapump and replicat if they shut down
--AUTORESTART ER *, RETRIES 60, WAITMINUTES 1, RESETMINUTES 60
--Manages trail files to conserve space
PURGEOLDEXTRACTS ./dirdat/*, USECHECKPOINTS, MINKEEPDAYS 7, FREQUENCYMINUTES 30
--Specifies to log the lag time as a warning in the event log
LAGCRITICALMINUTES 240
--Specifies how often to report lag info to the event log
LAGREPORTMINUTES 30
LAGINFOMINUTES 0


Despite changing the LAGREPORTMINUTE to 30 minutes, it is still reporting every 10 minutes.

All Oracle GoldenGate (OGG) processes were restarted after making sure there were no orphaned processes still remaining.


Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms