Classic vs Integrated Capture in Oracle GoldenGate: Key Differences Explained

 Oracle GoldenGate is a robust solution for real-time data replication, offering flexibility to suit a wide range of enterprise database environments. One of the fundamental decisions when implementing GoldenGate is choosing between Classic Capture and Integrated Capture. While both approaches serve the same purpose—capturing database changes for replication—they differ significantly in performance, scalability, and compatibility with modern Oracle features such as RAC, multitenant architecture, and TDE (Transparent Data Encryption).

In this article, we will explore these differences in depth, backed with real-world examples to help Oracle DBAs and IT teams make informed decisions. We’ll also cover how to identify whether a GoldenGate extract is Classic or Integrated and which parameters control its behavior. By the end, you’ll understand when to use Classic Capture, when Integrated Capture is the better choice, and how each impacts your replication strategy in live environments.

Classic Capture in Oracle GoldenGate

Classic Capture extracts data changes directly from Oracle redo or archive logs. This approach is suitable for simpler, smaller-scale environments, but it has some limitations.

Key Features

• Performance: Classic Capture can be CPU-intensive and slower with complex data types like LOBs (Large Objects).

• RAC Support: In Oracle RAC, a separate ASM user must be created, and necessary privileges granted to access ASM redo/archive logs. You can alternatively use the TRANLOGOPTIONS DBLOGREADER parameter in the Extract configuration.

• Multitenant Architecture: Not supported; only works at the database level, not PDBs.

• TDE (Transparent Data Encryption): Requires manual configuration.

• Scalability & Parallelism: Single-threaded processing limits scalability; logs are processed sequentially.

• Registration: No registration of the extract process with the database is required.

Identifying Classic Capture

You can check whether a GoldenGate extract is running in Classic Capture mode using the following approaches:

1. Extract Parameter File: Look for parameters like:

   • TRANLOGOPTIONS DBLOGREADER (optional for RAC)

   • Absence of INTEGRATEDPARAMS

   • No REGISTEREXTRACT requirement

2. GGSCI Commands: In GGSCI, run:

   INFO EXTRACT <extract_name>, DETAIL
   

   Classic Capture will show Capture type: Classic and may not reference logical change records (LCRs).

Real-Time Example

A mid-sized retail company running a single Oracle 12c database for their point-of-sale system implemented Classic Capture to replicate sales transactions to a reporting database. While replication worked, they noticed CPU spikes during peak hours due to sequential processing of large LOB fields for receipts and invoices.

Integrated Capture in Oracle GoldenGate

Integrated Capture leverages the Oracle database log mining server to read redo logs and produce Logical Change Records (LCRs). This modern approach is designed for complex and large-scale environments.

Key Features

• RAC Support: Automatically manages threads based on RAC nodes; no manual configuration required.

• Multitenant Architecture: Fully supports replication at the PDB level.

• Registration: Extract process must be registered with the database.

• Scalability & Parallelism: Supports automatic dynamic parallelism, efficiently handling large volumes of data.

• Performance: Ideal for high-volume, complex environments; more efficient than Classic Capture.

• Archivelog Management: Archivelogs remain until processed; can monitor through DBA_CAPTURE.

• Memory Allocation: Streams pool size is critical; Oracle recommends ~1.25 GB per Integrated Extract process.

• 
  

Identifying Integrated Capture

1. Extract Parameter File: Look for parameters like:

   • INTEGRATEDPARAMS pointing to database registration info

   • REGISTEREXTRACT command required to register the extract

   • Optional: STREAMS_POOL_SIZE configured for LCR processing

2. GGSCI Commands: In GGSCI, run:

   INFO EXTRACT <extract_name>, DETAIL
   

   Integrated Capture will display Capture type: Integrated and reference Logical Change Records (LCRs).

3. Database Views: Check DBA_CAPTURE or DBA_CAPTURE_PREPARED to see active integrated capture sessions.

Real-Time Example

A global e-commerce company with an Oracle 19c RAC database uses Integrated Capture to replicate orders and inventory updates across multiple data centers. Integrated Capture automatically scales with RAC nodes and handles multiple PDBs without extra configuration. As a result, replication latency is minimized even during flash sales with high transaction volumes.

---

Key Parameters Affecting Capture Mode

Classic vs Integrated Capture – Side-by-Side Comparison

Quick Takeaways

• Classic Capture is suitable for smaller, non-RAC databases; Integrated Capture scales automatically.

• Integrated Capture handles LOBs and large transactions more efficiently.

• Use GGSCI and extract parameter files to identify capture type.

• Classic Capture requires manual RAC and TDE configuration.

• Integrated Capture supports multitenant architecture and automatic parallelism.

• Real-time examples show Integrated Capture is preferred in enterprise setups.

• Key parameters like INTEGRATEDPARAMS, TRANLOGOPTIONS, and STREAMS_POOL_SIZE determine mode and performance.

FAQs

1. How do I know if my GoldenGate extract is Classic or Integrated?
   Check GGSCI INFO EXTRACT output and parameter file. Look for INTEGRATEDPARAMS for Integrated Capture.

2. Which parameters affect RAC support?
   TRANLOGOPTIONS DBLOGREADER for Classic; Integrated automatically manages RAC threads.

3. Is Classic Capture supported in multitenant databases?
   No, only Integrated Capture supports PDB-level replication.

4. Do I need to allocate memory for Integrated Capture?
   Yes, set STREAMS_POOL_SIZE (recommended 1.25 GB per IE process).

5. Can I switch from Classic to Integrated Capture easily?
   Yes, but you must register the extract and adjust parameters for LCR handling.

Have you experienced challenges distinguishing Classic and Integrated Capture in your Oracle GoldenGate setup? Share your insights, tips, or troubleshooting stories in the comments! If you found this article useful, please share it with your DBA peers - it could save hours of configuration headaches.