ORA-06603: LU6.2 Driver: Error allocating memory

ORA-06603: LU6.2 Driver: Error allocating memory

Cause: Operating system refused request for memory.

Action: Contact you local service representative.

ORA-06602: LU6.2 Driver: Error allocating context area

ORA-06602: LU6.2 Driver: Error allocating context area

Cause: Context area failure.

Action: Contact your local service representative.

ORA-06601: LU6.2 Driver: Invalid database ID string

ORA-06601: LU6.2 Driver: Invalid database ID string

Cause: The database string in the connect was invalid.

Action: Provide a valid database string, as defined in documentation.

ORA-06600: LU6.2 Driver: SNA software is not loaded

ORA-06600: LU6.2 Driver: SNA software is not loaded

Cause: The SNA software is not running.

Action: Start the SNA software and try again.

ORA-06596: unsupported LOB operation in RPC call

ORA-06596: unsupported LOB operation in RPC call

Cause: An attempt was made to perform certain LOB operations (for example, deep copying of a temporary or abstract LOB on the client-side) while performing an RPC. This is not currently supported.

Action: Perform the LOB operation in question before starting the RPC; or perform those LOB operations which are not actually executed on the client-side, on the server-side.

ORA-06595: REF CURSOR parameters are not supported in forwarded RPC calls

ORA-06595: REF CURSOR parameters are not supported in forwarded RPC calls

Cause: An attempt was made to make a forwarded RPC call with a REF CURSOR parameter.

Action: Either call the remote function directly (i.e., not by way of forwarding), or move the remote function to a database where it can be called directly.

ORA-06593: %s is not supported with natively compiled PL or SQL modules

ORA-06593: %s is not supported with natively compiled PL or SQL modules

Cause: Specified feature is not yet supported for natively compiled PL or SQL modules yet.

Action: Recompile the relevant PL or SQL modules in non-native mode by setting the parameter plsql_compiler_flags to INTERPRETED.

ORA-06592: CASE not found while executing CASE statement

ORA-06592: CASE not found while executing CASE statement

Cause: A CASE statement must either list all possible cases or have an else clause.

Action: Add all missing cases or an else clause.

ORA-06580: Hash Join ran out of memory while keeping large rows in memory

ORA-06580: Hash Join ran out of memory while keeping large rows in memory

Cause: Hash Join reserves 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 increaed.

ORA-06579: Bind variable not big enough to hold the output value

ORA-06579: Bind variable not big enough to hold the output value

Cause: The bind variable specified by the user is not large enough to hold the output returned by the function or a procedure.

Action: Specify a bind variable of larger size.

ORA-06578: output parameter cannot be a duplicate bind

ORA-06578: output parameter cannot be a duplicate bind

Cause: The bind variable corresponding to an IN or OUT or OUT parameter for a function or a procedure or a function return value in a CALL statement cannot be a duplicate bind variable.

Action: Change the bind variable to be unique

ORA-06577: output parameter not a bind variable

ORA-06577: output parameter not a bind variable

Cause: The argument corresponding to an IN or OUT or OUT parameter for a function or a procedure or a function return value in a CALL statement must be a bind variable.

Action: Change the argument to a bind variable

ORA-06576: not a valid function or procedure name

ORA-06576: not a valid function or procedure name

Cause: Could not find a function (if an INTO clause was present) or a procedure (if the statement did not have an INTO clause) to call.

Action: Change the statement to invoke a function or procedure

ORA-06575: Package or function string is in an invalid state

ORA-06575: Package or function string is in an invalid state

Cause: A SQL statement references a PL or 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 or SQL function for syntax errors or incorrectly assigned, or missing, privileges for a referenced object.

ORA-06574: Function string references package state, cannot execute remotely

