Shulou(Shulou.com)05/31 Report--

This article introduces the knowledge about "how to configure Manager and network communication in Oracle GoldenGate process". In the actual case operation process, many people will encounter such difficulties. Next, let Xiaobian lead you to learn how to deal with these situations! I hope you can read carefully and learn something!

1. Manager Process Profile

Manager is a controller process used to instantiate Oracle GoldenGate processes, assign ports, and perform file maintenance.

The Manager process, its child processes, and their related programs and files together form an Oracle GoldenGate instance.

Every Oracle GoldenGate installation has a Manager. A single Manager can support multiple extract and copy processes.

The Manager process performs the following functions:

Start the Oracle GoldenGate process

Initiate dynamic processes

Start the Collector process

port number of the administrative process (all ogg ports are configurable)

Trail tracking management

Create event, error and threshold reports

2. Assign a port to Manager for local communication

The Manager process requires a dedicated port to communicate with other local ogg processes.

The default port number for Manager is 7809 and must be specified (default recommended).

Ports must be unreserved and unrestricted.

If multiple instances of ogg exist on the system, each Manager must use a different port number.

GGSCI (rhel7.6-12c as ggsadmin@orcl) 29> EDIT PARAMS MGRPORT 7809

3. Maintain ports for remote connections through firewalls

If you use a firewall on the Oracle GoldenGate target side, you need additional ports on the target side to receive dynamic TCP/IP traffic from remote Oracle GoldenGate processes. These ports are:

Port of each Collector process launched by the local Manager to receive transaction data from remote online Extract processes. When the Extract process sends data to the target, the Manager on the target starts a dedicated Collector process.

Local Manager starts each Replicat port as part of the remote task. Remote tasks are used to initialize the load and are specified using the RMTTASK parameter. This port is used to receive incoming requests from remote Extract processes.

A few extra ports in case you need to extend the native Oracle GoldenGate configuration.

Ports for other Oracle GoldenGate products if they interact with local Oracle GoldenGate instances

To specify these ports, use the DYNAMICPORTLIST parameter in the Manager parameter file:

--Specify multiple ports DYNAMICPORTLIST 7830,7833--Specify range DYNAMICPORTLIST 7830-7835--Specify range and a single port DYNAMICPORTLIST 7830-7835,7839

Although DYNAMICPORTLIST is not a required parameter, it is strongly recommended to use DYNAMICPORTLIST for optimal performance. The Collector process is responsible for finding and binding to available ports, and having a list of known eligible ports speeds up this process.

In the absence of DYNAMICPORTLIST (or if sufficient ports are not specified for it), the collector can use a port range between 7819 and 12818. If the collector runs out of ports in the DYNAMICPORTLIST list, the following occurs:

Manager reports errors in its process reports and Oracle GoldenGate ggserr logs.

Collector retries according to the rules in the Oracle GoldenGate tcperrs file.

4. select Internet Protocol

By default, Oracle GoldenGate selects sockets in the following order of priority to ensure the best chance of a successful connection:

IPv6 dual-stack

If IPv6 dual-stack is not available, use IPv4

IPv6

if device with IPv6 networks in that local network do not support dual stack mode, you can use the USEIPV6 paramete to force Oracle GoldenGate to use IPv6 for all connections. This is a global parameter that applies to all processes of the Oracle GoldenGate instance. With USEIPV6, the entire network must be IPv6 compatible to avoid connection failures.

5. Use the recommended Manager parameters

The following parameters are optional, but recommended for the Manager process:

AUTOSTART: When Manager starts, it automatically starts one or more Extract and Replicat processes using the AUTOSTART parameter. AUTOSTART ensures that no process groups are ignored and synchronization activities begin immediately.

/*AUTOSTART {{EXTRACT | REPLICAT | ER} group_name |JAGENT}EXTRACT: self-starting EXTRACTREPLICAT: self-starting REPLICATER: self-starting EXTRACT and REPLICATJAGENT: auto-starting ogg monitor JAgentgroup_name: valid only for EXTRACT, REPLICAT, ER. JAGENT does not accept group names as input. Specify a group name or wildcard specification for multiple groups. When wildcards are used, Oracle GoldenGate starts all groups on the local system that satisfy the wildcard for the specified process type, except groups in PASSVIE mode. */ AUTOSTART ER *

AUTORESTART: Restart the Extract and Replicat processes after an abnormal termination. This parameter is required in cluster configurations, but is useful in any configuration to ensure processing continues.

