I Additional Configuration Steps for Using Classic Capture

This chapter contains additional configuration and preparation requirements that are specific only to Extract when operating in classic capture mode.

These requirements supplement the basic configuration requirements documented in Configuring Capture in Classic Mode .

Topics:

• Configuring Oracle TDE Data in Classic Capture Mode
  This section does not apply to Extract in integrated capture mode.
• Using Classic Capture in an Oracle RAC Environment
  The following general guidelines apply to Oracle RAC when Extract is operating in classic capture mode.
• Mining ASM-stored Logs in Classic Capture Mode
  This topic covers additional configuration requirements that apply when Oracle GoldenGate mines transaction logs that are stored in Oracle Automatic Storage Management (ASM).
• Ensuring Data Availability for Classic Capture
  To ensure the continuity and integrity of capture processing when Extract operates in classic capture mode, enable archive logging.
• Configuring Classic Capture in Archived Log Only Mode
  You can configure Extract to read exclusively from the archived logs. This is known as Archived Log Only (ALO) mode.
• Configuring Classic Capture in Oracle Active Data Guard Only Mode
  You can configure Classic Extract to access both redo data and metadata in real-time to successfully replicate source database activities using Oracle Active Data Guard. This is known as Active Data Guard (ADG) mode.
• Avoiding Log-read Bottlenecks in Classic Capture
  When Oracle GoldenGate captures data from the redo logs, I/O bottlenecks can occur because Extract is reading the same files that are being written by the database logging mechanism.