ORA-06574: Function string 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 (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-06573: Function string modifies package state, cannot be used here

ORA-06573: Function string modifies package state, cannot be used here

Cause: There are two possible causes for this message: * A SQL statement references a packaged, PL or SQL function that does not contain a pragma containing the Write no Package State (WNPS). * A SQL statement references a stand-alone, PL or SQL function that modifies a package state. A stand-alone, PL or SQL function referenced by a SQL statement cannot modify a package state.

Action: If the function is a packaged, PL or SQL function: Recreate the function and include a pragma containing the Write no Package State (WNPS). If the function is a stand-alone, PL or SQL function: Delete the function from the SQL statement.

ORA-06572: Function string has out arguments

ORA-06572: Function string has out arguments

Cause: A SQL statement references either a packaged, or a stand-alone, PL or SQL function that contains an OUT parameter in its argument list. PL or SQL functions referenced by SQL statements must not contain the OUT parameter.

Action: Recreate the PL or SQL function without the OUT parameter in the argument list.

ORA-06571: Function string does not guarantee not to update database

ORA-06571: Function string does not guarantee not to update database

Cause: There are two possible causes for this message: * A SQL statement references a packaged, PL or SQL function that does not contain a pragma that prevents the database from being updated. * A SQL statement references a stand-alone, PL or SQL function that contains an instruction to update the database.

Action: If the referenced function is a packaged, PL or SQL function: Recreate the PL or 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 or SQL function: Do not use the function.

ORA-06570: shared pool object does not exist, cannot be pinned

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: Remove the procedure from the calling stored procedure.

ORA-06569: Collection bound by bind_array contains no elements

ORA-06569: Collection bound by bind_array contains no elements

Cause: A collection with zero elements was bound to a bind variable in a call to procedure BIND_ARRAY in the package DBMS_SQL. In order to execute a bind of a collection, the collection must contain at least one element. If no elements are present then at execute time there will be no value for this bind and the statement is meaningless.

Action: Fill the collection with the elements you want to bind and try the bind call again.

ORA-06568: obsolete ICD procedure called

ORA-06568: obsolete ICD procedure called

Cause: An obsolete ICD procedure was called by a PL or SQL program. The PL or SQL program was probably written for an eralier release of RDBMS.

Action: Make sure that all PL or SQL programs have been upgraded to the latest release of the RDBMS. This can be accomplished by following upgrade instructions in the README file, or by running the catproc.sql script supplied with the RDBMS.

ORA-06567: invalid number of values specified

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. In order to execute a given parsed statement in a given cursor, the same number of values must have been bound for all bind variables, so when EXECUTE is called, the latest calls to BIND_VARIABLE must must have specified the same number of values to be bound for all bind variables.

Action: Make sure that the same number of values have been bound for all of the bind variables.

ORA-06566: invalid number of rows specified

ORA-06566: invalid number of rows specified

Cause: An invalid number of rows was specified in a call to the procedure 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 that for previously defined columns.

ORA-06565: cannot execute string from within stored procedure

ORA-06565: cannot execute string 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 or sql anonymous blocks.

Action: Remove the procedure from the calling stored procedure.

ORA-06564: object string does not exist

ORA-06564: object string 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-06563: top level procedure or function specified, cannot have subparts

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 (which don t 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-06562: type of out argument must match type of column or bind variable

ORA-06562: type of out argument must match type of column or bind variable

Cause: Attempting to get the value of a column or a bind variable by calling procedure COLUMN_VALUE or VARIABLE_VALUE of package DBMS_SQL but the type of the given out argument where to place the value is 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-06561: given statement is not supported by package DBMS_SQL

ORA-06561: given statement is not supported by package DBMS_SQL

Cause: Attempting to parse an unsupported statement using procedure PARSE provided by package DBMS_SQL.

Action: Only statements which begin with SELECT, DELETE, INSERT, UPDATE, LOCK, BEGIN, DECLARE or lamp;lt;lamp;nbsp;lamp;lt;lamp;nbsp; (PL or SQL label delimiter) are supported.

ORA-06560: pos, string, is negative or larger than the buffer size, string

ORA-06560: pos, string, is negative or larger than the buffer size, string

Cause: Internal error from the dbms_pipe package.

Action: none

ORA-06559: wrong datatype requested, string, actual datatype is string

ORA-06559: wrong datatype requested, string, actual datatype is string

Cause: The sender put different datatype on the pipe than that being requested (package dbms_pipe ). The 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-06558: buffer in dbms_pipe package is full. No more items allowed

ORA-06558: buffer in dbms_pipe package is full. No more items allowed

Cause: The pipe buffer size has been exceeded.

Action: none

ORA-06557: null values are not allowed for any parameters to pipe icd s

ORA-06557: null values are not allowed for any parameters to pipe icd s

Cause: Internal error from the dbms_pipe package.

Action: none

ORA-06556: the pipe is empty, cannot fulfill the unpack_message request

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-06555: this name is currently reserved for use by user SYS

ORA-06555: this name is currently reserved for use by user SYS

Cause: You tried to create a package named STANDARD , DBMS_STANDARD or DEBUG_IO . These are currently reserved for use by user SYS.

Action: Choose another name for your package.

ORA-06554: package DBMS_STANDARD must be created before using PL or SQL

ORA-06554: package DBMS_STANDARD must be created before using PL or SQL

Cause: The DBMS specific extensions to PL or SQL s package STANDARD are in package DBMS_STANDARD . This package must be created before using PL or SQL.

Action: Create package DBMS_STANDARD . The source for this PL or SQL stored package is provided with the distribution.

ORA-06550: line string, column string: string

ORA-06550: line string, column string: string

Cause: Usually a PL or SQL compilation error.

Action: none

ORA-06549: PL or SQL: failed to dynamically open shared object (DLL): string

ORA-06549: PL or SQL: failed to dynamically open shared object (DLL): string

Cause: One possible cause might be there are too many DLLs open at the same time.

Action: -------------------------------------------------------

ORA-06548: no more rows needed

ORA-06548: no more rows needed

Cause: The caller of a pipelined function does not need more rows to be produced by the pipelined function.

Action: Catch the NO_DATA_NEEDED exception is an exception handling block.

ORA-06547: RETURNING clause must be used with INSERT, UPDATE, or DELETE statements

ORA-06547: RETURNING clause must be used with INSERT, UPDATE, or DELETE statements

Cause: EXECUTE IMMEDIATE with a RETURNING clause is used to execute dynamic UPDATE, INSERT, or DELETE statements only.

Action: use RETURNING clause in EXECUTE IMMEDIATE for INSERT, UPDATE, or DELETE statements only. For other statements, use USING clause instead.

ORA-06546: DDL statement is executed in an illegal context

ORA-06546: DDL statement is executed in an illegal context

Cause: DDL statement is executed dynamically in illegal PL or SQL context. - Bind variable s used in USING clause to EXECUTE IMMEDIATE a DDL - Define variable s used in INTO clause to EXECUTE IMMEDIATE a DDL

Action: Use EXECUTE IMMEDIATE without USING and INTO clauses to execute the DDL statement.

ORA-06545: PL or SQL: compilation error - compilation aborted

ORA-06545: PL or SQL: compilation error - compilation aborted

Cause: A pl or sql compilation error occurred and the compilation was aborted completely without the compilation unit being written out to the backing store. Unlike ora-06541, the user will always see this error along with the accompaning PLS-nnnnn error messages.

Action: See accompanying PLS-nnnnn error messages.

ORA-06544: PL or SQL: internal error, arguments: (string(, (string(, (string(, (string(, (string(, (string(, (string(, (string(

ORA-06544: PL or SQL: internal error, arguments: (string(, (string(, (string(, (string(, (string(, (string(, (string(, (string(

Cause: A pl or sql internal error occurred.

Action: Report as a bug; the first argument is the internal error nuber.

ORA-06541: PL or SQL: compilation error - compilation aborted

ORA-06541: PL or SQL: compilation error - compilation aborted

Cause: A pl or sql compilation error occurred and the compilation was aborted; but the compilation unit was written out to the backing store. However, unlike ora-06545, 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-06540: PL or SQL: compilation error

ORA-06540: PL or SQL: compilation error

Cause: A pl or 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-06539: target of OPEN must be a query

ORA-06539: target of OPEN must be a query

Cause: The program attempted to perform an OPEN cursor operation on a dynamic statement that was not a query.

Action: Ensure that the OPEN cursor operation is done on a dynamic query statement. -------------------------------------------------------- 06540 through 06549 reserved for pl or sql error handling

ORA-06538: statement violates string RESTRICT_REFERENCES pragma

ORA-06538: statement violates string RESTRICT_REFERENCES pragma

Cause: The program attempted to execute a dynamic statement which does not meet the purity level specified (in the pragma RESTRICT_REFERENCES directive) for the module executing the statement.

Action: Ensure that the dynamic statement meets the purity level specified for the module executing the statement.

ORA-06537: OUT bind variable bound to an IN position

ORA-06537: OUT bind variable bound to an IN position

Cause: The program attempted to bind an OUT bind variable to a statement that was expecting an IN bind variable at that position.

Action: Make sure that an IN or IN OUT bind mode is specified for the bind argument.

ORA-06536: IN bind variable bound to an OUT position

ORA-06536: IN bind variable bound to an OUT position

Cause: The program attempted to bind an IN bind variable to a statement that was expecting an OUT bind variable at that position.

Action: Make sure that an OUT or IN OUT bind mode is specified for the bind argument.

ORA-06535: statement string in string is NULL or 0 length

ORA-06535: statement string in string is NULL or 0 length

Cause: The program attempted to use a dynamic statement string that was either NULL or 0 length.

Action: Check the program logic and ensure that the dynamic statement string is properly initialized.

ORA-06534: Cannot access Serially Reusable package string

ORA-06534: Cannot access Serially Reusable package string

Cause: The program attempted to access a Serially Reusable package in PL or SQL called from SQL context (trigger or otherwise). Such an access is currently unsupported.

Action: Check the program logic and remove any references to Serially Reusable packages (procedure, function or variable references) which might happen in PL or SQL called from sql context (trigger or otherwise).

ORA-06533: Subscript beyond count

ORA-06533: Subscript beyond count

Cause: An in-limit subscript was greater than the count of a varray or too large for a nested table.

Action: Check the program logic and explicitly extend if necessary.

ORA-06532: Subscript outside of limit

ORA-06532: Subscript outside of limit

Cause: A subscript was greater than the limit of a varray or non-positive for a varray or nested table.

Action: Check the program logic and increase the varray limit if necessary.

ORA-06531: Reference to uninitialized collection

ORA-06531: Reference to uninitialized collection

Cause: An element or member function of a nested table or varray was referenced (where an initialized collection is needed) without the collection having been initialized.

Action: Initialize the collection with an appropriate constructor or whole-object assignment.

ORA-06530: Reference to uninitialized composite

ORA-06530: Reference to uninitialized composite

Cause: An object, LOB, or other composite was referenced as a left hand side without having been initialized.

Action: Initialize the composite with an appropriate constructor or whole-object assignment.

ORA-06529: Version mismatch - PL or SQL profiler

ORA-06529: Version mismatch - PL or SQL profiler

Cause: The PL or SQL profiler package (dbmspb.sql, prvtpbp.plb) does not match the version of the code in the server implementing the profiler.

Action: Run the package profload.sql in $ORACLE_HOME or rdbms or admin to load the correct version of the PL or SQL profiler packages

ORA-06528: Error executing PL or SQL profiler

ORA-06528: Error executing PL or SQL profiler

Cause: An error occurred in during execution of a PL or SQL profiler procedure.

Action: Check the stacked errors for more details.

ORA-06527: External procedure SQLLIB error: string

ORA-06527: External procedure SQLLIB error: string

Cause: An error occurred in sqllib during execution of a Pro* external procedure.

Action: The message text indicates the actual SQLLIB error that occurred. Consult the Oracle Error Messages and Codes manual for a complete description of the error message and follow the appropriate action.

ORA-06526: Unable to load PL or SQL library

ORA-06526: Unable to load PL or SQL library

Cause: PL or SQL was unable to instantiate the library referenced by this referenced in the EXTERNAL syntax. This is a serious error and should normally not happen.

Action: Report this problem to customer support.

ORA-06525: Length Mismatch for CHAR or RAW data

ORA-06525: Length Mismatch for CHAR or RAW data

Cause: The length specified in the length variable has an illegal value. This can happen if you have requested requested a PL or SQL INOUT, OUT or RETURN raw variable to be passed as a RAW with no corresponding length variable. This error can also happen if there is a mismatch in the length value set in the length variable and the length in the orlvstr or orlraw.

Action: Correct the external procedure code and set the length variable correctly.

ORA-06524: Unsupported option : string

ORA-06524: Unsupported option : string

Cause: The option specified is an unsupported feature for external procedures.

Action: Correct the syntax in the external specification