Oracle Error Messages: 02/01/12

Wednesday, 1 February 2012

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.

ORA-04092: cannot string in a trigger

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-04091: table string.string is mutating, trigger or function may not see it

ORA-04091: table string.string is mutating, trigger or 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-04090: string specifies same table, event and trigger time as string

ORA-04090: string specifies same table, event and trigger time as string

Cause: Trigger is of duplicate event and trigger time.

Action: Combine the triggering information into one trigger which is fired at the given time.

ORA-04089: cannot create triggers on objects owned by SYS

ORA-04089: cannot create triggers on objects owned by SYS

Cause: An attempt was made to create a trigger on an object owned by SYS.

Action: Do not create triggers on objects owned by SYS.

ORA-04088: error during execution of trigger string.string

ORA-04088: error during execution of trigger string.string

Cause: A runtime error occurred during execution of a trigger.

Action: Check the triggers which were involved in the operation.

ORA-04087: cannot change the value of ROWID reference variable

ORA-04087: cannot change the value of ROWID reference variable

Cause: Rowid s can only be read and not changed.

Action: Do not attempt to change an rowid value.

ORA-04086: trigger description too long, move comments into triggering code

ORA-04086: trigger description too long, move comments into triggering code

Cause: The trigger description is limited to 2000 characters (for dictionary storage reasons). The description does not include the text of the when clause or the text of the pl or sql code executed for the trigger.

Action: If the trigger description contains a large comment, move that

ORA-04085: cannot change the value of an OLD reference variable

ORA-04085: cannot change the value of an OLD reference variable

Cause: Old values can only be read and not changed.

Action: Do not attempt to change an old variable.

ORA-04084: cannot change NEW values for this trigger type

ORA-04084: cannot change NEW values for this trigger type

Cause: New trigger variables can only be changed in before row insert or update triggers.

Action: Change the trigger type or remove the variable reference.

ORA-04083: invalid trigger variable string

ORA-04083: invalid trigger variable string

Cause: The variable referenced in the trigger body is invalid.

Action: See the manual for valid trigger variable types.

ORA-04082: NEW or OLD references not allowed in table level triggers

ORA-04082: NEW or OLD references not allowed in table level triggers

Cause: The trigger is accessing new or old values in a table trigger.

Action: Remove any new or old references.

ORA-04081: trigger string already exists

ORA-04081: trigger string already exists

Cause: The TRIGGER name or type already exists.

Action: Use a different trigger name or drop the trigger which is of the same name.

ORA-04080: trigger string does not exist

ORA-04080: trigger string does not exist

Cause: The TRIGGER name is invalid.

Action: Check the trigger name.

ORA-04079: invalid trigger specification

ORA-04079: invalid trigger specification

Cause: The create TRIGGER statement is invalid.

Action: Check the statement for correct syntax.

ORA-04078: OLD and NEW values cannot be identical

ORA-04078: OLD and NEW values cannot be identical

Cause: The referencing clause specifies identical values for NEW and OLD.

Action: Re-specify either the OLD or NEW referencing value.

ORA-04077: WHEN clause cannot be used with table level triggers

ORA-04077: WHEN clause cannot be used with table level triggers

Cause: The when clause can only be specified for row level triggers.

Action: Remove the when clause or specify for each row.

ORA-04076: invalid NEW or OLD specification

ORA-04076: invalid NEW or OLD specification

Cause: An invalid NEW or OLD specification was given for a column.

Action: Re-specify the column using the correct NEW or OLD specification.

ORA-04075: invalid trigger action

ORA-04075: invalid trigger action

Cause: An statement was given for the trigger action.

Action: Re-specify the trigger action.

ORA-04074: invalid REFERENCING name

ORA-04074: invalid REFERENCING name

Cause: An invalid name was given in the referencing clause.

Action: Verify the referencing name is not a reserved word.

ORA-04073: column list not valid for this trigger type

ORA-04073: column list not valid for this trigger type

Cause: A column list was specified for a non-update trigger type.

Action: Remove the column list.

ORA-04072: invalid trigger type

ORA-04072: invalid trigger type

Cause: An invalid trigger type was given.

