AUD-00809: ORDSpeechIndex: unable to ALTER REBUILD internal Text index

AUD-00809: ORDSpeechIndex: unable to ALTER REBUILD internal Text index

Cause: ALTER INDEX REBUILD for ORDSpeechIndex failed when trying to alter rebuild internal Text index.

Action: Make sure that you are supplying a valid parameter string. See SpeechIndexing and Oracle Text documentation for descriptions of a valid parameter string for ALTER INDEX REBUILD. To return to a consistent state, issue a ALTER INDEX REBUILD PARAMETERS( optimize full ) command.

AUD-00808: ORDSpeechIndex: unable to CREATE internal Text index

AUD-00808: ORDSpeechIndex: unable to CREATE internal Text index

Cause: CREATE INDEX for ORDSpeechIndex failed when trying to create internal Text index.

Action: Make sure that you are supplying a valid parameter string. See SpeechIndexing and Oracle Text documentation for descriptions of a valid parameter string for CREATE INDEX. To return to a consistent state, issue a DROP INDEX command.

AUD-00807: SpeechContains: index of indextype ORDSpeechIndex is required

AUD-00807: SpeechContains: index of indextype ORDSpeechIndex is required

Cause: SpeechContains was used without an associated index of indextype ORDSpeechIndex.

Action: Make sure that SpeechContains is used in the context of an index of indextype ORDSpeechIndex. See the Oracle interMedia documentation for sample usage scenarios.

AUD-00806: first argument to SpeechContains must be a column

AUD-00806: first argument to SpeechContains must be a column

Cause: The first argument to SpeechContains is not a column. This is not allowed.

Action: Make sure that the first argument to SpeechContains is a column in a database table.

AUD-00803: internal error while processing WHERE clause

AUD-00803: internal error while processing WHERE clause

Cause: The WHERE clause could not be properly processed.

Action: Contact Oracle Support Services.

AUD-00802: name of index is limited to 22 characters

AUD-00802: name of index is limited to 22 characters

Cause: The user specified an index name that is more than 22 characters long.

Action: Drop this index, and issue the CREATE INDEX statement again with a name that is at most 22 characters long.

AUD-00721: unable to find format plug-in package ORDPLUGINS.ORDX_string_ AUDIO

AUD-00721: unable to find format plug-in package ORDPLUGINS.ORDX_string_ AUDIO

Cause: Custom audio plug-in for user-specified format was not found.

Action: Ensure correct audio format is specified or proper custom audio plug-in package is installed.

AUD-00714: internal error

AUD-00714: internal error

Cause: An internal error occurred.

Action: Contact Oracle Support Services.

AUD-00713: internal error while parsing audio data

AUD-00713: internal error while parsing audio data

Cause: An internal error occurred during parsing.

Action: Contact Oracle Support Services.

AUD-00707: unable to read empty audio data

AUD-00707: unable to read empty audio data

Cause: There is no data in the audio object.

Action: Refer to the Oracle interMedia documentation for information on how to populate the audio object with audio data.

AUD-00706: unsupported or corrupted input format

AUD-00706: unsupported or corrupted input format

Cause: The audio data was either corrupted or the file format was not supported.

Action: Refer to the interMedia documentation for supported formats. If the audio data is not corrupted and is in a supported file format, contact Oracle Support Services.

AUD-00705: unsupported input format

AUD-00705: unsupported input format

Cause: The file format of the audio data was not supported. This error can only occur in the DEFAULT format plug-in package.

Action: Refer to the interMedia documentation for supported formats.

AUD-00704: invalid input format

AUD-00704: invalid input format

Cause: The audio data in the source was not in the format specified by the format field of the audio object. In some unusual cases, the audio data is actually corrupted.

Action: Provide a correct value in the format field. If the correct value is unknown, put NULL in the format field to invoke the DEFAULT format plug-in.

AUD-00703: unable to read audio data

AUD-00703: unable to read audio data

Cause: An error occurred while accessing the audio source.

Action: Make sure the audio source is valid. For external sources, make sure all access priviliges are granted.

AUD-00702: unable to initialize audio processing environment

AUD-00702: unable to initialize audio processing environment

Cause: The initalization of the audio processing procedure failed.

Action: See the database administrator to make sure that enough memory has been allocated to JServer. If JServer does have enough memory, contact Oracle Support Services.

AUD-00614: I or O error during export

AUD-00614: I or O error during export

Cause: The export operation failed because of an I or O error.

Action: Check OS logs and contact Oracle Support Services.

AUD-00613: export destination access denied

AUD-00613: export destination access denied

Cause: Permission to write to destination file was denied.

Action: Refer to the Oracle interMedia documentation for information on granting privileges for the export() method.

AUD-00612: unable to open export destination file

AUD-00612: unable to open export destination file

Cause: The file could not be created or opened.

Action: Check that the file does not refer to an existing directory. Check that the file is not locked by another application.

AUD-00611: unable to access the BLOB for reading

AUD-00611: unable to access the BLOB for reading

Cause: The BLOB could not be opened for reading.

Action: Contact Oracle Support Services.

SQL-02157: Source or destination lob is invalid

SQL-02157: Source or destination lob is invalid

Cause: One of the lobs used in the lob append call is invalid or possibly null.

Action: Make sure the lobs used in the append call are non-null.

SQL-02156: Invalid type for Indicator or Returned Length

SQL-02156: Invalid type for Indicator or Returned Length

Cause: A host variable associated with the item Indicator or Returned Length must be of type short or s9(4) comp. If value semantics and scalar they may also be gotten into display sign leading separate host variables

Action: Use signed short for indicator, ref indicator and returned length, ref returned length host variables in C. For COBOL use s9(4) comp. for GETs only with non-arrays and you may use display sign leading separate host variables

SQL-02155: Date Time Interval only valid with Dynamic=ANSI

SQL-02155: Date Time Interval only valid with Dynamic=ANSI

Cause: An attempt to access the datetime interval code or precision was encountered when type_code option not set to ANSI

Action: Use precompiler option type_code=ansi to access the date time interval code or date time interval precision

SQL-02154: Invalid or unset data type for host variable in ANSI Dynamic

SQL-02154: Invalid or unset data type for host variable in ANSI Dynamic

Cause: An ANSI Dynamic SET statement with item name DATA was encountered with out a valid TYPE having been previously set and option mode=ansi was used

Action: With mode=ansi, you must set the TYPE before setting the DATA. Issue a SET statement with correct item TYPE or, for output issue a DESCRBE to set the item type. Or use mode=oracle which allows the type to default to the type of the bind or define host variable

SQL-02153: Invalid character variable for use in a GET or SET statement

SQL-02153: Invalid character variable for use in a GET or SET statement

Cause: An host variable with type other than character, string or varchar was found as an item name (other than DATA item) in an ANSI Dynamic GET or SET descriptor statement.

Action: Host variable types for character items (other than the DATA item) in ANSI dynamic GET or SET descriptor statements must not be of type LONG or LONG VARCHAR. Redeclare the variable to be character, string or varchar type

SQL-02152: Invalid numeric variable for use in an array GET or SET statement

SQL-02152: Invalid numeric variable for use in an array GET or SET statement

Cause: An host variable with type other than int or short for C or S9(4) or S9(9) binary or comp was used for an exact numeric with and array size lamp;gt; 1.

Action: Use only int or short for C or S9(4) or S(9) binary or comp for COBOL when supplying an exact numeric in conjunction with the for clause to indicate arrays. Specifically, display sign leading separate is not allowed in this context.

SQL-02151: Invalid host variable for exact numeric SET statement item

SQL-02151: Invalid host variable for exact numeric SET statement item

Cause: An host variable with an invalid type or length was used to get or set an exact numeric item in an ANSI dynamic statement.

Action: Make sure your host variable is and int or short for C or for COBOL, S9(4) or S9(9) binary or comp or display sign leading separate.

SQL-02150: Encountered zero length in ANSI dynamic SET statement

SQL-02150: Encountered zero length in ANSI dynamic SET statement

