Overview of the Oracle GoldenGate Architecture

Oracle GoldenGate can be configured for the following purposes:

• A static extraction of data records from one database and the loading of those records to another database.

• Continuous extraction and replication of transactional Data Manipulation Language (DML) operations and data definition language (DDL) changes (for supported databases) to keep source and target data consistent

• Extraction from a database and replication to a file outside the database.

Oracle GoldenGate is composed of the following components:

• Extract

• Data pump

• Replicat

• Trails or extract files

• Checkpoints

• Manager

• Collector

Figure below represents the coherent construction modeling of Oracle GoldenGate for beginning information loads and for the synchronization of DML and DDL operations. This is the essential arrangement. Varieties of this model are suggested relying upon business needs.

Architecture of Oracle GoldenGate

Overview of Extract

The Extract procedure is the extraction (catch) system of Oracle GoldenGate. Concentrate keeps running on a source framework or on a downstream database, or both, contingent upon the database and the usage necessities.

You can arrange Extract in one of the accompanying ways:

Starting burdens: For beginning information burdens, Extract concentrates (catches) a present, static arrangement of information straightforwardly from their source objects.

Change synchronization: To keep source information synchronized with another arrangement of information, Extract catches DML and DDL operations after the introductory synchronization has occurred.

Concentrate catches from an information source that can be one of the accompanying:

Source tables, if the run is a starting burden.

The database recuperation logs or exchange logs, (for example, the Oracle re-try logs or SQL/MX review trails). The real system for catching from the logs changes relying upon the database sort. Case in point, Oracle GoldenGate for Oracle offers a coordinated catch mode, in which Extract interfaces straightforwardly with a database logmining server that mines the Oracle exchange stream. See "About Integrated Capture" in Installing and Configuring Oracle GoldenGate for Oracle Database for more data about incorporated catch.

An outsider catch module. This technique gives a correspondence layer that passes information and metadata from an outside API to the Extract API. The database merchant or an outsider seller gives the parts that concentrate the information operations and pass them to Extract.

At the point when arranged for change synchronization, Extract catches the DML and DDL operations that are performed on articles in the Extract arrangement. Concentrate stores these operations until it gets confer records or rollbacks for the exchanges that contain them. At the point when a rollback is gotten, Extract tosses the operations for that exchange. At the point when a confer is gotten, Extract continues the exchange to plate in a progression of documents called a trail, where it is lined for engendering to the objective framework. The majority of the operations in every exchange are composed to the trail as a consecutively sorted out exchange unit. This outline guarantees both pace and information uprightness.

Note:

Concentrate overlooks operations on items that are not in the Extract design, despite the fact that the same exchange might likewise incorporate operations on articles that are in the Extract setup.

Different Extract procedures can work on distinctive articles in the meantime. Case in point, two Extract procedures can separate and transmit in parallel to two Replicat forms (with two ingenuity trails) to minimize target dormancy when the databases are extensive. To separate among diverse Extract forms, you dole out every one a gathering name.