Oracle 12c R2 Error Codes and Solution Suggestions from ORA-06800 to ORA-07000
- ORA-06800: TLI Driver: SQL*Net SPX client went away during reconnect
Cause: The client process was aborted by the system or the user, and was unable to complete the connection establishment with the server listener process.
Action: Determine cause of client exit, and reattempt connection.
Cause: An unknown event occurred on the client’s listening socket.
Action: Contact your customer support representative.
Cause: The /etc/netware/yellowpages file does not exist, or is not readable by the TLI listener process.
Action: Insure the file exists and is readable. Make sure that the server machine’s node name, network number, ethernet address, and listening socket number are encoded in the file.
Cause: The /dev/ipx file does not exist, or the driver has not been installed in the kernel correctly.
Action: Reinvoke the Oracle root installation. If problem continues, contact your customer support representative.
Cause: The IPX driver has not been correctly installed.
Action: Reinvoke the Oracle root installation. If problem continues, contact your customer support representative.
Cause: The socket endpoint for sending SAP packet was corrupted for some unknown reason.
Action: Contact your customer support representative.
Cause: A step in the SPX/IPX protocol initialization failed.
Action: Check the previous error reported, and follow corrective action.
Cause: The file /dev/eth does not exist, or the driver it references could not be opened.
Action: The system’s real ethernet device file, for example /dev/wd, for the Western Digital ethernet driver, should be linked to the file /dev/eth. If this has been done, insure that the ethernet driver has been installed by completing the TCP/IP installation on your system, and testing a connection. If problem continues, contact your customer support representative for a list of supported ethernet drivers.
Cause: Either the ethernet driver has not been installed in the system correctly, or the ethernet driver is not supported.
Action: Insure that the ethernet driver has been installed by completing the TCP/IP installation on your system, and testing a connection. If problem continues, contact your customer support representative for a list of supported ethernet drivers.
Cause: The IPX driver has not been correctly installed.
Action: Reinvoke the Oracle root installation. If problem continues, contact your customer support representative.
Cause: The IPX driver has not been correctly installed.
Action: Reinvoke the Oracle root installation. If problem continues, contact your customer support representative.
Cause: The IPX driver has not been correctly installed, or the network number encoded in the /etc/netware/yellowpages file is invalid.
Action: The network number in the yellowpages file should match the four-byte network number of your Novell file server. If this is configured correctly, reinvoke the Oracle root installation. If problem continues, contact your customer support representative.
Cause: The ethernet driver is not installed correctly, or does not support this operation.
Action: Contact your customer support representative for a list of supported ethernet drivers.
Cause: The node address read from the ethernet driver does not match the value encoded in the /etc/netware/yellowpages file for this server.
Action: Confirm the correct ethernet node address for your LAN card, and enter this value in the yellowpages file.
Cause: The /dev/nspxd file does not exist, or the driver has not been installed in the kernel correctly.
Action: Reinvoke the Oracle root installation. If problem continues, contact your customer support representative.
Cause: The SPX driver has not been correctly installed.
Action: Reinvoke the Oracle root installation. If problem continues, contact your customer support representative.
Cause: The SPX driver has not been correctly installed.
Action: Reinvoke the Oracle root installation. If problem continues, contact your customer support representative.
Cause: The file $ORACLE_HOME/spx/address could not be opened for reading and writing.
Action: Make sure ORACLE_HOME is set, and the permissions on the ORACLE_HOME are read, write. If this file has been unintentially deleted, run spxctl (net option) to reset the configured Novell network number for SQL*Net SPX.
Cause: CMX is not started on your system.
Action: Install and/or start CMX on your system.
Cause: Local application oracmx has no local name assigned
Action: Enter unique local name for oracmx in the tns directory
Cause: ccp-xxxx is not started
Action: start your ccp software on the communication controller
Cause: remote application not entered in tns directory
Action: enter remote application in tns directory
Cause: no local name assigned to remote application
Action: assign local name to remote application
Cause: remote partner not listening
Action: make sure remote node has CMX installed and running make sure oracmx is running on remote host
Cause: internal error in CMX
Action: contact your customer support representative
Cause: remote partner aborted
Action: contact your customer support representative
Cause: remote partner aborted
Action: contact your customer support representative
Cause: remote partner aborted
Action: contact your customer support representative
Cause: oracle process not found or wrong mode (should be 4751)
Action: change /etc/oratab or set mode to 4751
Cause: internal error in CMX
Action: contact your customer support representative
Cause: internal error in CMX
Action: contact your customer support representative
Cause: oracmx has been stopped, or user process has been aborted
Action: contact your customer support representative
Cause: connect sequence out of sync
Action: contact your customer support representative
Cause: internal error in CMX
Action: contact your customer support representative
Cause: remote partner aborted
Action: contact your customer support representative
Cause: internal error in CMX
Action: contact your customer support representative
Cause: internal error in CMX
Action: contact your customer support representative
Cause: internal error in CMX
Action: contact your customer support representative
Cause: received packets are corrupted
Action: contact your customer support representative
Cause: received packets are corrupted
Action: contact your customer support representative
Cause: internal error in CMX
Action: contact your customer support representative
Cause: break handling out of sync
Action: contact your customer support representative
Cause: received packets are corrupted
Action: contact your customer support representative
Cause: partner is not responding
Action: make sure partner is up and running and reachable
Cause: internal error in CMX
Action: contact your customer support representative
Cause: internal error in CMX
Action: contact your customer support representative
Cause: ORACLE_SID is not entered in remote oratab
Action: add ORACLE_SID to remote oratab
Cause: internal error in CMX
Action: contact your customer support representative
Cause: internal error in CMX
Action: contact your customer support representative
Cause: internal error in CMX
Action: contact your customer support representative
Cause: internal error in CMX
Action: contact your customer support representative
Cause: internal error in CMX
Action: contact your customer support representative
Cause: SQL*Net AppleTalk error codes base. This is not an error.
Action: None
Cause: AppleTalk API received error in VMS system service.
Action: Contact Oracle Customer Support representative.
Cause: Peer program may have aborted
Action: Investigate network problems and try again.
Cause: Not enough memory available.
Action: Check VMS process quotas and/or sysgen parameters
Cause: Erroneous file name
Action: Check path name for server output file, or SQL*Net Appletalk Logical names and symbols.
Cause: Too many database connections.
Action: Check ATKSRV_MAXCONparameter in configuration file.
Cause: Unable to get Appletalk host name.
Action: Check Appletalk configuration.
Cause: Incoming SQL*Net connection specified invalid SID name.
Action: Specify correct SID in connect string and retry.
Cause: Unable to access CONFIG.ATK
Action: Check file protections.
Cause: Buffered I/O quota exceeded.
Action: Increase BIOlm using AUTHORIZE utility and retry.
Cause: SQL*Net Appletalk listener could not create log file.
Action: Check directory path and protections.
- ORA-06961: Insufficient privilege for attempted operation
- ORA-06970: X.25 Driver: remote host is unknown
Cause: Host name specified in the login (connect string) is unknown.
Action: Check spelling; make sure name is in the X.25 HOST file.
- ORA-06971: X.25 Driver: error while receiving data
- ORA-06972: X.25 Driver: error while sending data
- ORA-06973: X.25 Driver: invalid buffer size
Cause: The buffer size specified in the login string must be between 5 and 4096.
Action: Re-submit with valid buffer size.
Cause: From the remote host’s SQL*Net X.25 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 X.25 server).
Cause: Connection attempt to remote host has failed. Probably means that the SQL*Net X.25 server on the remote host is not up, or the host itself is not up.
Action: Start the SQL*Net X.25 server process on the remote host.
Cause: Process open file quota probably exceeded.
Action: Contact your customer support representative.
Cause: X.25 level 2 is down. X.25 link is not working.
Action: Run system checks to verify functioning of X.25 software. Contact your hardware vendor.
Cause: Call back address probably same as called address.
Action: Verify that callback address and called address are different.
Cause: The remote X.25 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.