Cause: An invalid length of zero was encountered in an ANSI dynamic statement.

Action: Set the length to a non-zero value

SQL-02149: ANSI Dynamic insufficient item descriptor areas

SQL-02149: ANSI Dynamic insufficient item descriptor areas

Cause: The SQL statement being described contains more output items (or columns) than were allocated in the descriptor.

Action: Increase the MAX number of occurrences when allocating the descriptor.

SQL-02148: ANSI Dynamic count value out of range

SQL-02148: ANSI Dynamic count value out of range

Cause: The count in a dynamic GET or SET statement is less than one or greater than MAX given for descriptor allocation.

Action: Supply a number for the COUNT clause between 1 and the MAX occurrences supplied when the descriptor was allocated.

SQL-02147: ANSI Dynamic occurrence value out of range

SQL-02147: ANSI Dynamic occurrence value out of range

Cause: The value clause in a dynamic GET or SET statement is less than one or greater than MAX given for descriptor allocation.

Action: Supply a number for the VALUE clause between 1 and the MAX occurrences supplied when the descriptor was allocated.

SQL-02146: Attempt to allocate an existing descriptor

SQL-02146: Attempt to allocate an existing descriptor

Cause: An attempt allocated a descriptor which has previously been allocated was encountered.

Action: Use and unique descriptor name or deallocate the descriptor before attempting to reallocate it.

SQL-02145: Invalid dynamic descriptor

SQL-02145: Invalid dynamic descriptor

Cause: An attempt to access an unallocated or invalid descriptor was encountered.

Action: For ANSI descriptors, check that descriptor name is valid and descriptor has been allocated and not previously deallocated. Or if using Oracle descriptors (sqlda) with mode=ansi also use dynamic=oracle.

SQL-02144: Invalid ANSI dynamic usage

SQL-02144: Invalid ANSI dynamic usage

Cause: An ANSI allocate, deallocate, get or set descriptor statement was encountered when dynamic option was not set.

Action: Precompile your source with option dynamic=ansi.

SQL-02143: Target object has not been properly allocated

SQL-02143: Target object has not been properly allocated

Cause: An attempt was made to retrieve elements from a collection into an unallocated object pointer.

Action: Allocate the object pointer with the EXEC SQL ALLOCATE statement.

SQL-02142: Collection is NULL

SQL-02142: Collection is NULL

Cause: The collection referenced in an EXEC SQL COLLECTION statement is null.

Action: Check the status of the associated indicator variable prior to executing an EXEC SQL COLLECTION statement.

SQL-02141: Collection descriptor has not been allocated

SQL-02141: Collection descriptor has not been allocated

Cause: An unallocated collection descriptor was referenced in a COLLECTION SET or COLLECTION GET statement.

Action: Allocate the collection descriptor with the EXEC SQL ALLOCATE statement. e.g. EXEC SQL ALLOCATE :coldesc_p;

SQL-02140: An unnamed connection already exists

SQL-02140: An unnamed connection already exists

Cause: An attempt to register an external procedure context was made when an unnamed connection already exists for the runtime context.

Action: Do not attempt to establish any connections with the EXEC SQL CONNECT statement from external procedures.

SQL-02139: Unable to get the OCI handles

SQL-02139: Unable to get the OCI handles

Cause: The call to OCIExtProcGetEnv failed.

Action: Ensure that the OCIExtProcContext that the external procedure has been created with a CONTEXT parameter and that this context is correctly referenced in the EXEC SQL REGISTER CONNECT statement.

SQL-02138: No external procedure context exists

SQL-02138: No external procedure context exists

Cause: The external procedure context passed in the EXEC SQL REGISTER CONNECT statement is not valid.

Action: Ensure that you have done the following: 1. Created the PL or SQL procedure or function with a CONTEXT parameter. 2. Included OCIExtProcContext in the formal parameter list of the external procedure 3. Correctly passed the OCIExtProcContext to the EXEC SQL REGISTER CONNECT statement.

SQL-02137: Multi-threaded agent with no RETURNING clause present

SQL-02137: Multi-threaded agent with no RETURNING clause present

Cause: The EXEC SQL REGISTER CONNECT statement does not contain a RETURNING clause and the agent is running in threaded mode.

Action: Re-code the statement to use a RETURNING clause that references a declared sql_context host variable.

SQL-02136: Invalid NCHAR character set id

SQL-02136: Invalid NCHAR character set id

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

Action: Set the NLS_NCHAR environment variable to a valid fixed width character set id and run the application again.

SQL-02135: Unable to initialize date format using supplied mask

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-02134: Invalid runtime context

SQL-02134: Invalid runtime context

Cause: The runtime context associated with this statement has not been properly allocated.

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

SQL-02133: Unable to initialize process for use with threads

SQL-02133: Unable to initialize process for use with threads

Cause: This is an internal error.

Action: Call customer support.

SQL-02132: Unable to allocate runtime context sdfla asdjklfajs jfja ajsdf

SQL-02132: Unable to allocate runtime context sdfla asdjklfajs jfja ajsdf

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-02131: Runtime context in use

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 to either 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-02130: EXEC TOOLS interface is not available.

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. EXEC TOOLS interface.

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

SQL-02129: Fetched number of bytes is odd.

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-02128: Sessions still exist, not logged off

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. *Note: This error *msg* is never actually used. The error *number* is used, given as a possible return value to the sqllib xa function sqlxdh.

SQL-02127: Precompiler or SQLLIB version mismatch

SQL-02127: Precompiler or 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 a newer version of SQLLIB

SQL-02126: Count of array elements cannot be negative (i.e. lamp;lt;lamp;nbsp; 0)

SQL-02126: Count of array elements cannot be negative (i.e. lamp;lt;lamp;nbsp; 0)

Cause: The precompiler found a negative number of array elements in the the N or F element 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 or F variables are set to non-negative values.

SQL-02125: Connect error, can t get error text

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 the Oracle7 Server Messages manual, and follow the Cause and Action information provided.

SQL-02124: NULL value returned by EXEC TOOLS statement

SQL-02124: NULL value returned by EXEC TOOLS statement

Cause: A NULL value was returned by EXEC TOOLS for a host variable that lacks an indicator variable. This error is returned 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-02123: Context referenced in EXEC TOOLS GET CONTEXT statement not found

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-02122: Invalid OPEN or PREPARE for this database connection

SQL-02122: Invalid OPEN or PREPARE for this database connection

Cause: An attempt was made to execute an OPEN or a 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-02121: Invalid host name

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. *Note: This error *msg* is never actually used. The error *number* is used, given as the return value of sqlfcn if this error occurs.

SQL-02120: First and second arguments to SQLRCN both null

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 either the form of an OCI lda (first argument) or as an HSTDEF pointer itself (second argument).

Action: Pass in either an OCI LDA or an HSTDEF, but not both. *Note: This error *msg* is never actually used. The error *number* is used, given as the return value of sqlrcn if this error occurs.

SQL-02119: Invalid HSTDEF argument

SQL-02119: Invalid HSTDEF argument

Cause: A non-null ptr was given for a hstdef as the second argument to a call to sqlrcn 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. *Note: This error *msg* is never actually used. The error *number* is used, given as the return value of sqlrcn if this error occurs.

SQL-02118: Invalid row for a WHERE CURRENT OF operation

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-02117: Invalid SQL Cursor usage: trying to OPEN an OPENed cursor

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

Cause: An attempt was made to OPEN a 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 OPENed before trying to OPEN it. Specify MODE=ORACLE if an OPENed cursor is to be re-OPENed.

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.

PCC-02449: Cannot type equivalence a UCS2 type

PCC-02449: Cannot type equivalence a UCS2 type

Cause: A UCS2 type has been type equivalenced in an EXEC SQL TYPE statement or a variable of UCS2 type has been type equivalenced in an EXEC SQL VAR statement.

Action: Remove the EXEC SQL TYPE or EXEC SQL VAR statement.

PCC-02448: Cannot specify a UCS2 variable in the NLS_NCHAR option

PCC-02448: Cannot specify a UCS2 variable in the NLS_NCHAR option

