CONFIGURING THE MANAGER PROCESS
CONFIGURING THE MANAGER PROCESS
i)The Oracle GoldenGate Manager performs a number of functions like starting
the other GoldenGate processes, trail log file management and reporting.
ii)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.
iii)After installation of the software, we launch the GoldenGate Software
Command Interface (GGSCI) and issue the following command to edit the
Manager parameter file
EDIT PARAMS MGR
iv)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.
v)Some other recommended optional parameters are AUTOSTART which which
automatically start the Extract and Replicat processes when the Manager starts.
vi)The USERID and PASSWORD parameter and required if you enable
GoldenGate DDL support and this is the Oracle user account that we created for
vii)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.
[oracle@redhat346 ggs]$ ./ggsci
GGSCI 2> EDIT PARAMS MGR
PORT 7809
USERID ggs_owner, PASSWORD ggs_owner
PURGEOLDEXTRACTS /u01/oracle/ggs/dirdat/ex, USECHECKPOINTS
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
i)The Oracle GoldenGate Manager performs a number of functions like starting
the other GoldenGate processes, trail log file management and reporting.
ii)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.
iii)After installation of the software, we launch the GoldenGate Software
Command Interface (GGSCI) and issue the following command to edit the
Manager parameter file
EDIT PARAMS MGR
iv)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.
v)Some other recommended optional parameters are AUTOSTART which which
automatically start the Extract and Replicat processes when the Manager starts.
vi)The USERID and PASSWORD parameter and required if you enable
GoldenGate DDL support and this is the Oracle user account that we created for
vii)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.
[oracle@redhat346 ggs]$ ./ggsci
GGSCI 2> EDIT PARAMS MGR
PORT 7809
USERID ggs_owner, PASSWORD ggs_owner
PURGEOLDEXTRACTS /u01/oracle/ggs/dirdat/ex, USECHECKPOINTS
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
Comments
Post a Comment