Oracle8 Error Messages Release 8.0.4 A58312-01 |
Library | Product | Contents | Index

## 04040-04059: Stored Procedure Messages

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

If you are using Trusted Oracle, see the Trusted Oracle documentation for information about error messages in that environment.

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

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.

Action: Check the spelling of the renamed object and rerun the code. Valid names of tables, views, functions, and so forth can be listed by querying the data dictionary.

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

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

Action: Refer to Oracle8 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.

Action: More descriptive messages follow this one. Check the causes mentioned in the messages that follow and take the appropriate actions.

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

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 Oracle8 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 Oracle8 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: aborted: name formed a non-REF mutually-dependent cycle with name

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. For 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).

Prev | Top | Next
| Copyright © 1997 Oracle Corporation. All Rights Reserved. |
Library | Product | Contents | Index