Cause: A variable declared as utext, uvarchar, or longuvarchar was specified in the NLS_NCHAR command line option.

Action: Re-precompile without specifying the variable in an NLS_NCHAR command line option.

PCC-02447: Cannot specify destination offset in a LOB WRITE APPEND

PCC-02447: Cannot specify destination offset in a LOB WRITE APPEND

Cause: A destination offset was specified in a LOB WRITE APPEND statement. The destination offset is assumed to be the end of the LOB so specifying an explicit destination offset is erroneous.

Action: Remove the destination offset from the LOB WRITE APPEND statement.

PCC-02446: FOR clause not allowed in a DEALLOCATE statement

PCC-02446: FOR clause not allowed in a DEALLOCATE statement

Cause: An explicit FOR clause was used in a DEALLOCATE DESCRIPTOR statement.

Action: Remove the FOR clause from the statement.

PCC-02445: USING clause valid only on a PREPAREd dynamic statement

PCC-02445: USING clause valid only on a PREPAREd dynamic statement

Cause: The USING clause was used with an OPEN cursor statement where the cursor declaration was not for a PREPAREd statement. The correct sequence of statements should be as follows EXEC SQL PREPARE s FROM :stmt; EXEC SQL DECLARE c CURSOR FOR s; EXEC SQL OPEN c USING ...;

Action: Use the PREPARE statement for the SQL statement and use that in the DECLARE CURSOR statement.

PCC-02444: Invalid combination of descriptor and non-descriptor clauses

PCC-02444: Invalid combination of descriptor and non-descriptor clauses

Cause: There was a mixing of descriptor and non-descriptor clauses in an ANSI Dynamic SQL statement.

Action: Do not mix descriptors and non-descriptors in the ANSI statement in question.

PCC-02443: This usage is only valid when DYNAMIC=ANSI is specified

PCC-02443: This usage is only valid when DYNAMIC=ANSI is specified

Cause: One of the following statements was used without specifying a DYNAMIC=ANSI command line option setting o EXEC SQL ALLOCATE or DEALLOCATE or GET or SET DESCRIPTOR o EXEC SQL DESCRIBE OUTPUT or INPUT ... USING ... lamp;lt;lamp;nbsp;descriptorlamp;gt; o EXEC SQL EXECUTE ... INTO ... o EXEC SQL EXECUTE ... USING ... lamp;lt;lamp;nbsp;descriptorlamp;gt; o EXEC SQL OPEN ... INTO ... o EXEC SQL OPEN ... USING ... lamp;lt;lamp;nbsp;descriptorlamp;gt;

Action: Specify DYNAMIC=ANSI or remove statements like those above from the program.

PCC-02442: Expecting a value between 1 and 65535 inclusive

PCC-02442: Expecting a value between 1 and 65535 inclusive

Cause: The value specified in the WITH MAX clause of an ALLOCATE DESCRIPTOR statement or the VALUE clause of a GET or SET DESCRIPTOR statement was either less than 1 or greater than 65535.

Action: Specify a value between 1 and 65535 inclusive.

PCC-02441: Number of attributes does not match number of host variables

PCC-02441: Number of attributes does not match number of host variables

Cause: There is a mismatch between the number of attributes and the number of valid host variables in the LOB or Collection DESCRIBE.

Action: Make sure that for each attribute being requested there is at most a single valid host variable given to hold its value.

PCC-02440: This attribute is valid for either internal or external LOBs

PCC-02440: This attribute is valid for either internal or external LOBs

Cause: A request for a LOB attribute was made in a LOB DESCRIBE statement in which the given LOB host variable was neither an Internal an External LOB (BFILE) type.

Action: Use either an Internal or External LOB host variable in the LOB DESCRIBE statement.

PCC-02439: FOR clause not allowed in this COLLECTION statement

PCC-02439: FOR clause not allowed in this COLLECTION statement

Cause: An illegal FOR clause was used in a COLLECTION statement that did not allow one, particularly, one of either the TRIM or DESCRIBE COLLECTION statements.

Action: Remove the FOR clause from the statement.

PCC-02438: Arrays of collection objects are not allowed

PCC-02438: Arrays of collection objects are not allowed

Cause: An array of collections was given in a COLLECTION statement. Only scalar (non-array) collection objects are allowed in any of the COLLECTION statements.

Action: Change the declaration of the Collection host variable so that it is not an array.

PCC-02437: Expecting an expression having binary integral type

PCC-02437: Expecting an expression having binary integral type

Cause: A host variable was given that was not declared to be of some acceptable binary numberic integral type. Generally, when this error occurs, a signed or unsigned integral type was expected. Floating point or otherwise imprecise numeric types are considered erroneous.

Action: Replace the problematic host variable with one that was declared using a proper exact numeric integral type.

PCC-02436: This attribute is only valid for external LOB types (BFILEs)

PCC-02436: This attribute is only valid for external LOB types (BFILEs)

Cause: A request for a LOB attribute was made in a LOB DESCRIBE statement in which the given LOB was not an External LOB type (BFILE).

Action: Use an External LOB (BFILE) host variable in the LOB DESCRIBE statement.

PCC-02435: This attribute is only valid for internal LOB types

PCC-02435: This attribute is only valid for internal LOB types

Cause: A request for a LOB attribute was made in a LOB DESCRIBE statement in which the given LOB was not of some Internal LOB type.

Action: Replace the LOB host variable in the LOB DESCRIBE with one that was declared to be an Internal LOB.

PCC-02434: FOR clause not permitted in any LOB statement

PCC-02434: FOR clause not permitted in any LOB statement

Cause: An explicit FOR clause was used in some LOB statement. The use of the FOR clause in LOB statements is erroneous.

Action: Remove the FOR clause.

PCC-02433: Invalid host variable and attribute pairing

PCC-02433: Invalid host variable and attribute pairing

Cause: The host variable and attribute pairing in a LOB or Collection DESCRIBE is invalid. Most likely, this was due to some problem with the host variable. For example, this error could occur if the host variable was not declared or is otherwise not provided.

Action: Usually, other, more specific, errors will accompany this one. Correcting some or all of those problems should resolve this error.

PCC-02432: Cannot open an external LOB (BFILE) in READ WRITE mode

PCC-02432: Cannot open an external LOB (BFILE) in READ WRITE mode

Cause: An attempt was made to OPEN a BFILE in READ WRITE mode. Writable BFILEs are currently not supported so this operation is considered erroneous.

Action: Do not open BFILEs using READ WRITE mode. BFILEs can only be OPENed in READ ONLY mode.

PCC-02431: Expecting an expression of type external LOB (BFILE)

PCC-02431: Expecting an expression of type external LOB (BFILE)

Cause: The given host variable was not declared to be an External LOB. Only BFILE would have been accepted in this case.

Action: Redeclare the host variable using an External LOB type (BFILE).

PCC-02430: Expecting an expression of some arbitrary LOB type

PCC-02430: Expecting an expression of some arbitrary LOB type

Cause: The given host variable was not declared to be any type of LOB, Internal or External. In addition to any Internal LOB type, BFILE would also have been accepted, however, the type of the host variable did not match any of these.

Action: Redeclare the host variable using any of the LOB types, Internal or External.

PCC-02429: Expecting an expression of some internal LOB type

PCC-02429: Expecting an expression of some internal LOB type

Cause: The given host variable was not declared to be an Internal LOB. BLOB, CLOB or NCLOB would have been accepted, however, the type of the host variable did not match any of these.

Action: Redeclare the host variable using one of the Internal LOB types.

PCC-02428: Buffer type is incompatible with LOB type

PCC-02428: Buffer type is incompatible with LOB type

Cause: This error can occur in either of the following situations 1. An attempt to READ from a LOB into a buffer whose type was not compatible with the LOB type. 2. An attempt to WRITE a buffer into a LOB whose type was not compatible with the buffer type.

Action: Either the LOB type or the buffer type needs to be changed so that the LOB and buffer types become compatible for the specified operation.

PCC-02427: Expression is not of the correct character string type

