Oracle 12c R2 Error Codes and Solution Suggestions from ORA-06800 to ORA-07000

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.

ORA-06801: TLI Driver: listen for SPX server reconnect failed

Cause: An unknown event occurred on the client’s listening socket.

Action: Contact your customer support representative.

ORA-06802: TLI Driver: could not open the /etc/netware/yellowpages file

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.

ORA-06803: TLI Driver: the IPX device file could not be opened

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.

ORA-06804: TLI Driver: could not bind an IPX address at initialization

Cause: The IPX driver has not been correctly installed.

Action: Reinvoke the Oracle root installation. If problem continues, contact your customer support representative.

ORA-06805: TLI Driver: could not send datagram SAP packet for SPX

Cause: The socket endpoint for sending SAP packet was corrupted for some unknown reason.

Action: Contact your customer support representative.

ORA-06806: TLI Driver: could not complete protocol initialization for SPX

Cause: A step in the SPX/IPX protocol initialization failed.

Action: Check the previous error reported, and follow corrective action.

ORA-06807: TLI Driver: could not open ethernet device driver file

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.

ORA-06808: TLI Driver: could not link IPX and ethernet streams

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.

ORA-06809: TLI Driver: could not clear the IPX ethernet SAP at init

Cause: The IPX driver has not been correctly installed.

Action: Reinvoke the Oracle root installation. If problem continues, contact your customer support representative.

ORA-06810: TLI Driver: could not set the IPX ethernet SAP at init

Cause: The IPX driver has not been correctly installed.

Action: Reinvoke the Oracle root installation. If problem continues, contact your customer support representative.

ORA-06811: TLI Driver: could not set the IPX network number at init

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.

ORA-06812: TLI Driver: could not read the ethernet driver’s node address

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.

ORA-06813: TLI Driver: the configured ethernet address is incorrect

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.

ORA-06814: TLI Driver: the SPX device file could not be opened

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.

ORA-06815: TLI Driver: could not link SPX and IPX streams

Cause: The SPX driver has not been correctly installed.

Action: Reinvoke the Oracle root installation. If problem continues, contact your customer support representative.

ORA-06816: TLI Driver: could not set the SPX SAP address

Cause: The SPX driver has not been correctly installed.

Action: Reinvoke the Oracle root installation. If problem continues, contact your customer support representative.

ORA-06817: TLI Driver: could not read the Novell network address

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.

ORA-06900: CMX: cannot read tns directory

Cause: CMX is not started on your system.

Action: Install and/or start CMX on your system.

ORA-06901: CMX: no local name assigned to local application

Cause: Local application oracmx has no local name assigned

Action: Enter unique local name for oracmx in the tns directory

ORA-06902: CMX: cannot attach to cmx subsystem

Cause: ccp-xxxx is not started

Action: start your ccp software on the communication controller

ORA-06903: CMX: cannot read transport address of remote application

Cause: remote application not entered in tns directory

Action: enter remote application in tns directory

ORA-06904: CMX: no transport address available for remote application

Cause: no local name assigned to remote application

Action: assign local name to remote application

ORA-06905: CMX: connect error

Cause: remote partner not listening

Action: make sure remote node has CMX installed and running make sure oracmx is running on remote host

ORA-06906: CMX: cannot get maximum packet size from CMX

Cause: internal error in CMX

Action: contact your customer support representative

ORA-06907: CMX: error during connect confirmation

Cause: remote partner aborted

Action: contact your customer support representative

ORA-06908: CMX: error during transfer of ORACLE_SID

Cause: remote partner aborted

Action: contact your customer support representative

ORA-06909: CMX: error during acknowledge of ORACLE_SID

Cause: remote partner aborted

Action: contact your customer support representative

ORA-06910: CMX: Cannot start oracle process on remote machine

Cause: oracle process not found or wrong mode (should be 4751)

Action: change /etc/oratab or set mode to 4751

ORA-06911: CMX: t_event returns ERROR

Cause: internal error in CMX

Action: contact your customer support representative

ORA-06912: CMX: write error in datarq

Cause: internal error in CMX

Action: contact your customer support representative

ORA-06913: CMX: error during redirection of connection

Cause: oracmx has been stopped, or user process has been aborted

Action: contact your customer support representative

ORA-06914: CMX: unexepected event during start of oracle

