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.
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 The default manager port is 7809.
To manually start up the process the following command can be run from the "ggsci" prompt.
In "ggsci" type the below command to stop the manager process.
The above command asks for your confirmation. Type "y" and press enter.
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.
These provide the current status of the Manager process.
Manager is running (IP port ggsdb01.7833).
The SEND command refresh the output directly from memory and show the current state after refreshing.
This provides the ports open and being used by the GoldenGate processes including the Extract, Pump and Replicat processes.
This provides info on the trail files that may qualify for purging, for all processes managed by the Manager 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.