Oracle7 Server Messages
06500-06599: PL/SQL
This section lists messages generated when Oracle detects a problem with PL/SQL code. These ORA-nnnnn messages are usually followed by PLS-nnnnn messages, which are listed in Chapter 3.
ORA-06500 PL/SQL: storage error
| Cause: | This is a rare internal error message. Memory has been exhausted or corrupted. | |
| Action: | Contact customer support. | |
ORA-06501 PL/SQL: internal error num, arguments [num], [num], [num], [num],
[num], [num]
| Cause: | This is an internal error message. An error has been detected in a
PL/SQL program. | |
| Action: | Contact customer support. | |
ORA-06502 PL/SQL: numeric or value error
| Cause: | An arithmetic, numeric, string, conversion, or constraint error occurred. For example, this error occurs if an attempt is made to assign the value NULL to a variable declared NOT NULL, or if an attempt is made to assign an integer larger than 99 to a variable declared NUMBER(2). | |
| Action: | Change the data, how it is manipulated, or how it is declared so that values do not violate constraints. | |
ORA-06503 PL/SQL: Function returned without value
| Cause: | A call to a PL/SQL function completed, but no RETURN statement was executed. | |
| Action: | Rewrite the PL/SQL function, making sure that it always returns a value of a proper type. | |
ORA-06504 PL/SQL: Return types of Result Set variables or query do not match
| Cause: | Number and/or types of columns in a query do not match the declared return type of a Result Set variable, or the declared types of two Result Set variables do not match. | |
| Action: | Change the program statement or declaration. Identify the query to which the variable, during execution, actually refers. | |
ORA-06508 PL/SQL: could not find program unit being called
| Cause: | An attempt was made to call a stored program that could not be found. The program may have been dropped or incompatibly modified, or have compiled with errors. | |
| Action: | Check that all referenced programs, including their package bodies, exist and are compatible. | |
ORA-06509 PL/SQL: ICD vector missing for this package
| Cause: | This indicates a version clash between some package distributed with an Oracle product and the product executable. | |
| Action: | Contact customer support. | |
ORA-06510 PL/SQL: unhandled user-defined exception str
| Cause: | A user-defined exception was raised by PL/SQL code, but not handled. | |
| Action: | Fix the problem causing the exception or write an exception handler for
this condition. It may be necessary to contact the application or
database administrator. | |
ORA-06511 PL/SQL: cursor already open
| Cause: | An attempt was made to open a cursor that was already open. | |
| Action: | Close the cursor before attempting to reopen it. | |
ORA-06512 at str line num
| Cause: | This is usually the last of a message stack and indicates where a problem occurred in the PL/SQL code. | |
| Action: | Fix the problem causing the exception or write an exception handler for
this condition. It may be necessary to contact the application or
database administrator. | |
ORA-06513 PL/SQL: index for PL/SQL table out of range for host language array
| Cause: | An attempt was made to copy a PL/SQL table to a host language array, but an index in the table is either less than one or greater than the maximum size of the host language array. When copying PL/SQL tables to host language arrays, the table entry at index 1 is placed in the first element of the array, the entry at index 2 is placed in the second element of the array, and so on. If a table entry was not assigned, then the corresponding element in the host language array is set to NULL. | |
| Action: | Increase the size of the host language arrays or decrease the size of the PL/SQL table. Also make sure that you do not use index values less than 1. | |
ORA-06514 PL/SQL: The remote call cannot be handled by the server
| Cause: | The remote call had parameters that were cursor variables. This cannot be handled by stored procedures on your server. | |
| Action: | Avoid using cursor variables as parameters for stored procedures on this server or upgrade your server to a version that supports this. | |
ORA-06540 PL/SQL compilation error
| Cause: | A PL/SQL compilation error occurred. However, the user generally will not see this error message. Instead, there will be accompanying PLS-nnnnn error messages. | |
| Action: | See accompanying PLS-nnnnn error messages. | |
ORA-06541 PL/SQL: compilation error - compilation aborted
| Cause: | A PL/SQL compilation error occurred and the compilation was aborted. However, the user generally will not see this error message. Instead, there will be accompanying PLS-nnnnn error messages. | |
| Action: | See accompanying PLS-nnnnn error messages. | |
ORA-06544 PL/SQL: internal error, arguments:arg1, arg2, arg3, arg4, arg5, arg6, arg7, arg8
| Cause: | A PL/SQL internal error occurred. | |
| Action: | Report this as a bug; the first argument is the internal error number. | |
ORA-06550 line num, column num: str
| Cause: | A PL/SQL compilation error has occurred. The numbers given for line and column are the location in the PL/SQL block where the error occurred. | |
| Action: | Refer to the following PL/SQL messages for more information about the error. | |
ORA-06554 package DBMS_STANDARD must be created before using PL/SQL
| Cause: | The data dictionary script required by PL/SQL has not yet been run. | |
ORA-06555 this name is currently reserved for use by user SYS
| Cause: | An attempt was made to create a user-owned package named STANDARD, DBMS_STANDARD, or DBMS_OUTPUT. This is not allowed. | |
| Action: | Choose another name for the package. | |
ORA-06556 the pipe is empty, cannot fulfill the UNPACK_MESSAGE request
| Cause: | There are no more items in the pipe. | |
| Action: | Check that the sender and receiver agree on the number and types of items placed on the pipe. | |
ORA-06557 null values are not allowed for any parameters to pipe ICD's
| Cause: | Internal error from the DBMS_PIPE package. | |
| Action: | Contact customer support. | |
ORA-06558 buffer in DBMS_PIPE package is full. No more items allowed
| Cause: | The pipe buffer size has been exceeded. | |
ORA-06559 wrong datatype requested, type, actual datatype is type
| Cause: | The sender put a different datatype on the pipe than that being requested, package DBMS_PIPE. The recognized datatypes and the corresponding numbers are: 6 - number, 9 - char, 12 - date. | |
| Action: | Check that the sender and receiver agree on the number and types of items placed on the pipe. | |
ORA-06562 type of OUT argument must match type of column or bind variable
| Cause: | An attempt was made to get the value of a column or a bind variable by calling procedure COLUMN_VALUE or VARIABLE_VALUE of package DBMS_SQL. However, the type of the given out argument was different from the type of the column or bind variable that was previously defined by calling procedure DEFINE_COLUMN, for defining a column, or BIND_VARIABLE, for binding a bind variable, of package DBMS_SQL. | |
| Action: | Pass in an OUT argument of the correct type when calling procedure COLUMN_VALUE or VARIABLE_VALUE. The right type is the type that was provided when defining the column or binding the bind variable. | |
ORA-06560 pos, num, is negative or larger than the buffer size, num
| Cause: | Internal error from the DBMS_PIPE package. | |
| Action: | Contact customer support. | |
ORA-06563 top level procedure or function specified, cannot have subparts
| Cause: | The name to be resolved was specified with three parts, a.b.c, but the a.b part resolves to a top level procedure or function that does not have nested procedures. This can also happen with a two-part name, a.b, where a is a synonym for a top level package or procedure. | |
| Action: | Specify a procedure or function within a package or a top level procedure
or function. | |
ORA-06564 object name does not exist
| Cause: | The named object could not be found. Either it does not exist or you do not have permission to access it. | |
| Action: | Create the object or get permission to access it. | |
ORA-06565 cannot execute name from within stored procedure
| Cause: | The named procedure cannot be executed from within a stored procedure, function, or package. This function can only be used from PL/SQL
anonymous blocks. | |
| Action: | Remove the procedure from the calling stored procedure. | |
ORA-06566 invalid number of rows specified
| Cause: | An invalid number of rows was specified in a call to the procedures DEFINE_COLUMN in the package DBMS_SQL. For a given parsed statement in a given cursor, all columns must be defined to have the same number of rows, so all the calls to DEFINE_COLUMN must specify the same number
of rows. | |
| Action: | Specify a number that matches the number for previously defined columns. | |
ORA-06567 invalid number of values specified
| Cause: | An invalid number of values to be bound was specified in a call to the procedure BIND_VARIABLE in the package DBMS_SQL. For a given parsed statement in a given cursor, the same number of values must be bound for all bind variables, so all the calls to BIND_VARIABLE must specify the same number of values. | |
| Action: | Make sure that the same number of values are given for each of the
bind variables. | |
ORA-06568 obsolete ICD procedure called
| Cause: | An obsolete ICD procedure was called by a PL/SQL program. The PL/SQL program was probably written for an earlier release of Oracle. | |
| Action: | Ensure that all PL/SQL packages are upgraded to the latest release of Oracle by following the upgrade instructions noted in the README document or by running the CATPROC.SQL script. | |
ORA-06570 shared pool object does not exist, cannot be pinned
| Cause: | The specified shared pool shared cursor could not be found. Therefore, it cannot be pinned. | |
| Action: | Make sure that a correct shared cursor name is given. Names are a string of the form 'HHHHHHHH,SDDDDDDDDDD' where the H's are an 8-digit hex number from the 'address' column of V$SQLAREA, and the D's are a 1- to 10-digit decimal number with an optional leading sign from the
'hash_value' column. | |
ORA-06571 function name does not guarantee not to update database
| Cause: | There are two possible causes for this message: | |
- A SQL statement references a packaged PL/SQL function that does not contain a pragma that prevents the database from being updated.
- A SQL statement references a stand-alone, PL/SQL function that contains an instruction to update the database.
| Action: | If the referenced function is a packaged PL/SQL function: Recreate the PL/SQL function with the required pragma; be certain to include the 'Write No Database State' (WNDS) argument in the argument list of the pragma. | |
If the referenced function is a stand-alone PL/SQL function: Do not use
the function.
ORA-06572 function name has out arguments
| Cause: | A SQL statement references either a packaged or a stand-alone PL/SQL function that contains an OUT parameter in its argument list. PL/SQL functions referenced by SQL statements must not contain the OUT parameter. | |
| Action: | Recreate the PL/SQL function without the OUT parameter in the argument list. | |
ORA-06573 function name modifies package state, cannot be used here
| Cause: | There are two possible causes for this message: | |
- A SQL statement references a packaged PL/SQL function that does not contain a pragma containing the 'Write no PackageState' (WNPS).
- A SQL statement references a stand-alone PL/SQL function that modifies a package state. A stand-alone PL/SQL function referenced by a SQL statement cannot modify a package state.
| Action: | If the function is a packaged PL/SQL function: recreate the function and include a pragma containing the 'Write no Package State' (WNPS). | |
If the function is a stand-alone PL/SQL function: delete the function from the SQL statement.
ORA-06574 function name references package state, cannot execute remotely
| Cause: | There are two possible causes for this message: | |
- A remote packaged function or a remote-mapped, local packaged function that does not contain a pragma with the 'Write no Package State' (WNPS) and 'Read no Package State' (RNPS) arguments references a package state.
- A remote stand-alone function or a remote-mapped, local stand-alone function contains a reference to a package state that reads or writes a
package variable.
Only local functions that are referenced in a SELECT list, VALUES clause of an INSERT statement, or SET clause of an UPDATE statement can modify a package state.
| Action: | If the function is a packaged function: Recreate the function and include a pragma containing the 'Write no Package State' (WNPS) and 'Read no Package State' (RNPS) arguments. | |
If the function is a stand-alone function: Do not call the function.
ORA-06575 function name is in an invalid state
| Cause: | A SQL statement references a PL/SQL function that is in an invalid state. Oracle attempted to compile the function, but detected errors. | |
| Action: | Check the SQL statement and the PL/SQL function for syntax errors or incorrectly assigned, or missing, privileges for a referenced object. | |
ORA-06580 Hash Join ran out of memory while keeping large rows in memory
| Cause: | Hash Join reserved 3 slots (each slot size = DB_BLOCK_SIZE * HASH_JOIN_MULTIBLOCK_IO_COUNT) for a row. If a row is larger than that, this error will be raised. | |
| Action: | Increase HASH_JOIN_MULTIBLOCK_IO_COUNT so that each joined row fits in a slot. HASH_AREA_SIZE may also need to be increased. | |