It's highly recommended to deploy this script on all (source & destination) replication servers in order to detect the lag on all (Extract, Pump, and Replicat) processes.
This script is not designed to monitor the replicated data inside the tables it totally relies on the native GoldenGate GGSCI console.
This script should be executed/scheduled by the GoldenGate installation owner OS user.
How it works:
First, Download the script:
https://www.dropbox.com/s/l4dqzicviuaawt6/goldengate_lag_mon.sh?dl=0
Second, Adjust the following parameters:
MAIL_LIST="youremail@yourcompany.com"
Replace "youremail@yourcompany.com" pattern with your e-mail.
# ###########################################
# Mandatory Parameters To Be Set By The User:
# ###########################################
ORACLE_HOME=# ORACLE_HOME path of the database where GoldenGate is running against.
GG_HOME= # GoldenGate Installation Home path. e.g. GG_HOME=/goldengate/gghome
Please note that ORACLE_HOME & GG_HOME are mandatory to be adjusted by the user, in case you missed setting them, the script will automatically try to guess the right values, but this is not accurate, most probably the script may not work.
# ################
# Script Settings:
# ################
# LAG THRESHOLD in minutes: [If reached an e-mail alert will be sent. Default 10 minutes]
LAG_IN_MINUTES=10
Here you define the LAG threshold in minutes (it's 10 minutes by default).
# Excluded Specific PROCESSES NAME:
# e.g. If you want to exclude two replicate processes with names REP_11 and REP_12 from being reported then add them to below parameter as shown:
# EXL_PROC_NAME="DONOTREMOVE|REP_11|REP_12"
EXL_PROC_NAME="DONOTREMOVE"
DISCLAIMER: THIS SCRIPT IS DISTRIBUTED IN THE HOPE THAT IT WILL BE USEFUL BUT WITHOUT ANY WARRANTY. IT IS PROVIDED "AS IS".
GitHub version: