1. Oracle GoldenGate Classic Documentation
  2. Oracle GoldenGate Business Solutions
  3. Configuring Oracle GoldenGate for Active-Active Configuration
  4. Preventing Data Looping
  5. Preventing the Capture of Replicat Operations
  6. Preventing the Capture of Replicat Transactions (Oracle)

Preventing the Capture of Replicat Transactions (Oracle)

To prevent the capture of SQL that is applied by Replicat to an Oracle database, there are different options depending on the Extract capture mode:

  • When Extract is in classic or integrated capture mode, use the TRANLOGOPTIONS parameter with the EXCLUDETAG tag option. This parameter directs the Extract process to ignore transactions that are tagged with the specified redo tag. See Identifying Replicat Transactions to set the tag value. This is the recommended approach for Oracle.

  • When Extract is in classic capture mode, use the Extract TRANLOGOPTIONS parameter with the EXCLUDEUSER or EXCLUDEUSERID option to exclude the user name or ID that is used by Replicat to apply the DDL and DML transactions. Multiple EXCLUDEUSER statements can be used. The specified user is subject to the rules of the GETREPLICATES or IGNOREREPLICATES parameter. See Preventing Capture of Replicat Transactions (Other Databases) for more information.