PCC-02427: Expression is not of the correct character string type

Cause: The given host variable expression was not declared to be of the required character type. In this case, one of several possible character types would have been accepted. However, the host variable type did not match any of them.

Action: Redeclare the problematic host variable, using one of the permitted character types.

PCC-02426: Incompatible LOB types

PCC-02426: Incompatible LOB types

Cause: A LOB operation was attempted between LOBs whose types were not compatible. For example, When ASSIGNing one LOB to another, both LOBs must be of the same type. If they are not, this error results.

Action: Correct the LOB operation by having it function between LOBs of the same type. This may require a redeclaration of one of the LOBs used in the LOB statement performing the specified operation.

PCC-02425: An indicator variable is not required with this attribute

PCC-02425: An indicator variable is not required with this attribute

Cause: In a LOB or Collection DESCRIBE, an Indicator Variable was used with a Host Variable when retrieving a LOB attribute that doesn t require one.

Action: Remove the Indicator Variable.

PCC-02424: The number of values and host variables does not match

PCC-02424: The number of values and host variables does not match

Cause: There is a mismatch between the number of values specified and the number of valid host variables given in a CONTEXT lamp;lt;lamp;nbsp;optionlamp;gt; OPTION SET (or GET) statement.

Action: Use the same number of host variables as there are values given in that particular statement.

PCC-02423: Host variable has an invalid type for this option value

PCC-02423: Host variable has an invalid type for this option value

Cause: The type of the host variable corresponding to a specific option value in a CONTEXT lamp;lt;lamp;nbsp;optionlamp;gt; OPTION SET (or GET) statement is invalid for that particular value.

Action: Use a type suitable for the specific value being manipulated.

PCC-02422: Invalid value specified for the given context option

PCC-02422: Invalid value specified for the given context option

Cause: An illegal value was given for the specified runtime context option in the CONTEXT lamp;lt;lamp;nbsp;optionlamp;gt; OPTION SET (or GET) statement.

Action: Use a valid option value in the statement for the specified option being manipulated by the statement.

PCC-02421: This host variable requires the use of an indicator variable

PCC-02421: This host variable requires the use of an indicator variable

Cause: No indicator variable was provided (or matched) with a specific host variable where one was explicitely required.

Action: Provide an indicator variable for use with the specified host variable in the given SQL statement.

PCC-02420: Incomplete (or missing) type specification

PCC-02420: Incomplete (or missing) type specification

Cause: An incomplete or perhaps missing type specification was given when declaring a host variable used in some SQL statement.

Action: Provide a complete type definition when declaring host variables intended for use inside any SQL statements.

PCC-02419: Host variable arrays not allowed in an OBJECT SET or GET

PCC-02419: Host variable arrays not allowed in an OBJECT SET or GET

Cause: An array was found in the host variable list of an OBJECT SET or GET statement.

Action: Only scalars are allowed (except for single dimensioned char or varchar variables) in the host variable list of an OBJECT SET or GET. Make sure to use only scalars in these statements.

PCC-02418: Array size mismatch between Object and REF host variables

PCC-02418: Array size mismatch between Object and REF host variables

Cause: The array sizes of the Object and REF variables in an OBJECT CREATE or DEREF do not match.

Action: Adjust the array dimensions of the two host variables so that they are equal to one another.

PCC-02417: Illegal type conversion between attribute and host variable

PCC-02417: Illegal type conversion between attribute and host variable

Cause: An illegal type conversion was attempted in a Navigational GET or SET statement between the type of the Attribute and the type of the Host Variable.

Action: Change the type of either the Attribute or the Host Variable.

PCC-02416: The Object in an OBJECT GET or SET must not be an array

PCC-02416: The Object in an OBJECT GET or SET must not be an array

Cause: The Object specified in an OBJECT GET or SET statement is an array which is illegal.

Action: Redeclare the Object so that it is not an array or subscript the Object so that only a single element of the Object array is specified.

PCC-02415: Cannot manipulate Object attributes in an OBJECT GET or SET

PCC-02415: Cannot manipulate Object attributes in an OBJECT GET or SET

Cause: An attempt was made to either GET or SET an attribute of an Object that itself was an Object or REF type.

Action: Remove the attribute from the attribute list in the statement.

PCC-02414: This attribute does not exist in the specified Object

PCC-02414: This attribute does not exist in the specified Object

Cause: An attribute given in the attribute list of an OBJECT SET or GET statement is not a member of the specified object in that statement.

Action: Remove the attribute from the list.

PCC-02413: Number of attributes does not match number of host variables

PCC-02413: Number of attributes does not match number of host variables

Cause: The number of attributes supplied in the attribute list of an OBJECT SET of GET statement does not match the total number of host variables also supplied in that statement.

Action: Either remove some attributes or remove some host variables from the statement in order to make the total count for each the same.

PCC-02412: FOR clause not permitted in OBJECT GET or SET statement

PCC-02412: FOR clause not permitted in OBJECT GET or SET statement

Cause: An explicit FOR clause was used in an OBJECT GET or OBJECT SET statement. Use of the FOR clause is illegal for these statements.

Action: Remove the FOR clause.

PCC-02411: Invalid type for INDICATOR descriptor item host variable

PCC-02411: Invalid type for INDICATOR descriptor item host variable

Cause: The type of the host variable paired with the INDICATOR descriptor item was invalid. The only permissable types for the INDICATOR item are a signed 2 byte numeric type or an indicator struct generated by the Object Type Translator for a user defined object type.

Action: Either replace the INDICATOR host variable with a valid one having an acceptable type or redeclare the existing host variable to be of a valid type.

PCC-02410: Expecting an expression of some Collection type.

PCC-02410: Expecting an expression of some Collection type.

Cause: The expression is not a Collection type. A VARRAY or Nested Table object was expected, but the given host variable did not resolve to a valid Collection type.

Action: Check that the OTT-generated header for the Collection type was properly #included in the Pro*C or C++ program and that the typefile was specified in the INTYPE option on the Pro*C or C++ command line.

PCC-02409: Expecting an expression of some REF type

PCC-02409: Expecting an expression of some REF type

Cause: The expression is not a REF type. For example, some host variables in the Navigational CREATE and DEREF statements are required to be declared of some REF type.

Action: Rewrite the expression or declare the variable to be a REF.

PCC-02408: Expecting an expression of some Object type

PCC-02408: Expecting an expression of some Object type

Cause: The expression is not an Object type. For example, many host variable expressions in the Navigational statements require that the variable be declared of some Object type.

Action: Rewrite the expression or declare the variable to be an Object.

PCC-02407: Object and REF types do not match

PCC-02407: Object and REF types do not match

Cause: In an OBJECT CREATE or DEREF statement, the types of the given Object and its associated REF do not match.

Action: Make sure that the Object and its REF have the same type. The type information is generated by OTT and should appear in the header file which OTT creates.

