Valid For
Extract
Description
Use the GETAPPLOPS or IGNOREAPPLOPS parameter to capture or ignore DML operations produced by any application except the local Replicat. By default, application data is captured.
These parameters are useful in conjunction with the GETREPLICATES and IGNOREREPLICATES parameters for the following:
To separate data operations performed by a local Replicat from those performed by the business applications configured for Oracle GoldenGate extraction. Use IGNOREAPPLOPS and GETREPLICATES for one trail or file to contain just the Replicat operations, and use GETAPPLOPS and IGNOREREPLICATES for another trail or file to contain just the operations of the business applications.
As part of a cascading configuration, where changes applied by Replicat locally must be captured by a local Extract to be propagated to another system. In this case, IGNOREAPPLOPS and GETREPLICATES would be used.
As part of a loop detection scheme when using bidirectional replication. The default combination of GETAPPLOPS and IGNOREREPLICATES causes Extract to capture application data while ignoring Replicat operations posted to the same database objects. In addition to using these parameters, Extract must be configured to identify Replicat transactions.
See "GETREPLICATES | IGNOREREPLICATES" for more information.
Using GETAPPLOPS for Oracle Sequences
GETAPPLOPS must be enabled to capture sequences that are replicated by Replicat. Replicat issues sequence updates in an autonomous transaction, so they are not reflected in the trace table. The sequence update appears as if it is an application operation.
Using GETAPPLEOPS for DDL Operations
See "DDLOPTIONS" for information on to use GETAPPLOPS or IGNOREAPPLOPS functionality for DDL operations.
For more information about configuring bidirectional replication, see the Administering Oracle GoldenGate.
Default
GETAPPLOPS
Syntax
GETAPPLOPS | IGNOREAPPLOPS