/*AUTORESTART {EXTRACT | REPLICAT |ER} group_name[, RETRIES number][, WAITMINUTES minutes][, WAITSECONDS seconds][, RESETMINUTES minutes][, RESETSECONDS seconds]EXTRACT: Autorestart EXTRACTREPLICAT: Autorestart EXTRACT and REPLICATgroup_name: Group name or wildcard specification for multiple groups. When wildcards are used, Oracle GoldenGate starts all groups on the local system that satisfy the wildcard for the specified process type, except for groups in PASSVIE mode. RETRIES number: Maximum number of retries, default is 2. The first attempt by Manager to restart the process does not count, i.e. when number=2,Manager will attempt to restart the process 3 times. WAITMINUTES | WAITSECONDS {minutes |seconds}: The amount of time, in minutes or seconds, paused between detecting an abnormal process termination and restarting the process. Use this option to delay a restart until the necessary resources are available or another event occurs. The default delay is 2 minutes or 120 seconds. RESETMINUTES | RESETSECONDS {minutes |seconds}: The time window (in minutes or seconds) within which the number of retries is counted. The default is 120 minutes (2 hours) or 7200 seconds. When the time expires, the retry count returns to zero. */ AUTORESTART EXTRACT *, RETRIES 3, WAITMINUTES 5, RESETMINUTES 60

PURGEOLDEXTRACTS: Purges trace files when Oracle GoldenGate finishes processing them. Without PURGEOLDEXTRACTS, cleanup is not performed and trace files take up a lot of disk space. For best results, use PURGEOLDEXTRACTS as the Manager parameter and not as the Extract or Replicat parameter.

PURGEOLDEXTRACTS

（4）STARTUPVALIDATIONDELAY |STARTUPVALIDATION DELAYCSECS: Sets a delay time after which Manager verifies the status of processes started with the START EXTRACT or START REPLICAT command. If the process does not run after the specified delay time, an error message is displayed at the GGSCI prompt.

/*STARTUPVALIDATIONDELAY seconds |STARTUPVALIDATIONDELAYCSECS centuries default is 0 seconds, does not detect process start status STARTUPVALIDATIONDELAY seconds: specifies delay in seconds STARTUPVALIDATIONDELAYCSECS centuries: specifies delay in centiseconds */STARTUPVALIDATIONDELAYCSECS 10

6. Create Manager parameter file

--01. Run GGSCI program in ogg directory to enter GGSCI interface [oracle@rhel7.6-12c:/ggs/app]$ggsci--02. Edit Manager parameter file GGSCI (rhel7.6-12c) 1> EDIT PARAMS MGRPORT 7809DYNAMICPORTLIST 7810-7820, 7830AUTOSTART ER *AUTORESTART EXTRACT *, RETRIES 3, WAITMINUTES 5, RESETMINUTES 60 STARTUPVALIDATION DELAY 2USERIDALIAS sadminPURGEOLDEXTRACTS /ggs/app/dirdat/tt*, USECHECKPOINTS, MINKEEPHOURS 2--03. Save (same as linux vim)

7. start the Manager

There are two ways to start Manager:

Method 1: Through the operating system shell

/*mgr paramefile parameter_file [reportfile report_file]mgr:manager program paramefile parameter_file:Manager parameter file, default in dirprm/mgr.prmreportfile report_file: reportfile parameter is optional and can be used to store Manager process reports in a location other than the default location of the dirrpt directory in the Oracle GoldenGate installation location. */ mgr paramfile /ggs/app/dirprm/mgr.prm --foreground run mgr paramfile /ggs/app/dirprm/mgr.prm & --background run

Method 2: Through ggsci

[oracle@rhel7.6-12c:/ggs/app]$ggsciGGSCI (rhel7.6-12c) 1> start mgrManager started.GGSCI (rhel7.6-12c) 2> info mgrManager is running (IP port TCP:rhel7.6-12c.7809, Process ID 94811).

8. Stop Manager

Unix/Linux environments:

GGSCI (rhel7.6-12c) 6> stop mgrManager process is required by other GGS processes.Are you sure you want to stop it (y/n)? ySending STOP request to MANAGER ... Request processed.Manager stopped.GGSCI (rhel7.6-12c) 4> stop mgr ! Sending STOP request to MANAGER ... Request processed.Manager stopped.--! indicates no user determination

Windows environment:

If Manager is installed as a service, it can be stopped in the Services Panel;

If Manager is not installed as a service, the GGSCI interface needs to stop

STOP MANAGER"How to configure Manager and network communication in Oracle GoldenGate process" is introduced here. Thank you for reading it. If you want to know more about industry-related knowledge, you can pay attention to the website. Xiaobian will output more high-quality practical articles for everyone!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.