Triggers are defined using PL/SQL. Therefore, this section provides some general information but refers to Oracle Database PL/SQL Language Reference for details of syntax and semantics.
This statement does not change the declaration or definition of an existing trigger. To redeclare or redefine a trigger, use the
TRIGGER statement with the
The trigger must be in your own schema or you must have
TRIGGER system privilege.
In addition, to alter a trigger on
DATABASE, you must have the
CREATE TRIGGER for more information on triggers based on
trigger_compile_clause: See Oracle Database PL/SQL Language Reference for the syntax of this clause.)
Specify the schema containing the trigger. If you omit
schema, then Oracle Database assumes the trigger is in your own schema.
Specify the name of the trigger to be altered.
See Oracle Database PL/SQL Language Reference for the syntax and semantics of this clause and for complete information on creating and compiling triggers.
ENABLE | DISABLE
ENABLE to enable the trigger. You can also use the
TRIGGERS clause of
TABLE to enable all triggers associated with a table. See ALTER TABLE.
DISABLE to disable the trigger. You can also use the
TRIGGERS clause of
TABLE to disable all triggers associated with a table.
When you rename a trigger, the database rebuilds the remembered source of the trigger in the
DBA_SOURCE data dictionary views. As a result, comments and formatting may change in the
TEXT column of those views even though the trigger source did not change.
EDITIONABLE | NONEDITIONABLE
Use these clauses to specify whether the trigger becomes an editioned or noneditioned object if editioning is later enabled for the schema object type
schema. The default is
EDITIONABLE. For information about altering editioned and noneditioned objects, see Oracle Database Development Guide.
Restriction on NONEDITIONABLE
You cannot specify
NONEDITIONABLE for a crossedition trigger.