Oracle Error Messages: 02/07/12

Tuesday 7 February 2012

ORA-06926: CMX: T_ERROR during read data

ORA-06926: CMX: T_ERROR during read data

Cause: internal error in CMX

Action: contact your customer support representative

ORA-06925: CMX: disconnect during connect request

ORA-06925: CMX: disconnect during connect request

Cause: partner is not responding

Action: make sure partner is up and running and reachable

ORA-06924: CMX: wrong break message length

ORA-06924: CMX: wrong break message length

Cause: received packets are corrupted

Action: contact your customer support representative

ORA-06923: CMX: illegal break condition

ORA-06923: CMX: illegal break condition

Cause: break handling out of sync

Action: contact your customer support representative

ORA-06922: CMX: bad write length

ORA-06922: CMX: bad write length

Cause: internal error in CMX

Action: contact your customer support representative

ORA-06921: CMX: getdatmsg illegal datatype

ORA-06921: CMX: getdatmsg illegal datatype

Cause: received packets are corrupted

Action: contact your customer support representative

ORA-06920: CMX: getbrkmsg illegal datatype

ORA-06920: CMX: getbrkmsg illegal datatype

Cause: received packets are corrupted

Action: contact your customer support representative

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

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

Cause: internal error in CMX

Action: contact your customer support representative

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

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

Cause: internal error in CMX

Action: contact your customer support representative

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

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

Cause: internal error in CMX

Action: contact your customer support representative

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

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

Cause: remote partner aborted

Action: contact your customer support representative

ORA-06915: CMX: unknown t_event in datarq

ORA-06915: CMX: unknown t_event in datarq

Cause: internal error in CMX

Action: contact your customer support representative

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

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

Cause: connect sequence out of sync

Action: contact your customer support representative

ORA-06913: CMX: error during redirection of connection

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-06912: CMX: write error in datarq

ORA-06912: CMX: write error in datarq

Cause: internal error in CMX

Action: contact your customer support representative

ORA-06911: CMX: t_event returns ERROR

ORA-06911: CMX: t_event returns ERROR

Cause: internal error in CMX

Action: contact your customer support representative

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

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

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

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

ORA-06909: CMX: error during acknowledge of ORACLE_SID

ORA-06909: CMX: error during acknowledge of ORACLE_SID

Cause: remote partner aborted

Action: contact your customer support representative

ORA-06908: CMX: error during transfer of ORACLE_SID

ORA-06908: CMX: error during transfer of ORACLE_SID

Cause: remote partner aborted

Action: contact your customer support representative

ORA-06907: CMX: error during connect confirmation

ORA-06907: CMX: error during connect confirmation

Cause: remote partner aborted

Action: contact your customer support representative

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

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

Cause: internal error in CMX

Action: contact your customer support representative

ORA-06905: CMX: connect error

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-06904: CMX: no transport address available for remote application

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-06903: CMX: cannot read transport address of remote application

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-06902: CMX: cannot attach to cmx subsystem

ORA-06902: CMX: cannot attach to cmx subsystem

Cause: ccp-xxxx is not started

Action: start your ccp software on the communication controller

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

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-06900: CMX: cannot read tns directory

ORA-06900: CMX: cannot read tns directory

Cause: CMX is not started on your system.

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

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

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

Cause: The file $ORACLE_HOME or spx or 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-06816: TLI Driver: could not set the SPX SAP address

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-06815: TLI Driver: could not link SPX and IPX streams

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-06814: TLI Driver: the SPX device file could not be opened

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

Cause: The or dev or 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-06813: TLI Driver: the configured ethernet address is incorrect

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 or etc or netware or 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-06812: TLI Driver: could not read the ethernet driver s node address

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-06811: TLI Driver: could not set the IPX network number at init

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 or etc or netware or 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-06810: TLI Driver: could not set the IPX ethernet SAP at init

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-06809: TLI Driver: could not clear the IPX ethernet SAP at init

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-06808: TLI Driver: could not link IPX and ethernet streams

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 or 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-06807: TLI Driver: could not open ethernet device driver file

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

Cause: The file or dev or eth does not exist, or the driver it references could not be opened.

Action: The system s real ethernet device file, for example or dev or wd, for the Western Digital ethernet driver, should be linked to the file or dev or eth. If this has been done, insure that the ethernet driver has been installed by completing the TCP or 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-06806: TLI Driver: could not complete protocol initialization for SPX

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

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

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

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

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-06804: TLI Driver: could not bind an IPX address at initialization

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-06803: TLI Driver: the IPX device file could not be opened

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

Cause: The or dev or 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-06802: TLI Driver: could not open the or etc or netware or yellowpages file

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

Cause: The or etc or netware or 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-06801: TLI Driver: listen for SPX server reconnect failed

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-06800: TLI Driver: SQL*Net SPX client went away during reconnect

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-06794: TLI Driver: shadow process could not retrieve protocol info

ORA-06794: TLI Driver: shadow process could not retrieve protocol info

Cause: The ORACLE process either failed to allocate memory to store the protocol information record, or the protocol rejected the request for some unknown reason.

Action: Contact your customer support representative.

ORA-06793: TLI Driver: server cannot create new process

ORA-06793: TLI Driver: server cannot create new process

Cause: The remote TLI server was unable to start an ORACLE process on behalf of the client.

Action: Note the operating system error message or number and contact your system adminstrator. The remote host may be unable to create any new processes due to a full process table.

ORA-06792: TLI Driver: server cannot exec oracle

ORA-06792: TLI Driver: server cannot exec oracle

Cause: The remote TLI server was unable to start an ORACLE process on behalf of the client.

Action: Note the operating system error message or number and contact your system adminstrator. The permissions on the remote ORACLE program may be set incorrectly.