Golden Gate Preventing Data Looping

Original document is here : 

https://docs.oracle.com/goldengate/1212/gg-winux/GWUAD/wu_bidirectional.htm#i1036715

In short, Goal is to identify which process causes to replicate, and if the process is replicat, ignore it.

If your database is oracle and capture mode is direct :

Use these options :

• GETAPPLOPS | IGNOREAPPLOPS: Controls whether or not data operations (DML) produced by business applications except Replicat are included in the content that Extract writes to a specific trail or file.
  
• GETREPLICATES | IGNOREREPLICATES: Controls whether or not DML operations produced by Replicat are included in the content that Extract writes to a specific trail or file.

If your database is oracle and capture mode is integrated:

Use this method :

• Use DBOPTIONS with the SETTAG option in the Replicat parameter file. Replicat tags the transactions being applied with the specified value, which identifies those transactions in the redo stream. The default SETTAG value is 00. Valid values are a single TAG value consisting of hexadecimal digits. For more information about tags, see Reference for Oracle GoldenGate for Windows and UNIX.
  

• Use the TRANLOGOPTIONS parameter with the EXCLUDETAG option in the Extract parameter file. The logmining server associated with that Extract excludes redo that is tagged with the SETTAG value.
  The following shows how SETTAG can be set in the Replicat parameter file:
  

  DBOPTIONS SETTAG 0935
  

  The following shows how EXCLUDETAG can be set in the Extract parameter file:
  

  TRANLOGOPTIONS EXCLUDETAG 0935
  

  If you are excluding multiple tags, each must have a separate TRANLOGOPTIONS EXCLUDETAG statement specified.