Action: Specify either INSERT, UPDATE or DELETE.

ORA-04071: missing BEFORE, AFTER or INSTEAD OF keyword

ORA-04071: missing BEFORE, AFTER or INSTEAD OF keyword

Cause: The trigger statement is missing the BEFORE or AFTER or INSTEAD OF clause.

Action: Specify either BEFORE, AFTER or INSTEAD OF.

ORA-04070: invalid trigger name

ORA-04070: invalid trigger name

Cause: An invalid trigger name was specified.

Action: Verify that trigger name is not a reserved keyword.

ORA-04069: cannot drop or replace a library with table dependents

ORA-04069: cannot drop or replace a library with table dependents

Cause: An attempt was made to drop or replace a library that has dependents. There could be a table which depends on type which depends on the library being dropped.

Action: Drop all table(s) depending on the type, then retry.

ORA-04068: existing state of packagesstringstringstring has been discarded

ORA-04068: existing state of packagesstringstringstring has been discarded

Cause: One of errors 4060 - 4067 when attempt to execute a stored procedure.

Action: Try again after proper re-initialization of any application s state.

ORA-04067: not executed, string does not exist

ORA-04067: not executed, string does not exist

Cause: Attempt to execute a non-existent stored procedure.

Action: Make sure that a correct name is given.

ORA-04066: non-executable object, string

ORA-04066: non-executable object, string

Cause: Attempt to execute a non-procedure.

Action: Make sure that a correct name is given.

ORA-04065: not executed, altered or dropped string

ORA-04065: not executed, altered or dropped string

Cause: Attempt to execute a stored procedure that has been altered or dropped thus making it not callable from the calling procedure.

Action: Recompile its dependents.

ORA-04064: not executed, invalidated string

ORA-04064: not executed, invalidated string

Cause: Attempt to execute a stored procedure that has been invalidated.

Action: Recompile it.

ORA-04063: %s has errors

ORA-04063: %s has errors

Cause: Attempt to execute a stored procedure or use a view that has errors. For stored procedures, the problem could be syntax errors or references to other, non-existent procedures. For views, the problem could be a reference in the view s defining query to a non-existent table. Can also be a table which has references to non-existent or inaccessible types.

Action: Fix the errors and or or create referenced objects as necessary.

ORA-04062: %s of string has been changed

ORA-04062: %s of string has been changed

Cause: Attempt to execute a stored procedure to serve an RPC stub which specifies a timestamp or signature that is different from the current timestamp or signature of the procedure.

Action: Recompile the caller in order to pick up the new timestamp.

ORA-04061: existing state of string has been invalidated

ORA-04061: existing state of string has been invalidated

Cause: Attempt to resume the execution of a stored procedure using the existing state which has become invalid or inconsistent with the stored procedure because the procedure has been altered or dropped.

Action: Try again; this error should have caused the existing state of all packages to be re-initialized.

ORA-04060: insufficient privileges to execute string

ORA-04060: insufficient privileges to execute string

Cause: Attempt to execute a stored procedure without sufficient privileges.

Action: Get necessary privileges.

ORA-04055: Aborted: string formed a non-REF mutually-dependent cycle with string.

ORA-04055: Aborted: string formed a non-REF mutually-dependent cycle with string.

Cause: This compilation was aborted because the library unit that was compiled would have formed a non-REF mutually-dependent cycle with some other library units. This happens when an attempt is made to compile types that have attributes of other types that may participate in a cycle with this type. Example: create type t1; create type t2 (a t1); create type t1 (a t2);

Action: Break the cycle (possibly by adding a REF or by using another type).

ORA-04054: database link string does not exist

ORA-04054: database link string does not exist

Cause: During compilation of a PL or SQL block, an attempt was made to use a non-existent database link.

Action: Either use a different database link or create the database link.

ORA-04053: error occurred when validating remote object stringstringstringstringstring

ORA-04053: error occurred when validating remote object stringstringstringstringstring

Cause: An error has occurred when trying to validate a remote object.

Action: Fix the error. Make sure the remote database system has run KGLR.SQL to create necessary views used for querying or looking up objects stored in the database.

