IncludeTrigger
For Db2, the IncludeTrigger parameter specifies whether the High-speed Apply Engine uses records in the logical log that result from trigger activity.
Attributes
This parameter has the following attributes:
Attribute | Value |
|---|---|
Section | [LogicalLog] |
Abbreviation | None |
DBMS | Db2 |
Required? | No |
Valid values | Yes or No |
Default value | Yes |
Usage
Use this parameter to apply (or avoid applying) input records that reflect database changes that result from activity defined within a trigger. The activity can be performed directly within the trigger or by other processes nested beneath the trigger (for example, in a stored procedure called from within a trigger).
This parameter is frequently used when a target database environment defines the same triggers and relationships as the source environment where a logical log input file was created. In this situation, set the IncludeTrigger parameter to No. This action causes High-speed Apply Engine to ignore any trigger records in the input file. As High-speed Apply Engine processes the input, the triggers defined in the target environment are activated as they were in the source environment, and you can avoid any duplication of database changes.
Select one of the following values:
- Specify Yes to include (apply) trigger records. For consistency with past versions of High-speed Apply Engine, this value is the default.
- Specify No to exclude (ignore) trigger records.
To distinguish input records resulting from trigger activity, High-speed Apply Engine requires input logical log files to be generated by a Log Master.
Related topic