Skip to main content

Differences Between Classic and Integrated Capture in Oracle GoldenGate

  

Differences Between Classic and Integrated Capture in Oracle GoldenGate

Classic Capture:

In Classic Capture mode, the Oracle GoldenGate Extract process captures data changes directly from Oracle redo or archive log files. In Oracle RAC environments, a separate ASM user must be created, and the necessary privileges must be granted to access the logs in ASM redo/archive. Alternatively, you can use the TRANLOGOPTIONS DBLOGREADER parameter in the Extract configuration for Classic Capture in a RAC setup.

  • Performance: Classic Capture can be CPU-intensive and is generally slower when dealing with complex data types, such as LOBs (Large Objects).
  • Multitenant Architecture: Not supported.
  • RAC Support: Requires manual specification of threads based on the number of RAC nodes.
  • TDE (Transparent Data Encryption): More manual configuration is needed for TDE setups.
  • Scalability: Less scalable in larger environments due to its single-threaded processing nature.
  • Parallelism: Not supported; it processes redo logs sequentially in a single-threaded manner.
  • Registration: No need to register the extract process with the database in Classic Capture.

Integrated Capture:

In Integrated Capture mode, the database log mining server reads redo logs and captures changes as Logical Change Records (LCRs), which are then accessed by the GoldenGate Extract process. Integrated Capture is closely integrated with Oracle databases and requires no additional steps for RAC environments, as it automatically manages threads and configurations based on the nodes.

  • RAC Support: No need to specify threads; it dynamically manages them based on the number of RAC nodes.
  • Multitenant Architecture: Fully supported, allowing for replication at the PDB (Pluggable Database) level.
  • Registration: The extract process must be registered with the database.
  • Scalability: Supports automatic dynamic parallelism, allowing for efficient processing of large volumes of data while ensuring transactional consistency.
  • Performance: Integrated Capture is preferred for modern, large-scale, or complex environments due to its superior scalability and performance.

Archivelog Management: Archivelog files will remain until the LogMiner process has processed them. Details can be viewed in the DBA_CAPTURE view.

Memory Allocation: For Integrated Extract, it is essential to allocate memory under the streams_pool_size parameter. The Oracle recommended size for streams_pool_size for each Integrated Extract (IE) process is 1.25 GB.

 

Comments

Post a Comment

Popular posts from this blog

Issues and Solutions for Oracle 19c Grid Infrastructure Installation

     Common Issues and Solutions for Oracle 19c Grid Infrastructure Installation •       Check Log Files for Details Oracle installation issues often provide valuable clues in the log files. If the installer seems stuck or fails, check the following logs: ▪ Install log : /u01/app/oraInventory/logs/installActions<date>.log •       ▪ Grid Infrastructure log : $ORACLE_BASE/cfgtoollogs/ •         •       These logs can provide error messages and help identify the exact issue. •         •        Check Permissions and Ownership Verify that the Oracle Grid Infrastructure installation directories have the correct ownership and permissions. •        For example: •        Make sure the grid user has permission to write to the directories where the i...
Post a Comment
Read more

CHANGING DBID FOR ORACLE DATABASE 11G

C:\Users\computer>sqlplus SQL*Plus: Release 11.1.0.7.0 - Production on Thu Sep 10 21:03:33 2013 Copyright (c) 1982, 2008, Oracle.  All rights reserved. Enter user-name: sys as sysdba Enter password: Connected to: Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production With the Partitioning, OLAP, Data Mining and Real Application Testing options SQL> select dbid from v$database;       DBID ---------- 2188161033 SQL> exit Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production With the Partitioning, OLAP, Data Mining and Real Application Testing options C:\Users\computer>nid DBNEWID: Release 11.1.0.7.0 - Production on Thu Sep 10 21:04:44 2013 Copyright (c) 1982, 2007, Oracle.  All rights reserved. Keyword     Description                    (Default) ---------------------------------------------------- TARGET ...
Post a Comment
Read more

How to Improve Oracle Data Pump Performance - IMPDP

  How to Improve Oracle Data Pump Performance:- Use Parallelism : Set the PARALLEL parameter to at least 2 * number of CPUs . This allows multiple worker processes to perform tasks simultaneously, speeding up both export and import processes. Example: PARALLEL=4 for a system with 2 CPUs. Perform Import Using NETWORK_LINK : Use the NETWORK_LINK parameter to import data directly from the source database. This method is particularly helpful when space is constrained, as it streams the data without needing to generate dump files on the source. It can also reduce time compared to exporting and then importing, as data is streamed directly from the source to the target database. Disable Archivelog Mode (Standalone Databases) : For standalone databases, temporarily disable archive logging during the import process. Import operations can generate a lot of redo logs, slowing down the import. Disabling...
Post a Comment
Read more