03100-03199: Two-Task Interface

This sections lists messages generated when the two-task interface to Oracle is used.

Cause:	An attempt to allocate stack space for communication purposes failed. This is an internal error message not usually issued.

Action:	Contact customer support.

ORA-03106 fatal two-task communication protocol error

Cause:	The communication path between Oracle and the user task has stopped. This is an internal error message not usually issued.

Action:	Contact customer support.

ORA-03107 oranet buffer underflow

Cause:	This is an internal error message not usually issued.

Action:	Contact customer support.

ORA-03108 oranet: Oracle does not support this interface version

Cause:	The version of Oracle connected to via SQL*Net does not support this version of the SQL*Net protocol.

Action:	Upgrade the older version of Oracle and try again.

ORA-03109 oranet buffer overflow

Cause:	Data being transferred between the user program and Oracle overflowed the buffer space available. This is an internal error message not usually issued.

Action:	Contact customer support.

ORA-03110 oranet: Oracle does not support this SQL version

Cause:	The version of Oracle connected to via SQL*Net does not support the version of the SQL*Net protocol.

Action:	Upgrade the older version of Oracle and try again.

ORA-03111 break received on communication channel

Cause:	A break was processed on the communications channel, but was not properly handled by SQL*Net software. This is an internal error message not usually issued.

Action:	Contact customer support.

ORA-03112 a server linked as single-task cannot use SQL*Net

Cause:	A statement containing a SQL*Net connect string was issued to the single-task server. For example, a database link was used in a SQL statement.

Action:	Do not use SQL*Net connect strings in a single-task environment.

For more information about SQL*Net connect strings, see the index entries on "SQL*Net connect strings" and on "SQL*Net" in Oracle7 Server Distributed Systems, Volume I.

Cause:	An unexpected end-of-file was processed on the communication channel. The problem could not be handled by the SQL*Net, two task, software. This message could occur if the shadow two-task process associated with a SQL*Net connect has terminated abnormally, or if there is a physical failure of the interprocess communication vehicle, that is, the network or server machine went down.

Action:

If this message occurs during a connection attempt, check the setup files for the appropriate SQL*Net driver and confirm SQL*Net software is correctly installed on the server. If the message occurs after a connection is well established, and the error is not due to a physical failure, check if a trace file was generated on the server at failure time. Existence of a trace file may suggest an Oracle internal error that requires the assistance of customer support.

ORA-03114 not connected to Oracle

Cause:	A call to Oracle was attempted when no connection was established. Usually this happens because a user-written program has not logged on. It may also happen if communication trouble causes a disconnection.

Action:	Try again. If the message recurs and the program is user-written, check the program.

ORA-03115 unsupported network datatype or representation

Cause:	A user bind or define, or an Oracle function, is not supported by this heterogeneous SQL*Net connection.

Action:	Upgrade the older version of Oracle and try again.

ORA-03116 invalid buffer length passed to a conversion routine

Cause:	This is an internal error message not usually issued.

Action:	Contact customer support.

ORA-03117 two-task save area overflow

Cause:	This is an internal error message not usually issued.

Action:	Contact customer support.

ORA-03118 two-task coroutine has invalid state

Cause:	This is an internal error message not usually issued.

Action:	Contact customer support.

ORA-03120 two-task conversion routine: integer overflow

Cause:	An integer value in an internal Oracle structure overflowed when being sent or received over a heterogeneous connection. This can happen when an invalid buffer length or too great a row count is specified. It usually indicates a bug in the user application.

Action:	Check parameters to Oracle calls. If the problem recurs, reduce all integer parameters, column values not included, to less than 32767.

ORA-03121 no interface driver connected - function not performed

Cause:	This message occurs usually because the SQL*Net driver is not loaded into memory or there is a mismatch of the version of the driver. A user program linked with an obsolete library may also cause this message. Only programs provided by Oracle Corporation should use this interface.

Action:	If the message occurred during use of a program provided by Oracle Corporation, contact customer support. If a user program caused the message, relink the program with current versions of the Oracle libraries.

ORA-03122 attempt to close Oracle-side window on user side

Cause:	This is an internal error message not usually issued.

Action:	Contact customer support.

ORA-03123 operation would block

Cause:	The attempted operation cannot complete now.

Action:	Retry the operation later.

ORA-03124 two-task internal error

Cause:	Internal error.

Action:	Contact customer support.

ORA-03125 client-server protocol violation

Cause:	The application received a bad escape sequence from the server which may indicate a problem with the client application user code.

Action:	Contact your customer support representative.

ORA-03126 network drive does not support non-blocking operations

Cause:	A non-block operation was attempted and the network driver does not support non-block operations.

Action:	Use the default blocking operations or use a driver supporting non-blocking operations.

ORA-03127 no new operations allowed until the active operation ends

Cause:	An attempt was made to execute a new operation before the active, non-blocking operation completed or a new operation was attempted before all the pieces of a column were inserted or fetched.

Action:	Execute the new operation after the non-blocking operation completes. If piecewise binds/defines were done, execute the new operation after all the pieces have been inserted or fetched.

For more information about inserting and fetching and the non-blocking mode, see the index entries on "non-blocking mode" and on "developing an OCI program" in the Programmer's Guide to the Oracle Call Interface.

Cause:	The OCI test for non-blocking mode on a connection indicates that the connection is in blocking mode.

Action:	If non-blocking mode is required, use appropriate OCI calls to change the mode.

ORA-03129 the next piece to be inserted is required

Cause:	The application performed a piecewise bind on a column.

Action:	Provide the next piece of this bind variable.

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

Cause:	The application performed a piecewise define on the column.

Action:	Provide the next buffer for the next piece to be retrieved.

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

Cause:	The application either provided the length of the buffer for the next piece to be zero or provided a null pointer.

Action:	Verify if the buffer pointer for the next piece is null or if the length is zero.

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