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

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-02115: Code interpretation problem -- check COMMON_NAME usage

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 section 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-02114: Invalid SQL Cursor usage: trying to CLOSE a CLOSEd cursor

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-02113: Unable to open message file

SQL-02113: Unable to open message file

Cause: SQLLIB was unable to find or open the sqllib message file sql*.msb

Action: Check that the file exists in the mesg directory and that it is readable

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

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 3 possible solutions: 1. Use the precompiler option select_error=no. 2. Declare a host variable with a larger array dimension. 3. Declare a cursor or cursor variable for the select statement.

SQL-02111: Heap consistency error

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-02110: Inconsistent host cache. Invalid host cache entry type

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-02109: Inconsistent host cache. Host reference is out of range

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-02108: Invalid descriptor passed to run-time library

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-02107: Program too old for runtime library; please re-precompile it

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-02106: Inconsistent cursor cache. Invalid Oracle cursor number

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-02105: Inconsistent cursor cache. Global cursor not found

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-02104: Inconsistent host cache. No cursor cache available

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-02103: Inconsistent cursor cache. Out of range cursor cache reference

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-02102: Inconsistent cursor cache. No global cursor entry.

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-02101: Inconsistent cursor cache. Unit cursor or global cursor mismatch

SQL-02101: Inconsistent cursor cache. Unit cursor or 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-02100: Out of memory (i.e., could not allocate)

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-01075: you are currently logged on

SQL-01075: you are currently logged on

Cause: There is already a connection on this host.

Action: Do not attempt the second connection.

PCC-02451: Value of offset cannot be negative in ABSOLUTE orientation mode

PCC-02451: Value of offset cannot be negative in ABSOLUTE orientation mode

Cause: The offset for the FETCH ABSOLUTE statement is negative.

Action: Value of offset should be positive.

PCC-02450: Cursor was not declared in scrollable mode

PCC-02450: Cursor was not declared in scrollable mode

Cause: A cursor which was not DECLAREd in SCROLL mode was used in scrollable mode in the FETCH statement.

Action: Declare the cursor in scroll mode using the SCROLL keyword.