25000-25099: Trigger Messages

This section lists messages generated when triggers are accessed. For more trigger messages, see 04070-04099: Trigger Messages on page -55.

ORA-25000: invalid use of bind variable in trigger WHEN clause

Cause: A bind variable was used in the WHEN clause of a trigger.

Action: Remove the bind variable. To access the table columns, use (new/old).column_name.

For more information about triggers, see the index entry on "triggers" in Oracle8 Server SQL Reference.

ORA-25001: cannot create this trigger type on views

Cause: Only INSTEAD OF triggers can be created on a view.

Action: Change the trigger type to INSTEAD OF.

ORA-25002: cannot create INSTEAD OF triggers on tables

Cause: Only BEFORE or AFTER triggers can be created on a table.

Action: Change the trigger type to BEFORE or AFTER.

ORA-25003: cannot change NEW values for this column type in trigger

Cause: Attempt to change NEW trigger variables of datatype object, REF, nested table, VARRAY or LOB datatype which is not supported.

Action: Do not change the NEW trigger variables in the trigger body.

ORA-25004: WHEN clause is not allowed in INSTEAD OF triggers

Cause: WHEN clause is specified in an INSTEAD OF trigger.

Action: Remove the WHEN clause when creating an INSTEAD OF trigger.

ORA-25005: cannot CREATE INSTEAD OF trigger on a read-only view

Cause: An attempt was made to create an INSTEAD OF trigger on a view which was created with the read-only option. The view cannot be updated using INSTEAD OF triggers.

Action: Do not create the trigger.

ORA-25006: cannot specify this column in UPDATE OF clause

Cause: Attempt to create a trigger on update of a column whose datatype is disallowed in the clause, such as LOB and nested table.

Action: Remove the UPDATE OF clause.

ORA-25007: functions or methods not allowed in WHEN clause

Cause: PLSQL function call or method invocation is not allowed in the WHEN clause when creating a trigger.

Action: Remove the function call or method invocation from the WHEN clause.

ORA-25008: no implicit conversion to LOB datatype in instead-of trigger

Cause: When inserting or updating a view using instead-of trigger, the new value for a LOB view column is of a different datatype.

Action: Specified a LOB value as the new value for the LOB view column.

---