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

## 02100-02139: Oracle Runtime Library SQL Messages

The following error messages might be issued at runtime by SQLLIB, the Oracle runtime library.

##### SQL-02100: out of memory (i.e., could not allocate)

Cause: SQLLIB was unable to allocate enough memory to execute the program.

Action: Allocate more memory to the user session, then rerun the program. If the error persists, call customer support for assistance.

##### SQL-02101: inconsistent cursor cache. Unit cursor/global cursor mismatch

Cause: This internal error typically indicates a memory-related error.

Action: Check the program for memory-related errors, such as invalid pointers or array-bounds violations.

##### SQL-02102: inconsistent cursor cache. No global cursor entry

Cause: This internal error typically indicates a memory-related error.

Action: Check the program for memory-related errors, such as invalid pointers or array-bounds violations.

##### SQL-02103: inconsistent cursor cache. Out of range cursor cache reference

Cause: This internal error typically indicates a memory-related error.

Action: Check the program for memory-related errors, such as invalid pointers or array-bounds violations.

##### SQL-02104: inconsistent host cache. No cursor cache available

Cause: This internal error typically indicates a memory-related error.

Action: Check the program for memory-related errors, such as invalid pointers or array-bounds violations.

##### SQL-02105: inconsistent cursor cache. Global cursor not found

Cause: This internal error typically indicates a memory-related error.

Action: Check the program for memory-related errors, such as invalid pointers or array-bounds violations.

##### SQL-02106: inconsistent cursor cache. Invalid Oracle cursor number

Cause: This internal error typically indicates a memory-related error.

Action: Check the program for memory-related errors, such as invalid pointers or array-bounds violations.

##### SQL-02107: program too old for runtime library; please re-precompile it

Cause: The program was precompiled by an older version of the Oracle Precompilers, which is incompatible with this release of SQLLIB.

Action: Precompile the program with a newer version of the Oracle Precompilers.

##### SQL-02108: invalid descriptor passed to run-time library

Cause: This internal error typically indicates a memory-related error.

Action: Check the program for memory-related errors, such as invalid pointers or array-bounds violations.

##### SQL-02109: inconsistent host cache. Host reference is out of range

Cause: This internal error typically indicates a memory-related error.

Action: Check the program for memory-related errors, such as invalid pointers or array-bounds violations.

##### SQL-02110: inconsistent host cache. Invalid host cache entry type

Cause: This internal error typically indicates a memory-related error.

Action: Check the program for memory-related errors, such as invalid pointers or array-bounds violations.

##### SQL-02111: heap consistency error

Cause: This internal error typically indicates a memory-related error.

Action: Check the program for memory-related errors, such as invalid pointers or array-bounds violations.

##### SQL-02112: SELECT ... INTO returns too many rows

Cause: A SELECT ... INTO statement returned more rows than can be stored in the host variable provided.

Action: There are three possible solutions:

- Use the precompiler option SELECT_ERROR=NO.
- Declare a host variable with a larger array dimension.
- Declare a cursor or cursor variable for the select statement.

##### SQL-02113: unable to open message file

Cause: SQLLIB was unable to find or open the file, ora_sqllib:sqlli*.msb.

Action: Check that ora_sqllib is properly defined, and that a sqlli*.msb file exists and is readable.

##### SQL-02114: invalid SQL Cursor usage: trying to CLOSE a CLOSEd cursor

Cause: An attempt was made to CLOSE a cursor that was already CLOSEd with MODE={ANSI|ANSI14}. A CLOSEd cursor can be re-CLOSEd only when MODE={ORACLE|ANSI13}.

Action: When MODE={ANSI|ANSI14}, verify that a cursor is not already CLOSEd before trying to CLOSE it. Specify MODE={ORACLE|ANSI13} if a CLOSEd cursor is to be re-CLOSEd.

##### SQL-02115: code interpretation problem -- check COMMON_NAME usage

Cause: With Pro*FORTRAN, this error occurs if the precompiler option COMMON_NAME is specified incorrectly. With other Oracle Precompilers, this error occurs when the precompiler cannot generate a segment of code.

Action: With Pro*FORTRAN, when using COMMON_NAME to precompile two or more source modules, make sure to specify a different common name for each module. With other Oracle Precompilers, if the error persists, call customer support for assistance.

##### SQL-02116: FATAL ERROR: Reentrant code generator gave invalid context

Cause: This internal error typically indicates a memory-related error.

Action: Check the program for memory-related errors, such as invalid pointers or array-bounds violations.

##### SQL-02117: invalid SQL Cursor usage: trying to OPEN an OPENed cursor

Cause: An attempt was made to OPEN an cursor that was already OPENed with MODE={ANSI|ANSI14|ANSI13}. An open cursor can be re-OPENed only when MODE=ORACLE.

Action: When MODE={ANSI|ANSI14|ANSI13}, verify that a cursor is not already OPEN before trying to OPEN it. Specify MODE=ORACLE if an OPENed cursor is to be re-OPENed to avoid reparsing.

##### SQL-02118: invalid row for a WHERE CURRENT OF operation

Cause: An attempt was made to reference a nonexistent row using the CURRENT OF clause in an UPDATE or DELETE statement. This happens when no FETCH has been executed or when FETCH returns a "no data found" error that the program fails to trap.

