04040-04069: Stored Procedures

This section lists some of the messages generated when stored procedures are accessed.

Cause:	An attempt was made to create a package body before creating its package specification.

Action:	Create the package specification before trying to create the package body.

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

Cause:	An attempt was made to access a procedure, function, package, or package body that does not exist.

Action:	Ensure the name specified is correct.

ORA-04043 object name does not exist

Cause:	An object name was specified that was not recognized by the system. There are several possible causes:

• An invalid name for a table, view, sequence, procedure, function, package, or package body was entered. Since the system did not recognize the invalid name, it responded with the message that the named object did not exist.

• An attempt was made to rename an index or a cluster or some other object that cannot be renamed.

Cause:	An attempt was made to specify a procedure, function, or package in an inappropriate place in a statement.

Action:	Refer to Oracle7 Server SQL Reference for the correct placement of procedures, functions, and packages in statements.

ORA-04045 errors during recompilation/revalidation of name.name

Cause:	Errors occurred during the implicit recompilation/revalidation of the object named in the message.

When Trusted Oracle7 is configured in OS MAC mode, you may get this error if you attempt to select from a view that needs to be recompiled. In particular, if the view is on a lower database and a higher database selects from this view, this error can occur.

For Trusted Oracle7 users, if the cause is that the view needs to be recompiled, ensure that it is recompiled before it is selected.

Cause:	An attempt to compile and store a large stored procedure resulted 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-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-04051 user name cannot use database link name

Cause:	An attempt was made to access a non-existent database link, or a link not owned by the user logging in or PUBLIC, while attempting to access a remote object.

Action:	Change the database link structure, so all indirect remote access requests are done from the same user originating the request or PUBLIC.

ORA-04052 error occurred when looking up remote object name

Cause:	An error occurred looking up a remote object.

Action:	Fix the error. Check that the remote database system has run the script to create necessary views used for querying/looking up objects stored in the database. See the Oracle7 Server Administrator's Guide.

ORA-04053 error occurred when validating remote object name

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

Action:	Fix the error. Check that the remote database system has run the script to create necessary views used for querying/looking up objects stored in the database. See the Oracle7 Server Administrator's Guide.

ORA-04054 database link name does not exist

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

Action:	Use a different database link or create the database link.

ORA-04055 package STANDARD@name is incompatible to local package STANDARD

Cause:

An attempt was made to compile a remote procedure call, but the remote procedure was compiled using a package STANDARD that has a different time-stamp from the one of the local package STANDARD. Therefore, those package STANDARDs are incompatible with each other and PL/SQL packages, procedures, and functions compiled against the remote package STANDARD are also incompatible with those compiled against the local package STANDARD.

Action:	Upgrade either the local database or the remote database, whichever is older, to the same version.

ORA-04060 insufficient privileges to execute name

Cause:	An attempt was made to execute a stored procedure without sufficient privileges.

Action:	Obtain the necessary privileges through direct grants of the privileges, not through roles.

ORA-04061 existing state of name has been invalidated

Cause:	An attempt was made to resume the execution of a stored procedure using the existing state, which has become invalid or inconsistent because the stored procedure has been altered or dropped.

Action:	Attempt the action again. This action should cause the existing state of all packages to be reinitialized.

ORA-04062 name of name has been changed

Cause:	An attempt was made to execute a stored procedure to service a remote procedure call stub that specifies a timestamp or signature that is different from the current timestamp or signature of the procedure.

Action:	Recompile the caller to obtain the new timestamp.

For more information about obtaining a tinestamp, see the index entry on "timestamp conflict resolution method" in Oracle7 Server Distributed Systems, Volume II.

Cause:	An attempt was made to execute a stored procedure that has errors. For stored procedures, the problem could be syntax 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.

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

ORA-04064 not executed, invalidated name

Cause:	An attempt was made to execute a stored procedure that has been invalidated.

Action:	Recompile the procedure and its dependents.

ORA-04065 not executed, altered, or dropped name

Cause:	An attempt was made to execute a stored procedure that has been altered or dropped.

Action:	Recompile the procedure's dependents.

ORA-04066 non-executable object, name

Cause:	An attempt was made to execute an object that is not a package, procedure, or function.

Action:	Check that a correct name is used.

ORA-04067 not executed, name does not exist

Cause:	An attempt was made to execute a package, procedure, or function that does not exist.

Action:	Check the name in the command.

ORA-04068 existing state of packages has been discarded

Cause:	An error occurred when attempting to execute a stored procedure.

Action:	Refer to the accompanying messages and fix the error mentioned. Try the procedure again after proper reinitialization of any application's state.