Oracle 12c R2 Error Codes and Solution Suggestions from ORA-06250 to ORA-06500
- ORA-06250: NETNTT: cannot allocate send and receive buffers
Cause: Two-task driver could not allocate data buffers.
Action: There is insufficient memory to run your program. Kill off other processes to free up memory.
Cause: ORACLE_HOME environment variable not set.
Action: Make sure that the ORACLE_HOME environment variable has been properly set and exported.
Cause: The NTT two-task driver could not open a file containing address information.
Action: Make sure that the ORACLE_HOME environment variable has been properly set and exported. Make sure the instance you are attempting to connect to is actually up and running.
Cause: The NTT two-task driver could not read addressing information from its addressing file.
Action: Make sure that the ORACLE_HOME environment variable has been properly set and exported. Make sure the instance you are attempting to connect to is actually up and running.
Cause: The NTT two-task driver could not share a connection to the cube.
Action: Make sure that the ORACLE_HOME environment variable has been properly set and exported. Make sure the instance you are attempting to connect to is actually up and running.
Cause: An error occurred while reading the NTT communications link.
Action: Contact your customer support representative.
Cause: The Oracle listener process on the cube could not fork off a shadow process.
Action: The instance you are trying to connect to probably doesn’t have enough memory to run another shadow process. Ask someone else to log off, or connect to a different instance.
Cause: An error occurred while writing the NTT communications link.
Action: Contact your customer support representative.
Cause: Two-task driver could not allocate data buffers.
Action: There is insufficient memory to run your program. Kill off other processes to free up memory.
Cause: An error occurred while reading the NTT communications link.
Action: Contact your customer support representative.
Cause: An error occurred while writing the NTT communications linke.
Action: Contact your customer support representative.
Cause: The call to ‘nrange()’ failed while attempting to establish a connection.
Action: Contact your customer support representative.
Cause: The call to ‘nfconn()’ failed while attempting to establish a connection.
Action: Contact your customer support representative.
Cause: Two-task driver could not allocate data buffers.
Action: There is insufficient memory to run your program. Kill off other processes to free up memory.
Cause: The NTT two-task driver received an unexpected message type.”
Action: Contact your customer support representative.
Cause: The NTT two-task driver received an unexpected message type.”
Action: Contact your customer support representative.
Cause: The NTT two-task driver failed on an internal consistency check.
Action: Contact your customer support representative.
Cause: The NTT two-task driver failed on an internal consistency check.
Action: Contact your customer support representative.
Cause: The NTT two-task driver could not read configuration information from /etc/oratab.
Action: Make sure /etc/oratab exists and is readable. This error may occur if the file is incorrectly formatted. It also may occur if the driver has run out of memory.
Cause: A fatal error occurred during the disconnect from the server. This was probably caused by inaccessible message queues.
Action: If there is no message queue, restart the SQL*Net IPA servers using ipactl. Otherwise contact your customer support representative.
Cause: The memory pool is exhausted.
Action: Check the circumstances and try to allocate less memory in your program or adjust the init parameters in your INIT.ORA file and retry.
Cause: The cause may be one of the following: – there is no ADI server defined to reflect a connection to the specified host. – the remote host is not known by the local system. – the ORACLE kernel on the remote host is not generated with the IPA driver
Action: Check sequentially for the above causes and eliminate the actual cause found.
Cause: The SQL*Net IPA driver could not write the message into the message queue.
Action: Make sure that the message queue exists and is accessible. If necessary rerun ipactl.
Cause: The SQL*Net IPA driver could not read a message from the message queue.
Action: Make sure that the message queue exists and is accessible. If necessary rerun ipactl.
Cause: The communication between user and ORACLE is out of synchronization. This message should not normally be issued.
Action: Contact your customer support representative.
Cause: The IPA driver tried to write a message in the queue that was too big for the queue.
Action: Contact your customer support representative.
Cause: A fatal error occurred during the resetting of the connection.
Action: Contact your customer support representative.
Cause: You have exhausted all your connections.
Action: Try again when some of the current users have logged off.
Cause: The SQL*Net IPA servers have not been started.
Action: Run ipactl.
Cause: Environment variable(s) not set correctly.
Action: Check and correct.
Cause: Maximum number of servers reached.
Action: Shutdown and restart with an increased maximum number of servers. Note that database links consume one server per link. Be sure to start up enough servers to support database links.
Cause: Incorrect outgoing service name supplied.
Action: Check and correct the service name.
Cause: The shared memory has not been set up correctly.
Action: Contact your system manager.
Cause: Fatal interprocess communication error.
Action: Contact your system manager.
Cause: The connect string is malformed.
Action: Check and correct.
Cause: The SID is unknown at the remote side.
Action: Either the database does not exist, is not running, or there are no reserved servers for that SID.
Cause: The maximum number of simultaneous users of SQL*Net IPA has been exceeded on the local side.
Action: Wait for free connections to become available. If the problem persists, contact your system manager.
Cause: The maximum number of simultaneous connections that SQL*Net IPA can handle to different hosts has been exceeded on the local side.
Action: Wait for free connections to become available. If the problem persists, contact your system manager.
Cause: The maximum number of simultaneous users of SQL*Net IPA has been exceeded on the remote side.
Action: Wait for free connections to become available. If the problem persists, contact your system manager.
Cause: The maximum number of simultaneous connections that SQL*Net IPA can handle from different hosts has been exceeded on the remote side.
Action: Wait for free connections to become available. If the problem persists, contact your system manager.
Cause: There has been a timeout on an attempt to connect to a remote server the reason for which is most likely to be the remote SQL*Net IPA software is not running. An alternative reason could be that the remote initiator service name is incorrect.
Action: Check and start the remote SQL*Net software. Check that it is started with the correct service names supplied.
Cause: An internal error has occurred in the shared memory handling.
Action: Contact customer support.
Cause: Fatal interprocess communication error.
Action: Contact your system manager.
Cause: There was no default host string specified in the configuration and the user didn’t specify any explicit connect string.
Action: Either reconfigure the system specifying a default connect string or use an explicit connect string.
Cause: The login (connect) string contains an invalid driver designator.
Action: Correct the string and re-submit.
Cause: Error occurred while attempting to read a break message.
Action: Contact your customer support representative.
Cause: System unable to allocate needed virtual memory.
Action: Configure more memory, reduce load, or simply try again.
Cause: Syntax error in login string.
Action: Correct string and re-submit.
Cause: Unable to reset out of break state.
Action: Contact your customer support representative.
Cause: Error occurred while attempting to send a break message.
Action: Contact your customer support representative.
Cause: Error occurred while attempting to set up asynchronous handlers for in-coming, out-of-band break messages.
Action: Contact your customer support representative.
Cause: Message from partner contains bad header.
Action: Contact your customer support representative.
Cause: Unable to establish connection.
Action: Use diagnostic procedures to ascertain exact problem.
Cause: Error occurred while testing I/O status of the network connection.
Action: Contact your customer support representative.
Cause: The remote server was unable to start an ORACLE process on behalf of the client.
Action: Make sure permissions on the remote ORACLE program are correctly set. Contact your system administrator.
Cause: From the remote host’s server: the database SID, specified in the login (connect) string, was not recognized.
Action: Add the appropriate SID entry to the CONFIG.ORA or oratab file on the remote host (restarting the remote server may be needed).
Cause: Error found during recomputation of checksum or CRC.
Action: Possible hardware failures of communication nodes. Contact system administrator immediately.
Cause: Unable to transmit data to remote host.
Action: Try reconnect to remote host, and contact your system administrator.
Cause: Unable to receive data from remote host.
Action: Try reconnect to remote host, and contact your system administrator.
Cause: A function was called with an invalid argument.
Action: Contact your Oracle Customer Support Representative.
Cause: The file block number is out of range of the file. The additional information returns the block number.
Action: Verify that the block number is correct. Run dbfsize and check if the block number is in that range. Contact your Oracle Customer Support Representative.
Cause: The I/O buffer was not aligned on a 2K boundary.
Action: Contact your Oracle Customer Support Representative.
Cause: The additional information returns the block number
Action: Look up the additional information returned in your operating system reference manual. Verify that the block number is correct.
Cause: The read system call returned an error.
Action: The additional information indicates the block number. Look up the additional information returned in your operating system manual.
Cause: The write system call returned an error.
Action: The additional information indicates the block number. Look up the additional information returned in your operating system manual.
Cause: The Asynchronous I/O system call returned an error.
Action: The additional information indicates the block number. Look up the additional information returned in your operating system manual.
Cause: The Asynchronous I/O system call returned an error.
Action: The additional information indicates the block number. Look up the additional information returned in your operating system manual.
Cause: The Asynchronous I/O system call returned an error.
Action: The additional information indicates the block number. Look up the additional information returned in your operating system manual.
Cause: This write call may have been truncated. The additional information returns the block number and number of bytes.
Action: Verify that the block number and the number of bytes written are correct.
Cause: This read call may have been truncated. The additional information returns the block number and number of bytes.
Action: Verify that the block number and the number of bytes read are correct.
Cause: Either the ORACLE process id, or wait time or event ID is invalid.
Action: The additional information indicates the process id, time and event id.
Cause: Some system problems may exists on your system, please check error logs.
Action: The additional information indicates the error number. Look up the additional information returned in your operating system manual.
Cause: An invalid event ID is passed in to this routine.
Action: The additional information indicates the event id.
Cause: Some system problems may exist on your system, please check error logs.
Action: The additional information indicates the error number. Look up the additional information returned in your operating system manual.
Cause: An invalid event id, or the low and high event ID do not exist.
Action: The additional information indicates the error number. It also contains the event id, low boundary and high boundary.
Cause: Some system problems may exist on your system, please check error logs.
Action: The additional information indicates the error number. Look up the additional information returned in your operating system manual.
Cause: Invalid oracle process ID is passed in to this routine.
Action: The additional information indicates the process id.
Cause: Some system problems may exists on your system, please check error logs.
Action: The additional information indicates the error number. Look up the additional information returned in your operating system manual.
Cause: ORACLE tries to use the sysvendor interface (INIT.ORA parameter use_sysvendor=true) but the UNIX kernel does not have the ORACLE sysvendor interface linked in.
Action: Set use_sysvendor=false in INIT.ORA, if you don’t want to use this interface or link the UNIX kernel with this interface so that ORACLE can use it.
Cause: PL/SQL was unable to allocate additional storage. This message normally appears with an ORA-4030 or ORA-4031 error which gives additional information. Sometimes this error can be caused by runaway programs.
Action: 1) Ensure there are no issues or bugs in your PL/SQL program which are causing excessive amounts of memory to be used. 2) Programmatically cause unused objects to be freed (e.g. by setting them to NULL). 3) Increase the amount of shared or process memory (as appropriate) available to you.