Action: Check that the last cursor operation succeeded and that the current row of the cursor is valid. The outcome of a cursor operation can be checked in two ways: implicit checking with the WHENEVER statement or explicit checking of SQLCODE in the SQLCA.

##### SQL-02119: invalid HSTDEF argument

Cause: A non-null pointer was given for an HSTDEF as the second argument to a SQLRCN call when the first argument was also used. Either the first or the second argument to SQLRCN must be null.

Action: Pass a null pointer in either the first or second argument to SQLRCN.

##### SQL-02120: first and second arguments to SQLRCN both null

Cause: Both the first and second arguments to SQLRCN were null. An HSTDEF must be passed into SQLRCN in the form of either an OCI LDA (first argument) or as an HSTDEF pointer itself (second argument).

Action: Pass either an OCI LDA or a HSTDEF, but not both.

##### SQL-02121: invalid host name

Cause: The host name passed into a SQLFCN call was not used in a previous call to SQLRCN.

Action: Use the same identifier used in the corresponding SQLRCN call.

##### SQL-02122: invalid OPEN or PREPARE for this database connection

Cause: An attempt was made to execute an OPEN or PREPARE statement using a cursor that is currently open for another database connection and, therefore, cannot be used for this connection.

Action: Close the cursor to make it available for this connection or use a different cursor for this connection.

##### SQL-02123: context referenced in EXEC TOOLS GET CONTEXT statement not found

Cause: The context name given in the EXEC TOOLS GET CONTEXT statement was never stored with an EXEC TOOLS SET CONTEXT statement.

Action: Use the EXEC TOOLS SET CONTEXT statement to save any contexts to be retrieved later.

##### SQL-02124: NULL value returned by EXEC TOOLS statement

Cause: An EXEC TOOLS statement returned a null to a host variable that lacks an indicator variable. This error occurs only when MODE=ANSI. When MODE=ORACLE, although the value of the host variable is indeterminate, no error is generated.

Action: Associate an indicator variable with each host variable to which nulls might be returned.

##### SQL-02125: connect error, can't get error text

Cause: No connection (not even to the default host) was available, so SQLLIB could not get the message text for the Oracle error that occurred. However, SQLLIB returns the Oracle error number, which can be used to look up the message.

Action: Look up the appropriate message in Oracle8 Server Messages and follow the Cause and Action information provided.

##### SQL-02126: number of array elements cannot be negative (i.e. < 0)

Cause: The precompiler found a negative number of array elements in the N or F variable of the SQLDA (SQL Descriptor Area, which is used with dynamic SQL Method 4). Before executing the DESCRIBE statement, N must be set to the dimension of the descriptor arrays. After executing the DESCRIBE statement, N must be reset to the actual number of variables DESCRIBEd, which is stored in the F variable.

Action: Check that the N and F variables are set to non-negative values.

##### SQL-02127: Precompiler/SQLLIB version mismatch

Cause: The program was linked to an older version of SQLLIB, which is incompatible with this release of the Oracle Precompilers.

Action: Relink the program with the appropriate version of SQLLIB.

##### SQL-02128: sessions still exist, not logged off

Cause: A host was not removed ("logged off") from SQLLIB because XA still has sessions associated with that host.

Action: Before calling SQLXDH to drop a host, XA must either drop all sessions for that host or set the doit_anyway flag.

##### SQL-02129: FETCHed number of bytes is odd

Cause: The program tried to FETCH an invalid column value into a multi-byte NLS host variable. Specifically, the column did not contain valid double-byte data.

Action: Make sure the column contains only double-byte data. To verify this, use SQL*Plus or Server Manager.

##### SQL-02130: EXEC TOOLS interface is not available

Cause: An attempt was made to link with a version of an Oracle tool that does not support the EXEC TOOLS interface.

Action: Either upgrade the Oracle tool, or use the EXEC IAF interface.

##### SQL-02131: runtime context in use

Cause: Your application attempted to execute a SQL statement using a runtime context that is already in use.

Action: Rewrite the application either to wait for one thread to complete before executing another SQL statement with the same runtime context, or to allocate and use a separate runtime context for each thread.

##### SQL-02132: unable to allocate runtime context

Cause: An attempt to allocate a runtime context failed.

Action: This error typically occurs when the process memory is low. Allocate more memory and run the application again.

##### SQL-02133: unable to initialize process for use with threads

Cause: This is an internal error.

Action: Call Oracle customer support.

##### SQL-02134: invalid runtime context

Cause: The runtime context associated with an executable SQL statement was not properly allocated.

Action: Rewrite your application to execute the EXEC SQL CONTEXT ALLOCATE statement before executing any SQL statements.

##### SQL-02135: unable to initialize date format using supplied mask

Cause: The runtime library was unable to issue a set date format statement with the date format mask supplied.

Action: Check the validity of the date format and correct if necessary. Check the ORA error number for further information.

##### SQL-02136: invalid NCHAR character set id

Cause: An attempt was made to bind or define an NCHAR host variable, but the NLS_NCHAR variable was not set during precompilation.

Action: Set the NLS_NCHAR environment variable and re-precompile the application.

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