Oracle 11g Error Codes and Solution Suggestions from ORA-06100 to ORA-06300
- ORA-06102: NETTCP: cannot allocate context area
- Cause: Insufficient dynamic memory available for connection context area.
- Action: Contact your customer support representative.
- ORA-06105: NETTCP: remote host is unknown
- Cause: Host name specified in the login (connect) string is unknown.
- Action: Check spelling; make sure name is in the TCP/IP HOST file.
- ORA-06106: NETTCP: socket creation failure
- Cause: Process open file quota probably exceeded.
- Action: Contact your customer support representative.
- ORA-06107: NETTCP: ORACLE network server not found
- Cause: No entry in SERVICES file for ORACLE server.
- Action: Add (“orasrv”) entry to the TCP/IP SERVICES file.
- ORA-06108: NETTCP: connect to host failed
- Cause: Connection attempt to remote host has failed. Probably means that the SQL*Net TCP/IP server on the remote host is not up, or the host itself is not up (check the latter by targeting it with Telnet).
- Action: Start the SQL*Net TCP/IP server process on the remote host.
- ORA-06109: NETTCP: message receive failure
- Cause: I/O error occurred while attempting network read operation.
- Action: Contact your customer support representative.
- ORA-06110: NETTCP: message send failure
- Cause: I/O error occurred while attempting network write operation.
- Action: Contact your customer support representative.
- ORA-06111: NETTCP: disconnect failure
- Cause: Error occurred while closing a socket.
- Action: Contact your customer support representative.
- ORA-06112: NETTCP: invalid buffer size
- Cause: The buffer size specified in the login string exceeds the allowed maximum (of 4096).
- Action: Re-submit with valid buffer size.
- ORA-06113: NETTCP: Too many connections
- Cause: The maximum no. of concurrently open connections has been reached.
- Action: Exit an application with an open connection which is no longer required.
- ORA-06114: NETTCP: SID lookup failure
- Cause: From the remote host’s SQL*Net TCP/IP server: the database SID, specified in the login (connect) string, was not recognized.
- Action: Add the appropriate SID entry to the CONFIG.ORA file on the remote host (and restart the SQL*Net TCP/IP server).
- ORA-06115: NETTCP: unable to create ORACLE logicals
- Cause: The host’s SQL*Net TCP/IP server was unable to create the necessary logicals required by the ORACLE server process. See the SQL*Net TCP/IP server log file for more details.
- Action: Contact your system administrator.
- ORA-06116: NETTCP: unable to create ORASRV process
- Cause: The host’s SQL*Net TCP/IP server was unable to create the ORACLE server process. See the SQL*Net TCP/IP server log file for more details.
- Action: Contact your system administrator.
- ORA-06117: NETTCP: unable to create ORASRV: quota exceeded
- Cause: The host’s SQL*Net TCP/IP server was unable to create the ORACLE server process because of quota depletion.
- Action: Increase quota allocations to the SQL*Net TCP/IP server process.
- ORA-06118: NETTCP: unable to complete handshake with ORASRV
- Cause: The ORACLE server process was started but failed to complete its initialization.
- Action: Contact your customer support representative.
- ORA-06119: NETTCP: spurious client request
- Cause: The host’s SQL*Net TCP/IP server was unable to recognize this connection request. See the SQL*Net TCP/IP server log file for more details.
- Action: Contact your customer support representative.
- ORA-06120: NETTCP: network driver not loaded
- Cause: The TCP/IP network driver is not loaded.
- Action: Check that the TCP/IP driver is loaded correctly.
- ORA-06121: NETTCP: access failure
- Cause: The host’s SQL*Net TCP/IP server was unable to test the accessibility of the SID mapping file (specified in CONFIG.ORA) associated with this connection request. See the SQL*Net TCP/IP server log file for more details.
- Action: Contact your customer support representative.
- ORA-06122: NETTCP: setup failure
- Cause: The host’s SQL*Net TCP/IP server was unable to set up the appropriate environment to service this connection request. See the SQL*Net TCP/IP server log file for more details.
- Action: Contact your customer support representative.
- ORA-06123: NETTCP: cannot set KEEPALIVE
- Cause: The host’s SQL*Net TCP/IP server was unable to set the socket KEEPLIVE option. See the SQL*Net TCP/IP server log file for more details.
- Action: Contact your customer support representative.
- ORA-06124: NETTCP: timeout waiting for ORASRV
- Cause: The ORACLE server process was started but failed to respond after N secs.
- Action: For heavily loaded systems this is not an uncommon occurrence. Increase the value of N (the default is 30) by placing the following entry in the CONFIG.ORA file: SQLNET ORASRV_WAIT = <no. of secs> which will come into effect the next time the SQL*Net TCP/IP server is started.
- ORA-06125: NETTCP: ORASRV exited unexpectedly
- Cause: The ORACLE server process was started but exited unexpectedly. Possible causes:
- 1. Insufficient quotas to run ORASRV
- 2. ORACLE is not installed See the ORASRV output file for more details; the file will be in the ORA_SQLNET directory and will have a name of the form: ORA_SRVTnn_<SID>.OUT
- Action: If appropriate action is not obvious from the ORASRV output file then contact your customer support representative.
- ORA-06126: NETTCP: ORASRV unable to open network connection
- Cause: The ORACLE server process was started but was unable to open the socket passed to it by TCPSRV.
- Action: Contact your customer support representative.
- ORA-06127: NETTCP: unable to change username
- Cause: The host’s SQL*Net TCP/IP server could not establish a PROXY LOGIN connection because the client username is unknown (to the host OS).
- Action: Create new user account on host.
- ORA-06128: NETTCP: unable to create mailbox
- Cause: The host’s SQL*Net TCP/IP server was unable to create a mailbox (needed for IPC communication with the ORACLE server process). See the SQL*Net TCP/IP server log file for more details.
- Action: Contact your customer support representative.
- ORA-06129: NETTCP: unable to transfer socket ownership to ORASRV
- Cause: The host’s SQL*Net TCP/IP server was unable to transfer the network communication handle to the ORACLE server process. See the SQL*Net TCP/IP server log file for more details.
- Action: Contact your customer support representative.
- ORA-06130: NETTCP: host access denied
- Cause: The host’s SQL*Net TCP/IP server rejected this connection request because the client node does not have access privilege – as determined by the contents of the Valid Node Table (VNT), a component of the host’s CONFIG.ORA.
- Action: To grant access, add appropriate entry to the host’s VNT.
- ORA-06131: NETTCP: user access denied
- Cause: The host’s SQL*Net TCP/IP server rejected this connection request because the client user(name) does not have access privilege – as determined by the contents of the Username Mapping Table (UMT), a component of the host’s CONFIG.ORA.
- Action: To grant access, add appropriate entry to the host’s UMT.
- ORA-06132: NETTCP: access denied, wrong password
- Cause: The host SQL*Net TCP/IP server rejected this connection request because the client password did not match the host password.
- Action: To grant access, get passwords in sync.
- ORA-06133: NETTCP: file not found
- Cause: The host’s SQL*Net TCP/IP server could not find the SID mapping file (specified in CONFIG.ORA) associated with this connection request.
- Action: Check CONFIG.ORA for spelling; make correct entry.
- ORA-06134: NETTCP: file access privilege violation
- Cause: The host’s SQL*Net TCP/IP server did not have READ/ EXECUTE permission for the SID mapping file (specified in CONFIG.ORA) associated with this connection request.
- Action: Change protection on SID mapping file.
- ORA-06135: NETTCP: connection rejected; server is stopping
- Cause: The host’s SQL*Net TCP/IP server rejected this connection request because it is in the process of stopping.
- Action: Re-start SQL*Net TCP/IP server.
- ORA-06136: NETTCP: error during connection handshake
- Cause: Network I/O failure occurred while communicating with the host’s SQL*Net TCP/IP server. See the SQL*Net TCP/IP server log file for more details.
- Action: Contact your customer support representative.
- ORA-06137: NETTCP: error during connection handshake
- Cause: Network I/O failure occurred while communicating with the host’s SQL*Net TCP/IP server. See the SQL*Net TCP/IP server log file for more details.
- Action: Contact your customer support representative.
- ORA-06138: NETTCP: error during connection handshake
- Cause: Network I/O failure occurred while communicating with the host’s SQL*Net TCP/IP server. See the SQL*Net TCP/IP server log file for more details.
- Action: Contact your customer support representative.
- ORA-06140: NETTCP: no such user
- Cause: A proxy login connect attempt failed because the client username has no counterpart on the host.
- Action: None
- ORA-06141: NETTCP: no privilege for user
- Cause: A proxy login connect attempt failed because the SQL*Net TCP/IP server had insufficient privileges to access the proxy account.
- Action: Change account protection; change server privilges.
- ORA-06142: NETTCP: error getting user information
- Cause: A proxy login connect attempt failed because the SQL*Net TCP/IP server was unable to access the proxy account. See the SQL*Net TCP/IP server log file for more details.
- Action: Contact your customer support representative.
- ORA-06143: NETTCP: maximum connections exceeded
- Cause: The connect failed because the maximum conncurrent connections supported by the host’s SQL*Net TCP/IP server has already been reached.
- Action: Wait for a short period and re-try.
- ORA-06144: NETTCP: SID (database) is unavailable
- Cause: The database administrator on the host has varied the SID offline.
- Action: Wait for it to be varied back on-line.
- ORA-06145: NETTCP: unable to start ORASRV: images not installed
- Cause: The host’s SQL*Net TCP/IP server was unable to start the ORACLE server process because the ORACLE protected images were not installed.
- Action: Install the images.
- 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.
- ORA-06251: NETNTT: cannot translate address file name
- Cause: ORACLE_HOME environment variable not set.
- Action: Make sure that the ORACLE_HOME environment variable has been properly set and exported.
- ORA-06252: NETNTT: cannot open address file
- 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.
- ORA-06253: NETNTT: cannot read arguments from address file
- 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.
- ORA-06254: NETNTT: cannot share connection to cube
- 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.
- ORA-06255: NETNTT: cannot read pid of remote process
- Cause: An error occurred while reading the NTT communications link.
- Action: Contact your customer support representative.
- ORA-06256: NETNTT: remote fork failed
- 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.
- ORA-06257: NETNTT: cannot send command line to shadow process
- Cause: An error occurred while writing the NTT communications link.
- Action: Contact your customer support representative.
- ORA-06258: NETNTT: cannot allocate context area
- 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.
- ORA-06259: NETNTT: cannot read from remote process
- Cause: An error occurred while reading the NTT communications link.
- Action: Contact your customer support representative.
- ORA-06260: NETNTT: cannot write to remote process
- Cause: An error occurred while writing the NTT communications linke.
- Action: Contact your customer support representative.
- ORA-06261: NETNTT: nrange() failed
- Cause: The call to ‘nrange()’ failed while attempting to establish a connection.
- Action: Contact your customer support representative.
- ORA-06262: NETNTT: nfconn() failed
- Cause: The call to ‘nfconn()’ failed while attempting to establish a connection.
- Action: Contact your customer support representative.
- ORA-06263: NETNTT: out of memory in pi_connect
- 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.
- ORA-06264: NETNTT: data protocol error
- Cause: The NTT two-task driver received an unexpected message type.”
- Action: Contact your customer support representative.
- ORA-06265: NETNTT: break protocol error
- Cause: The NTT two-task driver received an unexpected message type.”
- Action: Contact your customer support representative.
- ORA-06266: NETNTT: bad write length
- Cause: The NTT two-task driver failed on an internal consistency check.
- Action: Contact your customer support representative.
- ORA-06267: NETNTT: bad state
- Cause: The NTT two-task driver failed on an internal consistency check.
- Action: Contact your customer support representative.
- ORA-06268: NETNTT: cannot read /etc/oratab
- 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.
- ORA-06300: IPA: Disconnect failure
- 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.