Oracle Goldengate Architecture

Hi,

 

I will tell Oracle Goldengate architecture in this post.

 

We can replicate the records of the transactions made on the source database to the target databases with Oracle GoldenGate, we can replicate in real time or on a delayed basis. This replication may involve all database operations performed in the source database, but can also be performed as a replication of only one seqeunce, table or schema.

One of the key features of Oracle GoldenGate is its hybrid structure. As the source database can be Oracle, the target database can be MS-SQL Server or vice versa. Thanks to its Oracle GoldenGate hybrid structure, it can support replication in cross-platform or database. Examples include; Oracle, MS-SQL, Postgre SQL, MySQL and IBM DB2.

Oracle GoldenGate is installed separately to the source and target servers, and the configurations of the servers can be different. While the processes on the source server are called Extract and Pumper , the processes on the target server are called Collector and Replicat . In addition to these, both sides have the Manager process. You can see this process architecture like following picture.

 

 

 

Now let us explain briefly these terms.

 

Manager: As the name implies, this process is main process and the management process of Oracle GoldenGate. Works on both source and destination servers. The configuration of GoldenGate is managed via this process. Sample; The trail files produced by the Extract process and reporting are under the management of this processes . In order for Extract, Pumper and Replicat processes to work, the Manager must be run. The length of time the trail files produced by the Extract process are stored is checked through the Manager process.

Extract: This process is running on the source database is responsible for capturing the records of all transactions performed in the database. These records are collected primarily from the Online Redolog (removed from RBA numbers) files or from archive files.

 

 

 

Pumper: The task of this process is to send the trail files generated by the Extract process to the target server via the defined 7809 port (TCP / IP) on the Manager service.

Replicat: Replicat process , as the name suggests, is responsible for processing the trail files sent by the Pumper process running on the source server to the target database. You can run incoming trail files in real time (online) or you can operate them in a delayed manner by means of parameters.

Collector: The Collector process is a background service of GoldenGate and only works on the target server. This process is responsible for processing the posted trail files and bringing them into the format that the Replicat process can use.

 

 

 

 

 

 

 

Leave a Reply

Your email address will not be published. Required fields are marked *