GoldenGate for Oracle System Requirements

Supported platforms

Supported Oracle Database versions

The following Oracle Database versions are supported in the current Oracle GoldenGate 10.4

Oracle 8i (DML support only)

Oracle 9.1 and 9.2 (DML and DDL support)

Oracle 10.1 and 10.2 (DML and DDL support)

Oracle 11g (DML and DDL support)

Supported Operating System Platforms

GoldenGate supports almost all mainstream operating systems

Windows 2000,200 3, XP

Linux

Sun Solaris

HP NonStop

HP-UX

HP TRU64

IBM AIX

IBM z/OS

Memory Requirements

According to the working principle and architecture of Oracle GoldenGate, a set of GoldenGate software must be installed on each data source and target, and a GoldenGate instance must be started separately, A GoldenGate instance is a management process, which is also the main control process during the operation of the entire GoldenGate instance.

GoldenGate is controlled by the operating system memory usage, rather than by the GoldenGate program. The GoldenGate process allocates the corresponding virtual memory from the OS as needed.

The GoldenGate GGSCI command interface tool supports 5000 concurrent Extract and Replicat processes for each GoldenGate instance.

Each Extract and Replicat process requires about 25-55 MB of memory, depending on the size of the transaction and the number of concurrent transactions.

Therefore, according to the preceding two conditions, GoldenGate's requirements for the operating system memory mainly depend on the number of Extract and Replicat processes.

DISK Space Requirements

Installation File: The GoldenGate compression package downloaded from the Oracle official website is about 50 ~ 150 MB, so you need to increase the extra resource overhead before allocating disk space. Of course, after installation, you can delete the compressed package.

Working directory: the working directory (working directories and binaries) of each GoldenGate instance, which requires about 40 MB of space, if you want to install multiple GoldenGate instances on the same Server to different directories/file systems, you need to allocate multiple times of space. When considering space allocation, this factor also needs to be considered.

Auxiliary space: This space is mainly used to store GoldenGate Trails, which contains work data. The consumption of this part of space depends on the Trail and the amount of data to be processed. This part of space needs to be planned based on the actual size of the database system and the log volume generated every day. We recommend that you save the GoldenGate queue file for 7-10 days.

For the RAC environment: the software and working directory of GoldenGate must be configured in the shared disk environment to ensure that all nodes are available. The GoldenGate process can be started from any node, when one of the nodes has an exception, you can start the remaining nodes without modifying any configuration parameters. otherwise, if you run on a single node, you need to share the archived logs from the remaining nodes and load them to the GoldenGate node through some technology.

At the same time, GoldenGate requires that all nodes must maintain clock synchronization, and that all RAC nodes and node nodes running the extract process must also maintain clock synchronization. Because GoldenGate compares the local system time with the commit timestamp. Therefore, this setting cannot be ignored. Otherwise, Data Replication disorder may occur.

Temporary space: by default, GoldenGate stores the temporary data in transaction processing in the dirtmp subdirectory. if the transaction is large, the directory may grow rapidly. To avoid data extraction failures due to I/O competition and insufficient temporary space, we recommend that you use the CACHEDIRECTORY option of the CACHEMGR parameter to save dirdat (directory of the trail file) the directory and dirtmp directory are deployed on different disks.

Network requirements

Configure IP or DNS

GoldenGate uses the host name or IP address for connection, so it is easier to use the host name.

GoldenGate requires unrestricted and free TCP/IP ports:

A port is used for communication between two GoldenGate Manager processes (for example, the Source Manager process and the Target Manager process)

Port range used for local GoldenGate inter-process communication: this port is not used

Configure the firewall to allow requests from the GoldenGate Port

Other programs

√ Before installing GoldenGate on a Windows system, install and configure the Microsoft Visual C ++ 2005 SP1 Redistributable Package. make certain it is the SP1 version of this package, and make certain the get the right bit version for your server.

This package installruntime components of Visual C ++ Libraries. For more information, and to download this package, go to http://www.microsoft.com.

GoldenGate fully supports virtual machine environments created with any license alization software on any platform. When installing GoldenGate into a virtual

Machine environment, select a GoldenGate build that matches the database and the operating system of the virtual machine, not the host system. For example, on

Windows system with a RHAS 4.0 virtual machine running Oracle11g, you wocould install the GoldenGate RHAS 4.0 build for Oracle 11g, just as you wocould on an actual

Operating system permission requirements

Use the Administrator account to install GoldenGate on windows.
You can download the Oracle repository installed on the Microsoft system of the Itanium platform from the Microsoft official website. This file contains the VisualStudio dlllibrary required by goldengate on the Itanium platform. If vcredist_ia64.exe is not installed, the following error will be reported:

"The application failed to initialize properly (0xc0150002). Click on OK

To terminate the application.

When GoldenGate is installed on linux/Unix platforms, the user must be a member of the dba group and have read and write permissions on the directory.

1 2 Next Page