Oracle 12c R2 Error Codes and Solution Suggestions from ORA-03000 to ORA-03200
- ORA-03001: unimplemented feature
Cause: This feature is not implemented.
Action: None
Cause: This is an internal error.
Action: Contact your customer support representative.
Cause: User attempted to use a feature which is no longer supported.
Action: None
Cause: An incompatible OCI function call was issued for new functionality.
Action: Do not use V7 OCI calls for this functionality.
- ORA-03100: communication area cannot be allocated; insufficient memory
- ORA-03101: invalid input data for string
Cause: Invalid input data was detected for the specified data type.
Action: Pass a valid value for the specified data type.
Cause: A malformed TTC (Two-Task Common) packet was received.
Action: Contact Oracle Support Services.
- ORA-03105: internal protocol error
- ORA-03106: fatal two-task communication protocol error
- ORA-03107: oranet buffer underflow
- ORA-03108: oranet: ORACLE does not support this interface version
- ORA-03109: oranet buffer overflow
- ORA-03110: oranet: ORACLE does not support this SQL version
- ORA-03111: break received on communication channel
- 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.
Cause: The connection between Client and Server process was broken.
Action: There was a communication error that requires further investigation. First, check for network problems and review the SQL*Net setup. Also, look in the alert.log file for any errors. Finally, test to see whether the server process is dead and whether a trace file was generated at failure time.
- ORA-03114: not connected to ORACLE
- ORA-03115: unsupported network datatype or representation
- ORA-03116: invalid buffer length passed to a conversion routine
- ORA-03117: two-task save area overflow
- ORA-03118: two-task coroutine has invalid state
- ORA-03119: two-task detected inconsistent datatype specification
Cause: There was both a datatype, and an anonymous datatype declaration found.
Action: Correct the specification.
- ORA-03120: two-task conversion routine: integer overflow
- ORA-03121: no interface driver connected – function not performed
- ORA-03122: attempt to close ORACLE-side window on user side
Cause: This is an internal error.
Action: Contact your customer support representative.
Cause: This is a status code that indicates that the operation cannot complete now.
Action: None; this is not an error. The operation should be retried again for completion.
Cause: Internal error.
Action: Contact your customer support representative.
Cause: The application received a bad escape sequence from the server and may indicate a problem with the client application user code.
Action: Contact your customer support representative.
Cause: A non-blocking operation was attempted and the network driver does not support non-blocking operations.
Action: Use default blocking operations or use a driver supporting non-blocking operations.
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.
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.
Cause: The application performed a piecewise bind on a column.
Action: Provide the next piece of this bind variable.
Cause: The application performed a piecewise define on the column.
Action: Provide the next buffer for the next piece to be retrieved.
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.
Cause: The default value specified for a record field was too large.
Action: Change the default value to fit the field size.
Cause: An attempt was made to connect to an Oracle server of older version.
Action: Please refer to documentation for more details.
Cause: 1) Server unexpectedly terminated or was forced to terminate. 2) Server timed out the connection.
Action: 1) Check if the server session was terminated. 2) Check if the timeout parameters are set properly in sqlnet.ora.
Cause: Inbound connection was timed out by the server because user authentication was not completed within the given time specified by SQLNET.INBOUND_CONNECT_TIMEOUT or its default value
Action: 1) Check SQL*NET and RDBMS log for trace of suspicious connections. 2) Configure SQL*NET with a proper inbound connect timeout value if necessary.
- ORA-03137: malformed TTC packet from client rejected: [string] [string] [string] [string] [string] [string] [string] [string]
Cause: A malformed TTC (Two-Task Common) packet was received from the client.
Action: Contact Oracle Support Services.
Cause: Connection was terminated due to a security policy violation.
Action: Contact the Database Administrator
Cause: The SEC_DISABLE_OLDER_ORACLE_RPCS initialization parameter was enabled.
Action: Contact the Database Administrator
Cause: The current I/O operation was not complete. The error is typically returned from vectored and/or asynchronous I/O calls.
Action: Perform the necessary operation to complete or abort the current I/O.
Cause: The I/O request queue was full and no more requests could be queued.
Action: Perform the proper operations to complete part or all of the current in-progress I/O requests.
Cause: Connection was lost for the specified session and serial number. This is either due to session being killed or network problems.
Action: Reconnect and if error persists, contact Oracle Support Services.
Cause: Connection was lost for the specified process ID and thread ID. This is either due to session being killed or network problems.
Action: Reconnect and if error persists, contact Oracle Support Services.
Cause: Connection was lost for the specified process ID. This is either due to session being killed or network problems.
Action: Reconnect and if error persists, contact Oracle Support Services.
Cause: Attempted to PUT data when GET streaming was in progress or attempted to GET data when PUT streaming was in progress.
Action: Complete current stream read or write I/O before attempting I/O in reverse direction.
Cause: A malformed TTC (Two-Task Common) packet was received.
Action: Contact Oracle Support Services.
Cause: A malformed TTC (Two-Task Common) packet was received.
Action: Contact Oracle Support Services.
- ORA-03148: OCI_ATTR_ROW_COUNT cannot return a row count exceeding UB4MAXVAL. The actual row count is [string]
Cause: The row count was larger than UB4MAXVAL. OCI clients using OCI_ATTR_ROW_COUNT cannot see row counts larger than UB4MAXVAL.
Action: Upgrade Oracle client to version 12 client libraries or higher and use OCI_ATTR_UB8_ROW_COUNT instead.
Cause: An invalid Oracle error code was received by the server.
Action: Contact Oracle Support Services.
Cause: The connection between the client and the remote server process was broken.
Action: Look in the alert.log file of the remote server for any errors. Also, check to see whether the remote server process is dead and whether a trace file was generated at failure time.
Cause: The schema name length was larger than UB1MAXVAL, and clients older than Release 12.2 were unable to process longer names.
Action: Upgrade the client to Release 12.2 or higher.
Cause: The object name length was larger than UB1MAXVAL, and clients older than Release 12.2 wree unable to process longer names.
Action: Upgrade the client to Release 12.2 or higher.
Cause: The column name length was larger than UB1MAXVAL, and clients older than Release 12.2 were unable to process longer names.
Action: Upgrade the client to Release 12.2 or higher.
Cause: A Deprecated Two-Task Common (TTC) remote procedural call (RPC) was invoked.
Action: Check the ‘allow_deprecated_rpcs’ parameter setting and set it to the desired configuration.
Cause: Statement execution could not proceed because the rewritten statement that was issued to the remote had a different ordering (or number) of bind variables as compared to the original statement issued locally.
Action: Rewrite the statement issued locally to more closely match the rewritten statement issued to the remote (especially in terms of order and number of bind variables). Contact Oracle Support Services for further assistance.
Cause: You are using an Oracle client application linked with libraries with lower version than the current server version.
Action: Upgrade client libraries to be same as or higher than the server version.
Cause: A new undo segment was added. A query can occasionally deadlock when issued around the time an undo segment is added and used immediately on the primary.
Action: Retry the query. Avoid creating new undo segments when using standby as a regular part of operation.
Cause: Recovery was terminated. A query can ocassionally deadlock when recovery is terminated because it needs a block with changes that are made after the point at which recovery was terminated.
Action: Retry the query. Avoid cancelling recovery on standby.
Cause: Standby recovery fell behind the STANDBY_MAX_DATA_DELAY requirement.
Action: Tune recovery and retry the query later, or switch to another standby database within the data delay requirement.
Cause: ALTER SESSION SYNC WITH PRIMARY did not work because either the standby was not synchronous or in a data-loss mode with regard to the primary, or the standby recovery was terminated.
Action: Make the standby synchronous and no-data-loss with regard to the primary. Make the standby recovery active.
Cause: ALTER SESSION SET STANDBY_MAX_DATA_DELAY did not work for SYS users.
Action: Issue ALTER SESSION SET STANDBY_MAX_DATA_DELAY for non-SYS users.
Cause: The value of the %s parameter was not the same in all instances.
Action: Check %s in all instances.
Cause: The database was not an open physical standby database.
Action: Issue the command on an open physical standby database.
Cause: Duplicate SESSION or GLOBAL specifications were specified.
Action: Remove the duplicate specification.
Cause: NOCACHE or ORDER sequences were not supported for Active Data Guard standby.
Action: Alter the sequence properties.
Cause: Connection to the corresponding primary database failed. The primary database might be down.
Action: Try again later.
Cause: The sequence object might have been dropped by the primary database.
Action: Check the sequence status on the primary database.
- ORA-03182: The sequence object is no longer a global sequence for Oracle Active Data Guard standby database.
Cause: The sequence object might have been altered by the primary database.
Action: Check the sequence status on the primary database.
Cause: The parameter could not be changed during Oracle Active Data Guard (Oracle ADG) recovery.
Action: Stop the Oracle ADG recovery and then change the parameter value.
Cause: segment type is not TABLE, INDEX, or CLUSTER
Action: use a correct segment type