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

ORA-39014: One or more workers have prematurely exited.ORA-00018: maximum number of sessions exceeded

ERROR: I was Performing a full database import and during the import I faced the below error. ORA-39014: One or more workers have prematurely exited. ORA-39029: worker 6 with process name "DW07" prematurely terminated ORA-31672: Worker process DW07 died unexpectedly. Job "SYSTEM"."SYS_IMPORT_FULL_04" stopped due to fatal error at 00:59:40 ORA-39014: One or more workers have prematurely exited. SOLUTION:  Run the import with fewer parallel processes, like PARALLEL=2 instead of 8. I was able to run the import successfully. NOTE 1: This errors occurs when there are less session allocation in the database. check the session,process parameters and increase them accordingly. To avoid such errors again. NOTE 2 : Note: Increasing processes parameter increases the amount of shared memory that needs to be reserved & the OS must be configured to support the larger amount of shared memory. So here we first need to increase the Memory & SG...
Post a Comment
Read more

ORA-01143: cannot disable media recovery - file 1 needs media recovery

I got a request from the client - To flashback the database to the existing restore point & disable flashback and archive log mode for database UATB. Here I came a cross error - ORA-01143. I followed the below steps. 1. SQL> select name from v$database; NAME ------------ UATB 2. SQL> SELECT NAME FROM V$RESTORE_POINT WHERE GUARANTEE_FLASHBACK_DATABASE='YES' ORDER BY TIME; NAME --------- UATB_COPY Here I'm going to restore the database to the above restore point. NOTE: The flashback database restore has to be done in MOUNT stage of the database. SQL> select name from v$database; NAME --------- UATB SQL> shut immediate; Database closed. Database dismounted. ORACLE instance shut down. SQL> startup mount ORACLE instance started. Total System Global Area  612368384 bytes Fixed Size                  1250428 bytes Variable Size             167775108 bytes ...
2 comments
Read more