Shulou(Shulou.com)06/01 Report--

CHAPTER 3 Chapter 3

Configuring Manager and Network Communications

Configure manager and network communication

This chapter contains the following instructions:

● configure the manager process

● specifies local and remote network communication ports, and all Oracle GoldenGate ports are configurable

Overview of the Manager process

To configure and run the Oracle GoldenGate,manager process, you must run on all Oracle GoldenGate source and target systems, as well as on any intermediate systems that the configuration uses.

The manager process performs the following functions:

● starts the Oracle GoldenGate process

● starts a dynamic process

● starts the Collector process

Port number of the ● management process

● performs queue management

● creates event, error, and threshold reports

Each Oracle GoldenGate installation has one manger. A manager can support multiple Oracle GoldenGate extraction and replication processes.

Assign a local communication port to manager

The Manager process in each Oracle GoldenGate configuration requires a dedicated port for communication between itself and other local Oracle GoldenGate processes.

To specify this port, use the port parameter in the Manager parameters file. Follow these guidelines:

The default port number for ● Manager is 7809. You must specify the default port number (recommended, if there is one) or select a different port.

● the port must be unreserved and unrestricted

Each Manager instance on a ● system must use a different port number

Maintain ports for remote connections through firewalls

If a firewall is used at the Oracle GoldenGate destination, additional ports are required on the target system to receive dynamic TCP/IP traffic from remote Oracle GoldenGate processes. These ports are:

● the port of each Collector process started by the local manager to receive propagated transaction data from the remote online extraction process

The port of the ● replication process that is started by the local manager as part of the remote task. Remote tasks are used for initial loading and refer to the RMTTASK parameter. This port is used for

Receive incoming requests from the remote extraction process

Some additional ports for ● in case they are needed to extend the local Oracle GoldenGate configuration

Ports for ● other Oracle GoldenGate products if they interact with local Oracle GoldenGate instances, as described in the documentation for those products.

To specify these ports, use the DYNAMICPORTLIST parameter in the manger parameter file.

Follow these guidelines:

● you can specify up to 5000 ports using any combination of the following formats:

7830, 7833, 7835

7830-7835

7830-7835, 7839

● ports must be unreserved and unrestricted.

Each manager instance on a ● system must use a different port list

Although not a required parameter, it is strongly recommended that you use DYNAMICPORTLIST for best performance. The Collector process is responsible for finding and binding to available ports and has a known

The list of eligible ports speeds up this process. When there is no DYNAMICPORTLIST (or if not enough ports are specified for it), the collector will try to use port 7840 for remote requests.

If 7840 is not available, Collector increments by 1 until an available port is found. This may delay the acceptance of remote requests. If the Collector process 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. For more information about tcperrs files, see "handling TCP/IP errors" on page 170.

For more information about the list of ports and dynamic ports, see the Oracle GoldenGate Windows and UNIX reference Guide.

Select internet protocol

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

● IPv6 dual-stack

● IPv4 if IPv6 dual-stack is not available IPv4 if IPv6 dual stack is not available

● IPv6

If your network has IPv6 network devices that do not support dual-stack mode, you can use the USEIPV6 parameter 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. When using USEIPV6, the entire network must be compatible with IPv6 to avoid connection failures.

For more information, see the Oracle GoldenGate Windows and UNIX reference Guide.

Recommended manager parameters

The following parameters are optional, but are recommended for manager processes.

For more information about these and other manager parameters, see the Oracle GoldenGate Windows and UNIX reference Guide.

● AUTOSTART: starts the extraction and replication process when Manager starts. This parameter is required in the cluster configuration when the Oracle GoldenGate activity must be in the

