Configure Goldengate Manager Process


Configure Goldengate Manager Process

The Goldengate Manager is the very first processes that needs to be setup in the replication configuration. This process must be running on the source and the target system and is required to be able to configure and start the other Goldengate processes. It also manages the disk space by purging the old trail files periodically. Only one manager process is required for every Goldengate installation.

Configuring the Goldengate Manager Process

Manager Parameter file
A simple configuration file mgr.prm, is required to start up the process. All parameter files are placed in the $GG_HOME/dirprm directory. The GG_HOME is the home directory where GoldenGate binaries are installed and dirprm was created in the pre-requisites phase by issuing “CREATE SUBDIRS”.

Below are the parameters which can be set in the mgr.prm file.

PORT 7810

PORT The default manager port is 7809.
AUTORESTART ER Restarts the crashed processes
RETRIES Number of restarts attempts
PURGEOLDEXTRACTS Purges the old trail files to manage the disk space
LAGCRITICALMINUTES Warning logged in the error log when lag threshold exceeded
LAGINFOMINUTES Information logged in the error log when lag threshold exceeded
LAGREPORTMINUTES Time interval after which manager process checks the processes for lag

Starting Manager
To manually start up the process the following command can be run from the “ggsci” prompt.

ggsci> start manager

Stopping Manager
In “ggsci” type the below command to stop the manager process.
ggsci> stop manager

The above command asks for your confirmation. Type “y” and press enter.

Advanced Manager Commands

The manager component is the key process which is responsible to manage the other process in the Goldengate environment. To effectively manage this manager process, a list of the must know commands are below.

This command is used to start or stop the manager process. Before this process can be stopped all other dependant processes should be stopped.

GGSCI (ggsdb01) 2> stop manager
Manager process is required by other GGS processes.
Are you sure you want to stop it (y/n)? y

Sending STOP request to MANAGER ...
Request processed.
Manager stopped.

GGSCI (ggsdb01) 3> start manager

Manager started.

STATUS Manager
These provide the current status of the Manager process.

GGSCI (ggsdb01) 1> status manager
Manager is running (IP port ggsdb01.7833).

INFO Manager
GGSCI (ggsdb01) 4> Info manager
Manager is running (IP port ggsdb01.7833).

GGSCI (ggsdb01) 5> Info mgr
Manager is running (IP port ggsdb01.7833).

GGSCI (ggsdb01) 6> refresh manager
Sending REFRESH request to MANAGER ...

GGSCI (ggsdb01) 7> view report MGR

SEND Manager
The SEND command refresh the output directly from memory and show the current state after refreshing.

GGSCI (ggsdb01) 7> send manager childstatus debug
Sending CHILDSTATUS, request to MANAGER ...

Child Process Status - 9 Entries

ID Group Process Retry Retry Time Start Time Port
---- -------- --------- ----- ------------------- ------------------- ----
0 PVST1 3530 0 None 2013/04/26 12:10:49 7840
1 PAH01 3512 0 None 2013/04/26 12:10:49 7841
2 PTAN1 8166 0 None 2013/04/26 12:10:49 7849
3 PSSO1 3474 0 None 2013/04/26 12:10:49 7842
4 XVST1 14237 0 None 2013/04/26 12:10:49 7843
5 XAH01 14842 0 None 2013/04/26 12:10:49 7844
6 XTAN1 5930 0 None 2013/04/26 12:10:49 7847
7 XSSO1 4847 0 None 2013/04/26 12:10:49 7845
8 RVST1 14854 0 None 2013/04/26 12:10:49 7846

This provides the ports open and being used by the GoldenGate processes including the Extract, Pump and Replicat processes.

GGSCI (ggsdb01) 9> send manager getportinfo detail
Sending GETPORTINFO, request to MANAGER ...

Dynamic Port List

Starting Index 0
Entry Port Error Process Assigned Program
----- ----- ----- ---------- ------------------- -------
0 15010 0
1 15011 0
2 15012 0
3 15013 0
4 15014 0
5 15015 0
6 15016 0
7 15017 0
8 15018 0
9 15019 0
10 15020 0

This provides info on the trail files that may qualify for purging, for all processes managed by the Manager process.

GGSCI (ggsdb01) 10> send manager getpurgeoldextracts

PurgeOldExtracts Rules
Fileset MinHours MaxHours MinFiles MaxFiles UseCP
/u01/VST/ggs/dirdat/* 1 0 1 0 Y
Extract Trails
Filename Oldest_Chkpt_Seqno IsTable IsVamTwoPAHseCommit
/u01/VST/ggs/dirdat/p3 3
/u01/VST/ggs/dirdat/pb 2
/u01/VST/ggs/dirdat/p2 1
/u01/VST/ggs/dirdat/xd 6
/u01/VST/ggs/dirdat/xa 14
/u01/VST/ggs/dirdat/pa 3
/u01/VST/ggs/dirdat/xn 0
/u01/VST/ggs/dirdat/pn 0
/u01/VST/ggs/dirdat/xs 8
/u01/VST/ggs/dirdat/p1 1

Monitoring and Alerting MGR process

After starting the MGR you can place the alerting to make sure you know if the process goes down. Simply place script in the crontab or another scheduler to be executed at the interval that best fits your needs.

GoldenGate Alerting and Monitoring Script

Simple Replication Series

GoldenGate Replication Pre-requisites
GoldenGate Manager
GoldenGate Classical Extract
GoldenGate Pump
GoldenGate Replicat
Uni-directional Replication Summary