Object-List Format

Use the object-list format to change the mode for one or more constraint, index, or trigger.
(1)
Object-List Format

1  CONSTRAINTS + , constraint  %Modes for Constraints and Unique Indexes1
1  INDEXES + , index
2.1  %Modes for Constraints and Unique Indexes1
2.1  %Modes
for Triggers and Duplicate Indexes2
1  TRIGGERS + , trigger?  %Modes for Triggers and Duplicate
Indexes2
Element Description Restrictions Syntax
constraint Name of a constraint whose mode is to be set Must be a local constraint, and all constraints in the list must be defined on the same table Identifier
index Name of an index whose mode is to be set Must be a local index, and all indexes in the list must be defined on the same table Identifier
trigger Name of a trigger whose mode is to be set Must be a local trigger, and all triggers in the list must be defined on the same table or view Identifier
For example, to change the mode of the unique index unq_ssn on the cust_subset table to filtering, enter the following statement:
SET INDEXES unq_ssn FILTERING;
You can also use the object-list format to change the mode for a list of constraints, indexes, or triggers that are defined on the same table. Assume that four triggers are defined on the cust_subset table: insert_trig, update_trig, delete_trig, and execute_trig. Also assume that all four triggers are enabled. To disable all triggers except execute_trig, enter this statement:
SET TRIGGERS insert_trig, update_trig, delete_trig DISABLED;
If my_trig is a disabled INSTEAD OF trigger on a view, the following statement enables that trigger:
SET TRIGGERS my_trig ENABLED;

In cluster environments, the SET TRIGGERS statement is not supported on updatable secondary servers. More generally, session-level index, trigger, and constraint modes that the SET Database Object Mode statement specifies are not redirected for UPDATE operations on table objects in databases of secondary servers.