1. Home
  2. Knowledge Base
  3. GoldenGate
  4. GoldenGate Tutorial 3 – Configuring the Manager process

GoldenGate Tutorial 3 – Configuring the Manager process

The Oracle GoldenGate Manager performs a number of functions like starting the other GoldenGate processes, trail log file management and reporting.

The Manager process needs to be configured on both the source as well as target systems and configuration is carried out via a parameter file just as in the case of the other GoldenGate processes like Extract and Replicat.

After installation of the software, we launch the GoldenGate Software Command Interface (GGSCI) and issue the following command to edit the Manager parameter file


The only mandatory parameter that we need to specify is the PORT which defines the port on the local system where the manager process is running. The default port is 7809 and we can either specify the default port or some other port provided the port is available and not restricted in any way.

Some other recommended optional parameters are AUTOSTART which which automatically start the Extract and Replicat processes when the Manager starts.

The USERID and PASSWORD parameter and required if you enable GoldenGate DDL support and this is the Oracle user account that we created for the Manager(and Extract/Replicat) as described in the earlier tutorial.

The Manager process can also clean up trail files from disk when GoldenGate has finished processing them via the PURGEOLDEXTRACTS parameter. Used with the USECHECKPOINTS clause, it will ensure that until all processes have fnished using the data contained in the trail files, they will not be deleted.

The following is an example of a manager parameter file

[oracle@redhat346 ggs]$ ./ggsci

Oracle GoldenGate Command Interpreter for Oracle
Version Build 002
Linux, x64, 64bit (optimized), Oracle 11 on Sep 17 2009 23:51:28

Copyright (C) 1995, 2009, Oracle and/or its affiliates. All rights reserved.


PORT 7809
USERID ggs_owner, PASSWORD ggs_owner

The manager can be stopped and started via the GSSCI commands START MANAGER and STOP MANAGER .

Information on the status of the Manager can be obtained via the INFO MANAGER command

GGSCI (devu007) 4> info manager

Manager is running (IP port devu007.7809).

Coming Next – Configuring an Online Extract and Replicat Group …..

The following two tabs change content below.

Gavin Soorma

Latest posts by Gavin Soorma (see all)

Updated on June 2, 2021

Was this article helpful?

Related Articles


  1. Hi I’ve been following all the steps but I have a problem with the manager
    When I execute:
    ggsci> start manager

    A very window appears and goes very quick, then I execute:
    ggsci> info manager
    Manager is Down!

    How could I resolved the problem?



  2. Hi – you can get some more details as to why the manager is failing to start – try VIEW REPORT MGR or VIEW GGSEVT – let me know if you can pick anything as to why the manager is not starting from running these commands

  3. Hi, If the “view ggsevt” command doesn’t show anything unusual but the manager refuses to start and bind to any port.
    “2011-02-07 14:44:02 INFO OGG-00987 Oracle GoldenGate Command Interpreter for Oracle: GGSCI command (oracle): edit params mgr.
    2011-02-07 14:45:00 INFO OGG-00987 Oracle GoldenGate Command Interpreter for Oracle: GGSCI command (oracle): start manager.”

    And the params-fil for the manager is:
    “port 7809
    userid ggs_owner, password ggs_owner
    purgeoldextracts /opt/goldengate/dirdat/ex, usecheckpoints”

    what can the problem be (using

  4. Very good explanation!!!!!! I wish you add some more . Basic steps to troubleshoot MGR issues.

Leave a Comment