Setting up a Manager process

The Manager process is a key process of a GoldenGate configuration. This process is the root of the GoldenGate instance and it must exist at each GoldenGate site. It must be running on each system in the GoldenGate configuration before any other GoldenGate processes can be started. This recipe explains how to create a GoldenGate Manager process in a GoldenGate configuration.

Getting ready

Before setting up a Manager process, you must have installed GoldenGate binaries. A Manager process requires a port number to be defined in its configuration. Ensure that you have chosen the port to be used for the GoldenGate manager instance that you are going to set up.

How to do it…

In order to configure a Manager process, you need to create a configuration file. The following are the steps to create a parameter file for the Manager process:

1. From the GoldenGate Home directory, run the GoldenGate software command line interface (GGSCI):

   ./ggsci
   

2. Edit the Manager process configuration as follows:

   EDIT PARAMS MGR
   

3. This command will open an editor window. You need to add the manager configuration parameters in this window as follows:

   PORT <PORT NO>
   DYNAMICPORTLIST <specification>
   AUTOSTART ER*
   AUTORESTART ER*, RETRIES 3, WAITMINUTES 3
   PURGEOLDEXTRACTS <specification>
   

   For example:

   PORT 7809
   DYNAMICPORTLIST 7810-7820, 7830
   AUTOSTART ER t*
   AUTORESTART ER t*, RETRIES 4, WAITMINUTES 4
   PURGEOLDEXTRACTS /u01/app/ggate/dirdat/tt*, USECHECKPOINTS, MINKEEPH
   OURS 2
   

4. Save the file and exit the editor window.

5. Start the Manager process by using the following code:

   GGSCI> START MGR
   

How it works…

All GoldenGate processes use a parameter file for configuration. In these files various parameters are defined. These parameters control the way the process functions. The steps to create the Manager process are broadly described as follows:

1. Log in to the GoldenGate command line interface.

2. Create a parameter file.

3. Start the Manager process.

4. When you start the Manager process you will get the following output:

   GGSCI (prim1-ol6-112.localdomain) 2> start mgr
   Manager started.
   

   You can check the status of the Manager process using the status command as follows:

   GGSCI (prim1-ol6-112.localdomain) 3> status mgr
   Manager is running (IP port prim1-ol6-112.localdomain.7809).
   

The Manager process performs the following administrative and resource management functions:

• Monitor and restart Oracle GoldenGate processes

• Issue threshold reports, for example, when throughput slows down or when synchronization latency increases

• Maintain trail files and logs

• Report errors and events

• Receive and route requests from the user interface

The preceding parameters specified are defined as follows:

• Port no: This is the port used by the Manager process itself.

• Dynamic port list: Range of ports to be used by other processes in the GoldenGate instance. For example, Extract, Datapump, Replicat, and Collector processes.

• Autostart ER*: To start the GoldenGate processes when the Manager process starts.

• Autorestart ER*: To restart the GoldenGate process in case it fails. The RETRIES option controls the maximum number of restart attempts and the WAITMINUTES option controls the wait interval between each restart attempt in minutes.

• Purgeoldextracts: To configure the automatic maintenance of GoldenGate trail files. The deletion criteria is specified using MINKEEPHOURS/MINKEEPFILES. The GoldenGate Manager process deletes the old trail files which fall out of this criteria.

There's more…

The Manager process can be configured to perform some more administrative tasks. The following are some other key parameters that can be added to the Manager process configuration:

• STARTUPVALIDATONDELAY(Secs): Use this parameter to set a delay in seconds after which the Manager process checks that the processes are started after it starts up itself.

• LAGREPORT: The Manager process writes the lag information of a process to its report file. This parameter controls the interval after which the Manager process performs this function.