24300-24999: UPI/OCI Messages

Cause:	An undefined mode value was specified.

Action:	Check that the correct mode is selected and that an allowed value for that mode is specified.

For more information about mode values, see the index entries on "mode, of a parameter in C," "mode, of a parameter in COBOL," "mode, of a parameter in FORTRAN" in the Programmer's Guide to the Oracle Call Interface.

Cause:	An HDA was not specified in the logon call while running in a thread safe environment.

Action:	Make sure that HDA is not NULL when calling the logon routine.

For more information about host data areas(HDA) and defining the OCI data structures, see the index entries on "host data area" and on "data structures, defining" in the Programmer's Guide to the Oracle Call Interface.

Cause:	An attempt was made to use the host connection while it was in use by another thread.

Action:	Wait for another thread to finish before using this connection.

For more information about connecting to the Oracle Server, see the index entry on "connections, multiple" in the Programmer's Guide to the Oracle Call Interface.

Cause:	One of the calls that was supported in deferred mode linkage exclusively was invoked when the client was linked non-deferred.

Action:	Use this call in deferred mode of linkage.

For more information about deferred mode linking, see the index entry on "deferred, mode linking" in the Programmer's Guide to the Oracle Call Interface.

Cause:	Data of this datatype cannot be sent or fetched in pieces.

Action:	Use other bind or define calls for this datatype.

For more information about bind and define calls, see the index entry on "developing an OCI program" in the Programmer's Guide to the Oracle Call Interface.

Cause:	The call was executed on a cursor for which this was invalid.

Action:	Verify that this call is valid for this cursor. For example, GET PIECE INFORMATION and SET PIECE INFORMATION are valid on a cursor if appropriate binds and defines have been done on this cursor.

For more information about bind and define calls, see the index entries on "bind operation" and on "define operation" in the Programmer's Guide to the Oracle Call Interface.

Cause:	A zero length buffer or a null buffer pointer was provided.

Action:	Verify that the buffer pointing to this piece or its length is non-zero. The buffer pointer for the next piece or its length can be zero if it is the last piece to be inserted and there are no more data for the column.

For more information about fetching operations, see the index entry on "rows, fetching" in the Programmer's Guide to the Oracle Call Interface.

Cause:	The length of the piece exceeds the maximum possible size of the data.

Action:	Verify that the length of this piece and the cumulative length of all the previous pieces are not more than the PROGVL parameter specified in the obindps call.

For more information about fetching operations, see the index entry on "rows, fetching" in the Programmer's Guide to the Oracle Call Interface.