ORA-04099: trigger string is valid but not stored in compiled form ORA-04930: open sequence number failed or initial state is valid

ORA-04099: trigger string is valid but not stored in compiled form ORA-04930: open sequence number failed or initial state is valid

Cause: Either Shared Sequence Number OS component was not installed properly, or an MC hardware failure may have occurred or a previous instance was not shut down properly.

Action: Verify that there are no background or foreground Oracle processes from a previous instance on this node using the OS command ps -ef|grep lamp;lt;lamp;nbsp;instance_ namelamp;gt;. Verify that there are no shared memory segments belonging to the user which owns the Oracle installation by isuing the ipcs -b OS command. If there are shared memory segments or processes still on the system, use svrmgrl to shutdown the instance with the abort option. If the instance is not up, verify that the cluster software and or or the hardware is installed and working. Log in as superuser and issue the cnxshow command. Are all of the nodes in the cluster listed? Are they members of the cluster? Is the communications between nodes okay? If the answer to any of these questions is false, contact Digital s customer support organization.

ORA-04098: trigger string.string is invalid and failed re-validation

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 or authorization failed for the trigger.

Action: Options are to resolve the compilation or authorization errors, disable the trigger, or drop the trigger.

ORA-04097: DDL conflict while trying to drop or alter a trigger

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-04096: trigger string has a WHEN clause which is too large, limit 2K

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-04095: trigger string already exists on another table, cannot replace it

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-04094: table string.string is constraining, trigger may not modify it

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.

Action: none

ORA-04093: references to columns of type LONG are not allowed in triggers

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.