PCC-02406: Expecting the form RETURN(ING( REF INTO :lamp;lt;lamp;nbsp;reflamp;gt; only

PCC-02406: Expecting the form RETURN(ING( REF INTO :lamp;lt;lamp;nbsp;reflamp;gt; only

Cause: When using the RETURNING clause in an OBJECT CREATE statement, only a single REF INTO :lamp;lt;lamp;nbsp;host variablelamp;gt; is expected. This error occurs if the expression list to which REF belongs is greater than one or if there are more than one host variables supplied in the into list.

Action: Rewrite the RETURNING clause as per the given specification.

PCC-02405: Variable is of undefined type

PCC-02405: Variable is of undefined type

Cause: No declaration was found for the type identifier of the variable.

Action: Provide a valid declaration for the type of the host variable. If using objects in your program, check that the OTT-generated header for the object type was #included and that the typefile was specified in the INTYPE option on the Pro*C command line.

PCC-02404: This indicator variable must be declared as a pointer type

PCC-02404: This indicator variable must be declared as a pointer type

Cause: The specified indicator variable was not declared as pointer type.

Action: Declare the indicator variable to be a pointer type.

PCC-02403: Invalid indicator variable type for this host variable

PCC-02403: Invalid indicator variable type for this host variable

Cause: The type of the indicator variable is not appropriate for the specified host variable.

Action: Change the type of the indicator variable to a valid type. Refer to the Programmers Guide to the ORACLE Pro*C or C++ Precompiler for a discussion of appropriate indicator variable declarations.

PCC-02402: Pro*C option OBJECTS=YES is required when using the object cache

PCC-02402: Pro*C option OBJECTS=YES is required when using the object cache

Cause: The object cache will be used for this host variable, but OBJECTS=NO was specified on the Pro*C command line.

Action: Specify OBJECTS=YES on the Pro*C command line when using the object cache.

PCC-02401: Host variable arrays of this type are currently not supported

PCC-02401: Host variable arrays of this type are currently not supported

Cause: Host variable arrays of the specified type are not supported.

Action: Rewrite your program so that there are no arrays of this type.

PCC-02400: This host variable must be declared as a pointer type

PCC-02400: This host variable must be declared as a pointer type

Cause: The specified host variable was not declared as a pointer type.

Action: Declare the host variable to be a pointer type.

PCC-02399: Illegal CHAR_MAP option value for DBMS=V6. Option ignored.

PCC-02399: Illegal CHAR_MAP option value for DBMS=V6. Option ignored.

Cause: A CHAR_MAP option other than CHAR_MAP=VARCHAR2 was specified inline. Since DBMS=V6, this option is ignored for a character or string variable in the offending statement.

Action: Either set DBMS to something other than V6, or specify CHAR_ MAP=VARCHAR2.

PCC-02398: Indicator ignored in this statement for this type

PCC-02398: Indicator ignored in this statement for this type

Cause: An indicator variable was used in a host or indicator variable pair for some type in a statement that did not require or need one. Typically, indicator variables are not used in ALLOCATE and FREE statements for types other than object or collection types. They are also not used in OBJECT CREATE or DEREF statements for REF types.

Action: Remove the use of the indicator for the type in the specified statement. It will be ignored otherwise.

PCC-02397: VARCHAR declarations not permitted in #include file

PCC-02397: VARCHAR declarations not permitted in #include file

Cause: A VARCHAR declaration was found in a file included using a #include form.

Action: Use the EXEC SQL INCLUDE form to include files with VARCHAR declarations instead.

PCC-02396: Illegal use of arrays inside an array of structs

PCC-02396: Illegal use of arrays inside an array of structs

Cause: An array of a struct that contained arrays of scalars or two-dimensional char or VARCHAR fields was used as a host variable.

Action: Rewrite the struct so that there are no scalar arrays or two-dimensional char or VARCHAR fields.

PCC-02395: Using arrays of structs requires that the struct be named

PCC-02395: Using arrays of structs requires that the struct be named

Cause: An array of some unnamed struct was used as a host variable. When using arrays of structs, the struct requires a name or tag.

Action: Provide a name for the struct.

PCC-02394: Input file name and output filename are identical

PCC-02394: Input file name and output filename are identical

Cause: The values of INAME and ONAME are the same or the default output filename is the same as that specified by ONAME.

Action: Use ONAME to specify a different filename for the output file.

PCC-02393: SQL statement found inside an EXEC SQL DECLARE SECTION

PCC-02393: SQL statement found inside an EXEC SQL DECLARE SECTION

Cause: An executable SQL statement appears inside a DECLARE SECTION.

Action: Move the SQL statement into the body of a function.

PCC-02392: You are already in an EXEC SQL DECLARE SECTION

PCC-02392: You are already in an EXEC SQL DECLARE SECTION

Cause: A SQL DECLARE SECTION appears nested inside another one.

Action: Do not nest DECLARE SECTIONS. Remove any nested inner ones.

PCC-02391: Runtime context variable not of correct type

PCC-02391: Runtime context variable not of correct type

Cause: The host variable in a EXEC SQL CONTEXT USE statement or in the RETURNING clause of a REGISTER CONNECT statement was not declared to be of type SQL_CONTEXT.

Action: Declare the runtime context variable to be of type SQL_CONTEXT.

PCC-02390: No EXEC SQL CONTEXT USE statement encountered

PCC-02390: No EXEC SQL CONTEXT USE statement encountered

Cause: No EXEC SQL CONTEXT USE statement was encountered and the option threads=yes was requested.

Action: Ensure that the necessary context variable (of type sql_context) has been declared and that has been ALLOCATEd and USEd prior to any executable SQL statements.

PCC-02389: Arrays not allowed as input bind variables in SELECT list

PCC-02389: Arrays not allowed as input bind variables in SELECT list

Cause: A host array was used in the SELECT list of a SELECT-INTO statement.

Action: Rewrite the SELECT statement without using arrays in SELECT list.

PCC-02388: Arrays not allowed in FROM or WHERE clause of SELECT statement

PCC-02388: Arrays not allowed in FROM or WHERE clause of SELECT statement

Cause: A host array was used in the WHERE clause of a SELECT-INTO statement.

Action: Rewrite the SELECT statement without using arrays or use a cursor.

PCC-02387: Expecting an expression of type sql_cursor

PCC-02387: Expecting an expression of type sql_cursor

Cause: A host bind variable was used in an ALLOCATE, FETCH or CLOSE statement that was not declared as a result set SQL_CURSOR.

Action: Declare the variable to be of type sql_cursor.

PCC-02386: Use of the AT clause is not permitted here

PCC-02386: Use of the AT clause is not permitted here

Cause: An explicit AT clause was used with an ALLOCATE statement or a FETCH or CLOSE statement also using a SQL_CURSOR declaration.

Action: Remove the AT clause.

PCC-02385: CHAR_MAP disallowed when using NLS_CHAR and NLS_ LOCAL=TRUE

PCC-02385: CHAR_MAP disallowed when using NLS_CHAR and NLS_ LOCAL=TRUE

Cause: The CHAR_MAP option was specified while indicating which host variables are to be treated by the precompiler as NLS multi-byte character variables. This mapping cannot be performed with the option NLS_ LOCAL=TRUE. This error also occurs when DBMS=V6 is used in conjunction with NLS_CHAR and NLS_LOCAL=TRUE.

Action: Remove either the CHAR_MAP option or set NLS_LOCAL=FALSE. Ensure that DBMS is not set to V6.

PCC-02384: Missing array length specifier

PCC-02384: Missing array length specifier

Cause: An array declaration was given without an array length specifier.

Action: Provide the length for the array declaration.

PCC-02383: Expecting an expression of type OCIExtProcContext

PCC-02383: Expecting an expression of type OCIExtProcContext

Cause: The type of the bind variable given in a REGISTER CONNECT USING statement was not (pointer to) OCIExtProcContext.

Action: Declare a variable having type (pointer to) OCIExtProcContext and use it in the REGISTER CONNECT USING statement.

PCC-02382: You must specify MODE=ANSI when using NLS_LOCAL=YES

PCC-02382: You must specify MODE=ANSI when using NLS_LOCAL=YES

Cause: NLS_CHAR was used to specify NLS multi-byte character variables without specifying MODE=ANSI.

Action: Specify MODE=ANSI on the command line when using NLS_ LOCAL=TRUE.

PCC-02380: Cannot specify a connect mode when altering a user password

PCC-02380: Cannot specify a connect mode when altering a user password

Cause: An attempt was made to connect in either SYSOPER or SYSDBA mode while at the same time trying to change passwords using the ALTER AUTHORIZATION clause in the same CONNECT statement.

Action: Changing passwords while connecting in SYSOPER or SYSDBA mode is prohibited. Rewrite the connect statement by either removing the ALTER AUTHORIZATION cluase or the CONNECT MODE clause.

PCC-02379: Cannot equivalence National Language character variables

PCC-02379: Cannot equivalence National Language character variables

Cause: A National Language character variable (specified using the NLS_CHAR option) has undergone datatype equivalencing using either the EXEC SQL VAR or TYPE statements.

Action: Do not equivalence National Language character variables.

PCC-02378: Invalid type for National Language character variable

PCC-02378: Invalid type for National Language character variable

Cause: A variable declared as a National Language character using the NLS_ CHAR option was not declared as a char or implicit VARCHAR.

Action: Declare the variable as a char or implicit VARCHAR or do not specify using the NLS_CHAR option.

PCC-02377: Arrays of implicit varchars are not permitted

PCC-02377: Arrays of implicit varchars are not permitted

Cause: An array of implicit VARCHARS was declared when HOST_ VARCHAR=TRUE.

Action: Rewrite the implicit VARCHAR declaration without using arrays.

PCC-02376: You may not declare SQLCODE when DEF_SQLCODE = TRUE

PCC-02376: You may not declare SQLCODE when DEF_SQLCODE = TRUE

Cause: The DEF_SQLCODE option may not be specified if a SQLCODE declaration already explicitely appears in the program.

Action: Remove the SQLCODE declaration from the program or specify DEF_ SQLCODE=NO (the default).

PCC-02375: SQL statement found outside the body of a function

PCC-02375: SQL statement found outside the body of a function

Cause: A SQL statement other than a declarative, datatype equivalence or WHENEVER statement was found outside the body of a function when PARSE=FULL.

Action: Move the SQL statement inside the body of a function.

PCC-02374: SQLCHECK value exceeds command line value

PCC-02374: SQLCHECK value exceeds command line value

Cause: The value given to the SQLCHECK option in an EXEC ORACLE statement in a program was greater than the value given either on the command line or greater than the default value if no SQLCHECK option was given on the command line. The order of the option values is SEMANTICSlamp;gt;SYNTAXlamp;gt;NONE. When this warning message is issued, the original value of SQLCHECK (the default or the command-line value) stays in effect.

Action: Remove or recode the EXEC Oracle option(s) in the .pc source file to avoid this warning message.

PCC-02373: Invalid declaration in EXEC SQL DECLARE section

PCC-02373: Invalid declaration in EXEC SQL DECLARE section

Cause: An improper declaration was placed in a Declare Section. This message is usually caused by including an EXEC SQL TYPE or EXEC SQL VAR declaration in a Declare Section.

Action: Move the declaration outside of the SQL DECLARE section.

PCC-02372: FOR clause not allowed in SELECT statement

PCC-02372: FOR clause not allowed in SELECT statement

Cause: A SQL statement containing a SELECT command cannot contain a FOR clause. The meaning of such a statement would be unclear.

Action: Rephrase the SELECT statement, removing the FOR clause.

PCC-02371: Illegal FOR clause

PCC-02371: Illegal FOR clause

Cause: The argument of a FOR clause must be specified as an integer or as an identifier containing an integer.

Action: Rewrite the FOR clause.

PCC-02370: An EXEC TOOLS MESSAGE host variable is not type char

PCC-02370: An EXEC TOOLS MESSAGE host variable is not type char

Cause: f a host variable is used to define a context name in an EXEC TOOLS GET CONTEXT or EXEC TOOLS SET CONTEXT statement, that host variable must be of a character type.

Action: Declare the message to a host variable of a char type.

PCC-02369: An EXEC TOOLS host pointer variable is not a pointer

PCC-02369: An EXEC TOOLS host pointer variable is not a pointer

Cause: The host variable specifying an EXEC TOOLS context must be a pointer type.

Action: Redeclare the variable, making sure that it is a pointer.

PCC-02368: An EXEC TOOLS host variable context name is not type char

PCC-02368: An EXEC TOOLS host variable context name is not type char

Cause: If a host variable is used to define a context name in an EXEC TOOLS GET CONTEXT or EXEC TOOLS SET CONTEXT statement, that host variable must be of a character type.

Action: Redeclare the context name to a host variable of a char type.

PCC-02367: This indicator variable must be declared as type short

PCC-02367: This indicator variable must be declared as type short

Cause: An indicator for a host variable of this type must have the C type short. An array of such indicators must be an array of shorts.

Action: Declare the indicator variable or indicator array as type short.

PCC-02366: Command line argument MODE=ANSI may not be used with DBMS=V6

PCC-02366: Command line argument MODE=ANSI may not be used with DBMS=V6

Cause: The semantics of certain operations (such as character comparison) in Oracle version ^ are not 100% compliant with the ANSI or ISO SQL standards. When V6 semantics are requested, using the DBMS=V6 or DBMS=V6_CHAR option, precompilation with MODE=ANSI is not permitted.

Action: Do not use ANSI mode with V6 options.

PCC-02365: Indicator array size cannot be smaller than host array size

PCC-02365: Indicator array size cannot be smaller than host array size

Cause: An indicator array must have dimension greater than or equal to the corresponding host variable array dimension.

Action: Change the dimension of the indicator array.

PCC-02364: Host struct and its indicator must have the same number of fields

PCC-02364: Host struct and its indicator must have the same number of fields

Cause: When a structure containing indicator variables is declared and associated with a host structure, the indicator structure must contain the same number of fields as the host structure. This is so even when some of the indicators will not be used or even when it would not make sense to do so (for fields constrained as NON NULL, for example).

Action: Redeclare the indicator variable with the correct number of fields.

PCC-02363: Indicator variable must be a structure

PCC-02363: Indicator variable must be a structure

Cause: If a host variable is a structure, the associated indicator variable must also be a structure.

Action: Recode the application to create an indicator variable as a structure.

PCC-02362: Host variable not declared within SQL DECLARE section

PCC-02362: Host variable not declared within SQL DECLARE section

Cause: When MODE=ANSI is specified at precompile time, all host variables must be declared inside Declare Sections. Remember that MODE=ANSI refers to ANSI SQL, not ANSI C.

Action: Add the EXEC SQL BEGIN DECLARE SECTION... EXEC SQL END DECLARE SECTION statements around all host variable declarations.

PCC-02361: Use of ARRAYLEN with SQL bind arrays is ignored

PCC-02361: Use of ARRAYLEN with SQL bind arrays is ignored

Cause: ARRAYLEN is only valid with arrays that can be bound in PL or SQL blocks.

Action: Use an appropriate array type.

PCC-02360: This array type is invalid for use with ARRAYLEN statement

PCC-02360: This array type is invalid for use with ARRAYLEN statement

Cause: Arrays of some host variables types are not allowed and hence also cannot be used in ARRAYLEN statements. VARCHAR and DATE are examples.

Action: Specify an array with a datatype that can be used in host arrays.

PCC-02359: Identifier specifying ARRAYLEN must be a 4-byte integer

PCC-02359: Identifier specifying ARRAYLEN must be a 4-byte integer

Cause: The expression that specifies the ARRAYLEN dimension must evaluate to an integer. For example, the statement EXEC SQL ARRAYLEN my_array(1,3) cannot be parsed.

Action: Correct the statement, using an integral dimesnsion.

PCC-02358: Identifier following ARRAYLEN must be the name of an array

PCC-02358: Identifier following ARRAYLEN must be the name of an array

Cause: A declared array must be specified as the argument for an ARRAYLEN statement. Declare the array textually before the ARRAYLEN statement. See the Programmer s Guide to the Oracle Precompilers for the syntax of the ARRAYLEN statement.

Action: Correct the statement, specifying a host array as the argument.

PCC-02357: Function calls may not be used as host variable expressions

PCC-02357: Function calls may not be used as host variable expressions

Cause: Only objects that are lvalues (that resolve to an address) can be host variables. Because a function call is not an lvalue, one cannot be used in place of a host variable.

Action: Recode the application.

PCC-02356: Warning at line number, column number, file string:

PCC-02356: Warning at line number, column number, file string:

Cause: This is a generic warning message. It precedes a more specific warning.

Action: No action required. Correct the error(s) indicated in the following message(s).

PCC-02355: Invalid or obsolete option, ignored

PCC-02355: Invalid or obsolete option, ignored

Cause: A command-line option that is not used in Pro*C Release 2.0 was specified. For example, the option AREASIZE is no longer valid with precompilers used with the Oracle7 Server.

Action: No action required. This is an informational message.

PCC-02354: A file included with #include may not contain SQL statements

PCC-02354: A file included with #include may not contain SQL statements

Cause: The Pro*C Precompiler reads header files referenced in #INCLUDE directives and uses the values defined in them. But the precompiler never generates code using statements in header files, so use of SQL statements in these files is illegal.

Action: Move the SQL statement(s) into the main body of the application or use EXEC SQL INCLUDE to check that the included file is precompiled.

PCC-02353: Semantic error at line number, column number, file string:

PCC-02353: Semantic error at line number, column number, file string:

Cause: This error message precedes a more specific error message.

Action: No action required. Correct the error(s) reported in the following message(s).

PCC-02352: out of bounds bind position from PL or SQL

PCC-02352: out of bounds bind position from PL or SQL

Cause: PL or SQL requested a bind position that does not exist.

Action: Contact ORACLE customer support.

PCC-02351: illegal datatype equivalencing operation

PCC-02351: illegal datatype equivalencing operation

Cause: The datatype specified could not be equivalenced, or the syntax was incorrect in the VAR or TYPE statement.

Action: See the Programmer s Guide to the Oracle Precompilers for a list of the datatypes that can be equivalenced and the correct syntax of the VAR or TYPE statement.

PCC-02350: cannot equivalence this SQL type

PCC-02350: cannot equivalence this SQL type

Cause: Datatype or variable equivalencing to the datatypes NUMBER or DECIMAL cannot be used. See the Datatype Equivalencing section in the Programmer s Guide to the Oracle Precompilers for more information.

Action: Use the appropriate datatype for the application.

PCC-02349: precision must be specified for this type

PCC-02349: precision must be specified for this type

Cause: In a VAR or TYPE statement, certain Oracle types require that the precision be specified. For example, VARCHAR2 or CHAR.

Action: Indicate the precision.

PCC-02348: indicators are not allowed in EXEC IAF statements

PCC-02348: indicators are not allowed in EXEC IAF statements

Cause: Indicator variables associated with host variables cannot be used in EXECIAF statements such as GET and PUT in a user exit.

Action: Eliminate the indicator variabls. If feasible (for example with Forms V4), use EXEC TOOLS statements, which do allow indicator variables. See the Programmer s Guide to the Oracle Precompilers for more information of EXECIAF and EXEC TOOLS statements.

PCC-02347: PL or SQL found syntax errors

PCC-02347: PL or SQL found syntax errors

Cause: A PL or SQL statement was used illegally.

Action: Check the PL or SQL User s Guide and Reference for the correct syntax.

PCC-02345: SQLCHECK=SEMANTICS must be given when embedded PL or SQL blocks are used

PCC-02345: SQLCHECK=SEMANTICS must be given when embedded PL or SQL blocks are used

Cause: Embedded PL or SQL blocks require that the command-line flag SQLCHECK=SEMANTICS is used.

Action: Use the SQLCHECK=SEMANTICS option. This also requires that the USERID connect option be given.

PCC-02344: Host variable array size mismatch. Using minimum: number

PCC-02344: Host variable array size mismatch. Using minimum: number

Cause: Host variable arrays in a single statement should all be of equal size.

Action: Redefine the bind variable array lengths to all be the same size.

PCC-02343: body of cursor must be a query expression

PCC-02343: body of cursor must be a query expression

Cause: A cursor definition must be a SELECT statement.

Action: Rewrite the cursor definition.

PCC-02342: using WHERE CURRENT OF on cursor defined without FOR UPDATE clause

PCC-02342: using WHERE CURRENT OF on cursor defined without FOR UPDATE clause

Cause: When MODE=Oracle, a cursor defined with a WHERE CURRENT OF clause must also have a FOR UPDATE clause.

Action: Rewrite the cursor definition.

PCC-02341: host variable has illegal type

PCC-02341: host variable has illegal type

Cause: A host variable has an unpermitted type (i.e.; enum, void, etc).

Action: Rewrite the host variable declaration, using a permissible host variable type.

PCC-02340: structure contains a bit field

PCC-02340: structure contains a bit field

Cause: Bit fields are not allowed in host variables because they are meaningless for database DML operations.

Action: This error message is followed by another message that gives the line and column of the reference to the offending host variable. Recode the application.

PCC-02339: host variables cannot be of union types

PCC-02339: host variables cannot be of union types

Cause: A C union as a host variable cannot be used.

Action: This error message is followed by another message that gives the line and column of the reference to the illegal union. Recode, using a struct or individual scalar host variables.

PCC-02338: structure contains a nested struct or union

PCC-02338: structure contains a nested struct or union

Cause: A structure used as a host variable may not have structures or unions nested within it.

Action: Rewrite the variable declaration.

PCC-02337: cannot declare multi-dimensioned array for this type

PCC-02337: cannot declare multi-dimensioned array for this type

Cause: Host variable arrays of scalars with more than 1 dimension cannot be declared.The only host variables allowed to be multi-dimensioned are CHAR and VARCHAR.

Action: Rewrite the variable declaration.

PCC-02336: host variable expression has invalid type

PCC-02336: host variable expression has invalid type

Cause: The host variable was declared using a C type that is not permitted as a host variable. See the Programmer s Guide to the Oracle Precompilers for a list of the permissible C types for host variables.

Action: Use a permissible host variable type.

PCC-02335: body of cursor must name statement identifier

PCC-02335: body of cursor must name statement identifier

Cause: In a Dynamic SQL Method 4 application, the DECLARE... CURSOR statement must name a statement identifier that has been PREPAREd in a preceding statement. The PREPARE statement must physically (not logically) precede the DECLARE command.

Action: This error message is followed by another message that gives the line and column of the reference to the statement. Recode the application.

PCC-02334: SQL identifier was not declared as a cursor

PCC-02334: SQL identifier was not declared as a cursor

Cause: A cursor name was used in an OPEN, FETCH, or CLOSE statement that had not been DECLAREd.

Action: Check that all SQL cursor names have been declared. Remember that cursors are identifiers, not variables, and that they are local to the precompilation unit.

PCC-02333: SQL identifier was not declared as a statement

PCC-02333: SQL identifier was not declared as a statement

Cause: A SQL statement identifier was referenced in a DECLARE... CURSOR statement that was not PREPAREd.

Action: Check that all SQL statement names have been declared. Remember that SQL statement names are identifiers, not variables, and that they are local to the precompilation unit.

PCC-02332: attempted to redefine SQL identifier

PCC-02332: attempted to redefine SQL identifier

Cause: A SQL identifier (such as a cursor name) can be defined only once.

Action: Do not redefine the SQL identifier.Use a different name.

PCC-02331: undefined SQL identifier

PCC-02331: undefined SQL identifier

Cause: All SQL identifiers must be declared before they are used. This message can result when a CURSOR or STATEMENT is not declared (defined) before being referenced.

Action: Define the SQL identifier before it is used.

PCC-02330: expecting an expression of integer type

PCC-02330: expecting an expression of integer type

Cause: The expression does not evaluate to an integer. For example, a SQL FOR expression must evaluate to an integral type.

Action: Rewrite the expression.

PCC-02329: found reference to undeclared function

PCC-02329: found reference to undeclared function

Cause: A function was referenced that was not declared. All function references must be declared.

Action: Declare the function.

PCC-02328: undefined struct member

PCC-02328: undefined struct member

Cause: A structure component was referenced that was not declared as part of the structure.

Action: Redefine the structure member.

PCC-02327: struct or struct pointer required

PCC-02327: struct or struct pointer required

Cause: A scalar host variable was used in a context where a structure (or its pointer) is required.

Action: Make the host variable a structure or add more scalar host variables to satisfy the SQL syntax requirements.

PCC-02326: illegal structure reference operation

PCC-02326: illegal structure reference operation

Cause: A structure component using invalid syntax was referenced. For example, a -lamp;gt; operator was used instead of a required `. operator.

Action: Correct the invalid reference.

PCC-02325: illegal indirection operation

PCC-02325: illegal indirection operation

Cause: An attempt was made to use a non-pointer type as a pointer.

Action: Rewrite the expression.

PCC-02324: found variable name used as a typedef name

PCC-02324: found variable name used as a typedef name

Cause: The name of a variable was found where a typedef was expected.

Action: Rewrite the expression and specify the correct typedef reference.

PCC-02323: found typedef name used in an expression (expecting a value)

PCC-02323: found typedef name used in an expression (expecting a value)

Cause: The name of a typedef was found where a variable was expected.

Action: Rewrite the expression and remove the reference to the typedef.

PCC-02322: found undefined identifier

PCC-02322: found undefined identifier

Cause: An identifier used in a SQL statement was not defined. For example, a cursor name was referenced that had not been declared, or in a DECLARE CURSOR statement, a statement name was used that had not been PREPAREd.

Action: Provide a declaration for the variable and or or its type identifier.

PCC-02321: only subtraction between two pointers is permitted

PCC-02321: only subtraction between two pointers is permitted

Cause: Pointer values cannot be added, multiplied, or divided. The only arithmetic operation permitted with pointers is subtraction.

Action: Recode to avoid this error message.

PCC-02320: arithmetic expression does not have correct operand types

PCC-02320: arithmetic expression does not have correct operand types

Cause: The arithmetic expression must be specified with integral types.

Action: Rewrite the expression using integral types.

PCC-02319: expression type does not match usage

PCC-02319: expression type does not match usage

Cause: The type of a variable does not match is usage. For example, in dynamic SQL, a host variable containing the text of a SQL statement must be declared as a C character type or be equivalenced to the SQL type STRING.

Action: Remove the declaration.

PCC-02318: missing type expression

PCC-02318: missing type expression

Cause: The specified expression is missing the declaration of a type.

Action: Specify a type for the expression.

PCC-02317: illegal cast type expression

PCC-02317: illegal cast type expression

Cause: An illegal cast is present in the expression.

Action: Remove the illegal cast.

PCC-02316: illegal operator in constant expression

PCC-02316: illegal operator in constant expression

Cause: A non-arithmetic operator was present in a constant expression.

Action: Rewrite the expression to eliminate the non-arithmetic operator.

PCC-02315: cannot evaluate expression as constant

PCC-02315: cannot evaluate expression as constant

Cause: The specified expression does not evaluate to a constant. Such expressions are required, for example, as the length of a VARCHAR.

Action: Replace the expression with one that does evaluate to a constant integer.

PCC-02314: cannot evaluate constant sizeof expression

PCC-02314: cannot evaluate constant sizeof expression

Cause: A SIZEOF operator was used where a precompiler expression was expected. For example, as the length of a varchar.

Action: Eliminate the SIZEOF operator in this instance.

PCC-02313: malformed VARCHAR declaration - missing length

PCC-02313: malformed VARCHAR declaration - missing length

Cause: When a VARCHAR is declared, a length specification is mandatory. For example, the following VARCHAR declaration is meaningless, hence illegal: VARCHAR v1((;

Action: Specify the length for each declared VARCHAR.

PCC-02312: arrays of VARCHAR greater than 2 dimensions not allowed

PCC-02312: arrays of VARCHAR greater than 2 dimensions not allowed

Cause: A VARCHAR variable having more that 2 dimensions was declared. Multidimensional arrays are not supported as host variables.

Action: Recode the application to remove multidimensional array usage.

PCC-02311: cannot have VARCHAR bit fields

PCC-02311: cannot have VARCHAR bit fields

Cause: Host variables cannot contain bit fields.

Action: Recode the application to remove the bit fields.

PCC-02310: formal parameter VARCHARs should be declared as pointers

PCC-02310: formal parameter VARCHARs should be declared as pointers

Cause: Many C compilers allow structures to be passed to and returned from functions. Although a VARCHAR is implemented as a C struct, VARCHARs must be passed to a function as pointers.

Action: Take the address of a VARCHAR when it is passed to a function. See the example in the section Referencing VARCHAR Variables in the Programmer s Guide to the Oracle Precompilers.

PCC-02309: illegal formal parameter declaration

PCC-02309: illegal formal parameter declaration

Cause: A formal parameter to a function was specified without giving its type.

Action: Rewrite the function declaration and include types of all parameters in function declarations.

PCC-02308: identifier required in this function declaration

PCC-02308: identifier required in this function declaration

Cause: A function definition written in ANSI C must have both the name and the type for all parameters.

Action: Rewrite the function definition so that it contains the name of each parameter.

PCC-02307: void can only be used when single parameter

PCC-02307: void can only be used when single parameter

Cause: A function can be declared or defined using the following syntax: int func1(void) to indicate that the function has no parameters. void can be used only once in this case.

Action: Remove the extra voids in the function definition or declaration.

PCC-02306: illegal name of C function

PCC-02306: illegal name of C function

Cause: A C function was declared with a name that is not a legal C identifier.

Action: Use legal C identifiers for all function names.

PCC-02305: illegal mixing of new and old style C function declarations

PCC-02305: illegal mixing of new and old style C function declarations

Cause: All C functions using either the traditional style (K R style) function declarations or the new (ANSI) style must be declared; the two styles cannot be mixed.

Action: Adopt a consist declaration style for functions.

PCC-02304: invalid declaration of C function

PCC-02304: invalid declaration of C function

Cause: A C function using invalid syntax was declared.

Action: Consult a C programming manual and correct the declaration.

PCC-02302: cannot open code generation output file string

PCC-02302: cannot open code generation output file string

Cause: Pro*C was unable to open one or both temporary files required for code generation. The user executing the precompiler must have write permission (and or or the appropriate privileges) on the current directory.

Action: Check that permission exists to create files in the the directory where you precompile.

PCC-02301: cannot reopen input file for reading

PCC-02301: cannot reopen input file for reading

Cause: The semantic analysis phase of the precompiler could not reopen the input file to generate the output code.

Action: Check that the input file and it s directory protection and priveleges do not change during precompilation.

PCC-02210: C++ punctuation sequences are not permitted

PCC-02210: C++ punctuation sequences are not permitted

Cause: C++ punctuation sequences are not supported by the ProC or C++ precompiler.

Action: Rewrite your C++ code without using punctuation sequences and precompile it again.

PCC-02209: Macro invocation has incorrect number of arguments

PCC-02209: Macro invocation has incorrect number of arguments

Cause: A macro invocation in the source does not have the same number of arguments as the macro definition in the #define line.

Action: Correct the macro reference or the macro definition.

PCC-02208: No filename specified in #include statement

PCC-02208: No filename specified in #include statement

Cause: The precompiler parser encountered a #include directive that had no filename associated with it. For example, #include

Action: Specify appropriate filename with the #include directive, or correct the syntax.

PCC-02207: Invalid macro name

PCC-02207: Invalid macro name

Cause: The precompiler parser encountered a #define directive that had no macro name associated with it. For example, #define

Action: Correct the syntax.

PCC-02206: Host variables are not permitted within a DDL statement

PCC-02206: Host variables are not permitted within a DDL statement

Cause: A Data Definition Language statement cannot use host variables. For example, the statement CREATE TABLE :table_name (c1 char(10)); is illegal, because the name of the table in a CREATE TABLE statement cannot be represented using host variable.

Action: Use dynamic SQL to create the names of database objects (tables, views, columns, etc.) at runtime. See the Programmer s Guide to the Oracle Precompilers, Release2.2 for information about dynamic SQL.

PCC-02205: Parser error at line number, column number, file string:

PCC-02205: Parser error at line number, column number, file string:

Cause: The precompiler parser encountered a syntax error, either in C code or in SQL code. A more specific message should follow.

Action: for any following messages.

PCC-02204: EXEC SQL INCLUDE not permitted from within an included file

PCC-02204: EXEC SQL INCLUDE not permitted from within an included file

Cause: EXEC SQL INCLUDE statements cannot be nested. Also, EXEC SQL INCLUDE statement cannot be put inside a file that is included using the #include preprocessor command.

Action: Recode the program so that the nested include statement is not required.