EXCLUDETAG

Valid For

For all supported databases.

For Extract or Replicat processes, using the parameter files. Also see TRANLOGOPTIONS for using the parameter within the Extract parameter file.

Distribution path, using conditions when creating the distribution path. For the primary Extract, using

Description

Use EXCLUDETAG tag in your Extract or Replicat parameter file to specify changes to be excluded from trail files. The limitation for this parameter is that the tag value can be up to 2000 hexadecimal digits (0-9A-F) or the plus sign (+). You can have multiple EXCLUDETAG lines, but each EXCLUDETAG should have a single value. By default, Replicat the individual records every change it applies to the database by 00 in both classic mode or integrated mode. Compared with older versions, new trail file contains tag tokens, which would not introduce problems for older trail readers.

Use EXCLUDETAG + to ignore the individual records that are tagged with any redo tag.

Do not use NULL with tag or + because it operates in conflict, resulting in errors.

To tag the individual records, use the DBOPTIONS parameter with the SETTAG option in the Replicat parameter file. Use these parameters to prevent cycling (loop-back) of Replicat the individual records in a bi-directional configuration or to filter other transactions from capture. The default SETTAG value is 00 and this is the tag that Replicat uses when applying transactions to the target Oracle database.

Also see TRANLOGOPTIONS to know more about using EXCLUDETAG as a parameter option.

Valid value is any single Oracle Streams tag. A tag value can be up to 2000 hexadecimal digits (0-9 A-F) long.

Note:

These parameters should be used instead of EXCLUDEUSER or TRACETABLE when possible.

Default

None

Syntax

[EXCLUDETAG [tag | NULL] | [+]

Example 1

For Replicat, in the Replicat parameter file:

excludetag 0