ORA-04052: error occurred when looking up remote object stringstringstringstringstring

ORA-04052: error occurred when looking up remote object stringstringstringstringstring

Cause: An error has occurred when trying to look up a remote object.

Action: Fix the error. Make sure the remote database system has run KGLR.SQL to create necessary views used for querying or looking up objects stored in the database.

ORA-04051: user string cannot use database link string.string

ORA-04051: user string cannot use database link string.string

Cause: During forwarding of a remote object access, an attempt was made to use a non-existent database link or one owned by a user other than the logon user or PUBLIC.

Action: Change your database link structure so that all indirect remote accesses are done from the same userid that originates the request.

ORA-04050: invalid or missing procedure, function, or package name

ORA-04050: invalid or missing procedure, function, or package name

Cause: The required procedure, function, or package name is invalid or missing.

Action: Specify a valid name.

ORA-04047: object specified is incompatible with the flag specified

ORA-04047: object specified is incompatible with the flag specified

Cause: The object type implied by the flag does not match the type of object specified.

Action: Specify the correct object, or use the appropriate flag

ORA-04046: results of compilation are too large to support

ORA-04046: results of compilation are too large to support

Cause: Attempt to compile and store a large stored procedure that results in compilation data that is too large for the system to support or store.

Action: Reduce the size of the store procedure by splitting it into smaller stored procedures.

ORA-04045: errors during recompilation or revalidation of string.string

ORA-04045: errors during recompilation or revalidation of string.string

Cause: This message indicates the object to which the following errors apply. The errors occurred during implicit recompilation or revalidation of the object.

Action: Check the following errors for more information, and make the necessary corrections to the object.

ORA-04044: procedure, function, package, or type is not allowed here

ORA-04044: procedure, function, package, or type is not allowed here

Cause: A procedure, function, or package was specified in an inappropriate place in a statement.

Action: Make sure the name is correct or remove it.

ORA-04043: object string does not exist

ORA-04043: object string does not exist

Cause: An object name was specified that was not recognized by the system. There are several possible causes: package body was entered. Since the system could not recognize the invalid name, it responded with the message that the named object does not exist. cannot be renamed.

Action: Check the spelling of the named object and rerun the code. (Valid names of tables, views, functions, etc. can be listed by querying the data dictionary.)

ORA-04042: procedure, function, package, or package body does not exist

ORA-04042: procedure, function, package, or package body does not exist

Cause: Attempt to access a procedure, function, package, or package body that does not exist.

Action: Make sure the name is correct.

ORA-04041: package specification must be created first before creating package body

ORA-04041: package specification must be created first before creating package body

Cause: Attempt to create a package body before creating its package specification.

Action: Create the package specification first before creating the package body.

ORA-04034: unable to shrink pool to specified size

ORA-04034: unable to shrink pool to specified size

Cause: The pool could not shrink to the specified size as it could not free memory.

Action: Specify a larger value to which to shrink the pool to.

ORA-04033: Insufficient memory to grow pool

ORA-04033: Insufficient memory to grow pool

Cause: The system had insufficient memory to grow the pool to the specified size.

Action: Specify a smaller value to grow the pool.

ORA-04032: pga_aggregate_target must be set before switching to auto mode

ORA-04032: pga_aggregate_target must be set before switching to auto mode

Cause: attempt to set workarea_size_policy to AUTO while pga_aggregate_target is not specified

Action: before setting workarea_size_policy, set pga_aggregate_target to a value representing the total private memory available to the instance. This total is generally the total physical memory available in the system minus what is needed for the SGA minus what is needed for the operating system (e.g. 500MB)

ORA-04031: unable to allocate string bytes of shared memory ( string , string , string , string )

ORA-04031: unable to allocate string bytes of shared memory ( string , string , string , string )

Cause: More shared memory is needed than was allocated in the shared pool.

Action: If the shared pool is out of memory, either use the dbms_shared_pool package to pin large packages, reduce your use of shared memory, or increase the amount of available shared memory by increasing the value of the INIT.ORA parameters shared_pool_reserved_size and shared_pool_size . If the large pool is out of memory, increase the INIT.ORA parameter large_pool_size .