It is very useful when the system starts up immediately. (Manager is required as part of the startup routine. You can use multiple AUTOSTART statements in the same parameter file

● AUTORESTART: start the extraction and replication process again after abnormal termination. This parameter is required in the cluster configuration, but it is also useful in the configuration that ensures the continuity of the process

● PURGEOLDEXTRACTS: clears the queue file when Oracle GoldenGate finishes processing. If there is no PURGEOLDEXTRACTS, the cleanup operation will not be performed and the trace file will take up a lot of magnetism.

Disk space. For best results, use PURGEOLDEXTRACTS as the manager parameter, not as the Extract or Replicat parameter

● STARTUPVALIDATIONDELAY | STARTUPVALIDATIONDELAYCSECS:: sets the delay time after manager verifies the running status of the process. Start validation so that Oracle GoldenGate users know that the process failed before generating an error message or process report

● USERID: required if Oracle GoldenGate DDL support is used.

Create a manager parameter file

To configure manager with the required port information and optional parameters, follow these steps to create a parameter file. For more information about Oracle GoldenGate parameter files, see

Chapter 4 on page 25

Be careful

If Oracle GoldenGate resides in a cluster, follow the instructions in the vendor documentation to configure the manager process in the cluster application so that Oracle GoldenGate and other

The application fails over normally together. For more information about installing Oracle GoldenGate in a cluster, see the Oracle GoldenGate installation and setup Guide for your database

1 from the Oracle GoldenGate directory, run the ggsci program to open the Oracle GoldenGate software command interface (GGSCI)

2 in GGSCI, issue the following command to edit the manager parameter file

EDIT PARAMS MGR

3 add parameters to be used for the manager process, one per line. If the parameter statement must span multiple lines, use the ampersand (&) before each line

4. Save and then close the file

Example

The following is a sample manager parameter file that uses required and recommended parameters on a UNIX system

PORT 7809

DYNAMICPORTLIST 7810-7820, 7830

AUTOSTART ER t *

AUTORESTART ER tweets, RETRIES 4, WAITMINUTES 4

STARTUPVALIDATIONDELAY 5

PURGEOLDEXTRACTS / ogg/dirdat/tt*, USECHECKPOINTS, MINKEEPHOURS 2

For more information about these and other manager parameters, see the Oracle GoldenGate Windows and UNIX reference Guide

Starting Manager

Start manager

You must run manager before starting other Oracle GoldenGate processes.

You can start the Manager from the following location:

Command line of any supported operating system for ●

● GGSCI command interface.

Service Mini Program on ● Windows systems (if Manager is installed as a service). Refer to the Windows documentation or your system administrator

● T if the system is part of a Windows cluster, use the cluster management tool, which is the recommended way for manager resources to come online.

Refer to the cluster documentation or system administrator.

Cluster software for ● UNIX or Linux clusters. Refer to the documentation provided by the cluster vendor to determine whether to launch Manager from the cluster or to use GGSCI

Or the command line of the operating system to start Manager. .

Start Manager from the operating system command shell

Mgr param file [report file]

The 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.

Start manager using GGSCI

1 from the Oracle GoldenGate directory, run GGSCI.

two. In GGSCI, issue the following command

START MANAGER

Note that when you start Manager from the command line or GGSCI on Windows Server 2008 with user account control enabled, you will receive a UAC prompt asking you to allow or deny the program to run.

Stop manager

Manager runs indefinitely or until the user stops it. In general, manager should keep running when performing synchronization activities. Manager performs important monitoring and maintenance functions and cannot start a process unless Manager is running.

Stop manager

● on UNIX and Linux (including USS on z/OS), you must use the STOP Manager command in GGSCI to stop Manager.

STOP MANAGER [!]

Location:! Stop the manager without user confirmation

● in a UNIX or Linux cluster, please refer to the documentation provided by the cluster vendor to determine whether to stop Manager from the cluster or use GGSCI.

● on Windows, you can stop manager from the service Mini Program (if manager is installed as a service). Refer to the Windows documentation or your system administrator.

● in a Windows cluster, you must take manager resources offline from Cluster Administrator. If you try to stop Manager from the GGSCI interface

The cluster monitor interprets it as a resource failure and attempts to bring the resource online again. Multiple startup requests through GGSCI will eventually exceed startup

Threshold for the manager cluster resource, and the cluster monitor marks the manager resource as failed.

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.