ORA-04091: table string.string is mutating, trigger/function may not see it
Cause: A trigger (or a user defined plsql function that is referenced in this statement) attempted to look at (or modify) a table that was in the middle of being modified by the statement which fired it.
Action: Rewrite the trigger (or function) so it does not read that table.
ORA-04092: cannot string in a trigger
Cause: A trigger attempted to commit or rollback.
Action: Rewrite the trigger so it does not commit or rollback.
ORA-04093: references to columns of type LONG are not allowed in triggers
Cause: A trigger attempted to reference a long column in the triggering table.
Action: Do not reference the long column.
ORA-04094: table string.string is constraining, trigger may not modify it
Cause: A trigger attempted to modify a table that was constraining for some referential constraint of a parent SQL statement.
ORA-04095: trigger ‘string’ already exists on another table, cannot replace it
Cause: Cannot replace a trigger which already exists on a different table than the one being replaced.
Action: Drop the trigger with the same name and re-create it.
ORA-04096: trigger ‘string’ has a WHEN clause which is too large, limit 2K
Cause: A trigger’s ‘when’ clause is limited to 2K for dictionary storage reasons. The trigger being created exceeded that size.
Action: Use a smaller ‘when’ clause. Note, the trigger body could be used to perform the same limiting action as the ‘when’ clause.
ORA-04097: DDL conflict while trying to drop or alter a trigger
Cause: An attempt was made to concurrently perform two DDL operations on a trigger or trigger table.
Action: Investigate the new state of the trigger and retry the DDL operation, if still appropriate.
ORA-04098: trigger ‘string.string’ is invalid and failed re-validation
Cause: A trigger was attempted to be retrieved for execution and was found to be invalid. This also means that compilation/authorization failed for the trigger.
Action: Options are to resolve the compilation/authorization errors, disable the trigger, or drop the trigger.
ORA-04099: trigger ‘string’ is valid but not stored in compiled form
Cause: A trigger was attempted to be retrieved for execution and was found to be valid, but not stored. This may mean the an upgrade was done improperly from a non-stored trigger release.
Action: Alter compile the trigger to create the trigger in stored form. Also, you may want to review that a proper upgrade was done.
Above are list of Oracle Database Errors or Warnings from Error ORA-04091 to ORA-04099 received while performing certain operation against Oracle Database or related products.
What are Oracle Database Error Messages?
Oracle Error Messages may be returned while using products which are part of Oracle Database. Each Oracle Database Error or Warning Message mentioned above contains the Warning or Error Message Statement, a short explanation of the probable causes of the Error message, and a recommended action.
Hope this was helpful.
Information about Oracle Database Error Messages or Warning Messages on Windows and Linux Operating Systems.