Cause: connect sequence out of sync

Action: contact your customer support representative

ORA-06915: CMX: unknown t_event in datarq

Cause: internal error in CMX

Action: contact your customer support representative

ORA-06916: CMX: error in data read (t_datain)

Cause: remote partner aborted

Action: contact your customer support representative

ORA-06917: CMX: error in data read (too many bytes read)

Cause: internal error in CMX

Action: contact your customer support representative

ORA-06918: CMX: T_NOEVENT during wait for read event

Cause: internal error in CMX

Action: contact your customer support representative

ORA-06919: CMX: error during write request (unknown event)

Cause: internal error in CMX

Action: contact your customer support representative

ORA-06920: CMX: getbrkmsg illegal datatype

Cause: received packets are corrupted

Action: contact your customer support representative

ORA-06921: CMX: getdatmsg illegal datatype

Cause: received packets are corrupted

Action: contact your customer support representative

ORA-06922: CMX: bad write length

Cause: internal error in CMX

Action: contact your customer support representative

ORA-06923: CMX: illegal break condition

Cause: break handling out of sync

Action: contact your customer support representative

ORA-06924: CMX: wrong break message length

Cause: received packets are corrupted

Action: contact your customer support representative

ORA-06925: CMX: disconnect during connect request

Cause: partner is not responding

Action: make sure partner is up and running and reachable

ORA-06926: CMX: T_ERROR during read data

Cause: internal error in CMX

Action: contact your customer support representative

ORA-06927: CMX: T_DATAIN received before all data written

Cause: internal error in CMX

Action: contact your customer support representative

ORA-06928: CMX: wrong ORACLE_SID

Cause: ORACLE_SID is not entered in remote oratab

Action: add ORACLE_SID to remote oratab

ORA-06929: CMX: error when sending ORACLE_SID

Cause: internal error in CMX

Action: contact your customer support representative

ORA-06930: CMX: error when checking ORACLE_SID

Cause: internal error in CMX

Action: contact your customer support representative

ORA-06931: CMX: error during read_properties for server

Cause: internal error in CMX

Action: contact your customer support representative

ORA-06932: CMX: error in local name

Cause: internal error in CMX

Action: contact your customer support representative

ORA-06933: CMX: error during attach

Cause: internal error in CMX

Action: contact your customer support representative

ORA-06950: No error

Cause: SQL*Net AppleTalk error codes base. This is not an error.

Action: None

ORA-06951: Operating system call error

Cause: AppleTalk API received error in VMS system service.

Action: Contact Oracle Customer Support representative.

ORA-06952: Remote end of the communication issued a forward-reset packet.

Cause: Peer program may have aborted

Action: Investigate network problems and try again.

ORA-06953: Not enough virtual memory

Cause: Not enough memory available.

Action: Check VMS process quotas and/or sysgen parameters

ORA-06954: Illegal file name

Cause: Erroneous file name

Action: Check path name for server output file, or SQL*Net Appletalk Logical names and symbols.

ORA-06955: Number of database servers exceed limit

Cause: Too many database connections.

Action: Check ATKSRV_MAXCONparameter in configuration file.

ORA-06956: Failed to get local host name

Cause: Unable to get Appletalk host name.

Action: Check Appletalk configuration.

ORA-06957: No SID is currently available

Cause: Incoming SQL*Net connection specified invalid SID name.

Action: Specify correct SID in connect string and retry.

ORA-06958: Failed to access configuration file

Cause: Unable to access CONFIG.ATK

Action: Check file protections.

ORA-06959: Buffer I/O quota is too small

Cause: Buffered I/O quota exceeded.

Action: Increase BIOlm using AUTHORIZE utility and retry.

ORA-06960: Failed to access log file

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.

ORA-06974: X.25 Driver: SID lookup failure

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).

ORA-06975: X.25 Driver: connect to host failed

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.

ORA-06976: X.25 Driver: endpoint creation failure

Cause: Process open file quota probably exceeded.

Action: Contact your customer support representative.

ORA-06977: X.25 Driver: X.25 Level 2 failure

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.

ORA-06978: X.25 Driver: Too many callback tries

Cause: Call back address probably same as called address.

Action: Verify that callback address and called address are different.

ORA-06979: X.25 Driver: server cannot start oracle

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.