OracleGoldenGate tutorial 1: Introduction and Installation

The Manager process must run on the source and target, and be started before the Extract and Replicat processes. Without the OGG process, other operations cannot be performed. It manages to start Oracle

The Manager process must run on the source and target, and be started before the Extract and Replicat processes. Without the OGG process, other operations cannot be performed. It manages to start Oracle

Read navigation

1. Description

1. Download and documentation

: I downloaded Oracle GoldenGate 12.1.2.1.0 version of Oracle GoldenGate V12.1.2.1.0 for Oracle on Linux x86-64 (336 MB)
Online document address:
Introduction to Oracle GoladenGate: https://docs.oracle.com/goldengate/1212/gg-winux/GWUAD/wu_about_gg.htm#GWUAD110
Official Oracle Installation Tutorial:
Step by step GoldenGate configuration: https://sachinichake.wordpress.com/2013/05/08/step-by-step-golden-gate-configuration

1. 2. Resource Description

1. 3. Component Description

1.3.1.Manager

The Manager process must run on the source and target, and be started before the Extract and Replicat processes. No OGG process can perform other operations, it manages starting Oracle GoldenGate processes, starting dynamic processes, allocating ports to GoldenGate processes, managing trail files, creating events, and reporting errors and diagnoses;

1.3.2.Extract

Extract can run on both ends at the source end or at the same time according to system and business needs to Extract and capture system change data; it can be configured to initialize data loading (loading static data directly from the data source) and synchronize the change data between the source and the server after a certain time point (from online logs or archive logs to capture the changed data ), it can also extract and capture DDL data from systems that support DDL changes;
When configured as data synchronization, the extract process extracts and captures any DML and DDL (Additional configuration required) operations on the objects configured in the extract configuration file. The extract process records these operations, until the user commits or rolls back the transaction; when the user receives a rollback, extract revokes these records; when the user receives a (commit) operation, extract Process records store these operations into one or more trail files and send them to the target end as queues to ensure data transmission speed and data consistency.

1.3.3.Data Pumps

Data Pumps is the second type of GoldenGate extract configuration. If Data Pump is not used, the extract process must send the captured operation Data to the target trail. If Data Pump is configured, the extract process extracts captured Data and writes it to the trail. data pump reads the trail and sends the trail to the target trail through the network. Data pump enhances the availability of data extraction and capture at the source and target ends. The main advantages are: 1. protection of network transmission failure and target failure; 2. it can implement complex data filtering and conversion; 3. multiple data sources can be combined to the target end; 4. you can synchronize one source data to multiple target terminals.

1.3.4.Replicats

The Replicat process runs on the target end to read the tail file, reconstruct DML and DDL, and apply them to the target database. Replicat compiles the SQL statement once. When the variable value is different, the compiled SQL statement is used repeatedly; the Replicat process can configure initialization data loading like the extract process (loading static data directly from the data source) and synchronize the change data between the source and the server after a certain time point (from online logs or archive logs to capture the changed data );

1.3.5.Trails

The trail file stores the captured change data. The trail may exist on the disk of the source system, on the disk of the target system, or on the internal media or related system of the system according to the GoldenGate configuration; using the trail file storage to extract captured data can be independent of the extract or replicat process. You can have more options for processing data and when to reach the target end, for example, you may configure extraction and save at the same time, and then send data to the target end later. The trail file can be created by running the add rmttrail or add exttrail command as needed by the process. The file name is 8 characters long, you can specify two characters at creation, and then fill in the other six sequence characters by GoldenGate. The sequence characters are from 000000 to 999999. For example, if you specify two characters as 'tr' at creation ', goldenGate creates a tr120001 file to save the captured data. The file name is unique and saved in the GoldenGate_home \ dirdat directory.

1.3.6.Checkpoints

Checkpoint stores the Checkpoint location for reading and writing data from a file. It is used to restore and restore data. Checkpoint ensures that changes occur and submits data (commit) the data is captured by extract extraction and applied to the target by the replicat process; ensure that errors occur when the system, network, or GoldenGate needs to restart the process will not cause data loss; in complex synchronization configurations, checkpoints enables multiple extract and replicat processes to read data from the same trail set.

1.3.7.Collector

Collector is the target background process. By default, the source extract process initializes TCP/IP to connect to the target collector process, but because GoldenGate is configurable, in some cases, you may need to configure and initialize collector on the target end. For example, if the target end synchronizes the time zone, but the source end has a lower time zone than the target end. Functions of collector: 1. scan and bind an available port to the request's extract process based on the request from the source extract process. 2. receives the source extract to extract the trail and writes it to the target trail file. mgr automatically starts the collector process. When the Source sends a network request, GoldeGate users cannot interact with it. Collector can only accept one extract process (one-to-one) at a time and terminate with the termination of extract.

2. Directory and environment variable settings

Install the source end in the/u01/app/product/ogg_src directory on the same machine, and install the target end in the/u01/app/product/ogg_trg directory;

[Oracle @ sywu ~] $ Mkdir-p/u01/app/product/ogg_src [oracle @ sywu ~] $ Mkdir-p/u01/app/product/ogg_trg [oracle @ sywu ~] $ Ls/u01/app/product11.2.3 ogg_src ogg_trg

To install GoldenGate in Linux, you must configure ORACLE_SID, ORACLE_HOME, and LD_LIBRARY_PATH;

Export ORACLE_BASE =/u01export ORACLE_HOME = $ ORACLE_BASE/app/product/11.2.3/db_1export ORACLE_SID = sydbexport LD_LIBRARY_PATH = $ ORACLE_HOME/lib: $ ORACLE_HOME/lib32alias sqlplus = 'rlwrap sqlplus 'alias rman = 'rlwrap rman' alias nmon = '/usr/nmon/others' alias bbed = 'rlwrap bbed' PATH = $ PATH: $ HOME /. local/bin: $ HOME/bin: $ ORACLE_HOME/OPatchexport PATH

Note: The data operating system version, database version, and Oracle GoldenGate version bit type must be consistent, either 32bit or 64bit;

3. Install GoldenGate

3. 1. Install the source GoldenGate [oracle @ sywu ~] $ Unzip 121210_fbo_ggs_Linux_x64_shiphome.zip-d/tmp [oracle @ sywu ~] $/Tmp/fbo_ggs_Linux_x64_shiphome/Disk1/runInstaller

Select the corresponding GoldenGate option based on the database version;

Change the GoldenGate Software installation location, install it in the/u01/app/product/ogg_src directory, check whether the database installation location is correct, and configure the port;

Check the installation information and confirm the installation;

In this way, the installation of the source is complete.

3. 2. Install the target GoldenGate