ORA-06119: NETTCP: spurious client request

ORA-06119: NETTCP: spurious client request

Cause: The host s SQL*Net TCP or IP server was unable to recognize this connection request. See the SQL*Net TCP or IP server log file for more details.

Action: Contact your customer support representative.

ORA-06118: NETTCP: unable to complete handshake with ORASRV

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-06117: NETTCP: unable to create ORASRV: quota exceeded

ORA-06117: NETTCP: unable to create ORASRV: quota exceeded

Cause: The host s SQL*Net TCP or IP server was unable to create the ORACLE server process because of quota depletion.

Action: Increase quota allocations to the SQL*Net TCP or IP server process.

ORA-06116: NETTCP: unable to create ORASRV process

ORA-06116: NETTCP: unable to create ORASRV process

Cause: The host s SQL*Net TCP or IP server was unable to create the ORACLE server process. See the SQL*Net TCP or IP server log file for more details.

Action: Contact your system administrator.

ORA-06115: NETTCP: unable to create ORACLE logicals

ORA-06115: NETTCP: unable to create ORACLE logicals

Cause: The host s SQL*Net TCP or IP server was unable to create the necessary logicals required by the ORACLE server process. See the SQL*Net TCP or IP server log file for more details.

Action: Contact your system administrator.

ORA-06114: NETTCP: SID lookup failure

ORA-06114: NETTCP: SID lookup failure

Cause: From the remote host s SQL*Net TCP or 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 or IP server).

ORA-06113: NETTCP: Too many connections

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-06112: NETTCP: invalid buffer size

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-06111: NETTCP: disconnect failure

ORA-06111: NETTCP: disconnect failure

Cause: Error occurred while closing a socket.

Action: Contact your customer support representative.

ORA-06110: NETTCP: message send failure

ORA-06110: NETTCP: message send failure

Cause: I or O error occurred while attempting network write operation.

Action: Contact your customer support representative.

ORA-06109: NETTCP: message receive failure

ORA-06109: NETTCP: message receive failure

Cause: I or O error occurred while attempting network read operation.

Action: Contact your customer support representative.

ORA-06108: NETTCP: connect to host failed

ORA-06108: NETTCP: connect to host failed

Cause: Connection attempt to remote host has failed. Probably means that the SQL*Net TCP or 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 or IP server process on the remote host.

ORA-06107: NETTCP: ORACLE network server not found

ORA-06107: NETTCP: ORACLE network server not found

Cause: No entry in SERVICES file for ORACLE server.

Action: Add ( orasrv ) entry to the TCP or IP SERVICES file.

ORA-06106: NETTCP: socket creation failure

ORA-06106: NETTCP: socket creation failure

Cause: Process open file quota probably exceeded.

Action: Contact your customer support representative.

ORA-06105: NETTCP: remote host is unknown

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 or IP HOST file.

ORA-06102: NETTCP: cannot allocate context area

ORA-06102: NETTCP: cannot allocate context area

Cause: Insufficient dynamic memory available for connection context area.

Action: Contact your customer support representative.

ORA-06044: NETDNT: connect failed, byte count quota exceeded

ORA-06044: NETDNT: connect failed, byte count quota exceeded

Cause: Connect failed because of insufficient byte count quota.

Action: Increase byte count quota.

ORA-06043: NETDNT: message send failure

ORA-06043: NETDNT: message send failure

Cause: Driver gets I or O error while doing network write operation

Action: Contact your customer support representative.

ORA-06042: NETDNT: message receive failure

ORA-06042: NETDNT: message receive failure

Cause: Driver gets I or O error while doing network read operation

Action: Contact your customer support representative.

ORA-06041: NETDNT: disconnect failed

ORA-06041: NETDNT: disconnect failed

Cause: Driver gets error while doing network close operation

Action: Contact your customer support representative.

ORA-06040: NETDNT: invalid login (connect) string

ORA-06040: NETDNT: invalid login (connect) string

Cause: Syntax error in login string.

Action: Resubmit with correct string.

ORA-06039: NETDNT: connect failed

ORA-06039: NETDNT: connect failed

Cause: Connect failed for unexpected reason (see OSD error).

Action: Contact your customer support representative.

ORA-06037: NETDNT: connect failed, node unreachable

ORA-06037: NETDNT: connect failed, node unreachable

Cause: Host node is down.

Action: Contact your network administrator.

ORA-06035: NETDNT: connect failed, insufficient resources

ORA-06035: NETDNT: connect failed, insufficient resources

Cause: Insufficient system resources are available to complete the connection; for example, all DECnet channels are in use.

Action: Contact your network administrator.

ORA-06034: NETDNT: connect failed, partner exited unexpectedly

ORA-06034: NETDNT: connect failed, partner exited unexpectedly

Cause: Connection with host node was made but partner aborted

Action: Make sure object (see 06031, above) is working (for VMS run the command file and make sure that the ORACLE server process starts up); sometimes happens when the network or node is under stress - in this case a retry often works.

ORA-06033: NETDNT: connect failed, partner rejected connection

ORA-06033: NETDNT: connect failed, partner rejected connection

Cause: Connection with partner was made but was rejected.

Action: Contact your network administrator.

ORA-06032: NETDNT: connect failed, access control data rejected

ORA-06032: NETDNT: connect failed, access control data rejected

Cause: Host string contains invalid username or password

Action: Retry with correct username or password

ORA-06031: NETDNT: connect failed, unrecognized object name

ORA-06031: NETDNT: connect failed, unrecognized object name

Cause: Host string contains reference to object (which doesn t exist): d:lamp;lt;lamp;nbsp;nodelamp;gt;-lamp;lt;lamp;nbsp;objlamp;gt; =lamp;gt; object is ORDNlamp;lt;lamp;nbsp;objlamp;gt;; when lamp;lt;lamp;nbsp;nodelamp;gt; is VMS, the object is ORDNlamp;lt;lamp;nbsp;objlamp;gt;.COM when lamp;lt;lamp;nbsp;nodelamp;gt; is UNIX, the object is ORDNlamp;lt;lamp;nbsp;objlamp;gt; d:lamp;lt;lamp;nbsp;nodelamp;gt;:: task=lamp;lt;lamp;nbsp;objlamp;gt; =lamp;gt; object is lamp;lt;lamp;nbsp;objlamp;gt;; when lamp;lt;lamp;nbsp;nodelamp;gt; is VMS, the object is lamp;lt;lamp;nbsp;objlamp;gt;.COM when lamp;lt;lamp;nbsp;nodelamp;gt; is UNIX, the object is lamp;lt;lamp;nbsp;objlamp;gt;

Action: Retry with correct object name or create the required object on host node

ORA-06030: NETDNT: connect failed, unrecognized node name

ORA-06030: NETDNT: connect failed, unrecognized node name

Cause: Node name specified in host string is unknown (probably misspelled)

Action: Retry with correct node name

ORA-06029: NETASY: port assignment failure

ORA-06029: NETASY: port assignment failure

Cause: Async driver unable to assign port to channel (should never happen(

Action: Contact your customer support representative.

ORA-06028: NETASY: unable to intialise for logging

ORA-06028: NETASY: unable to intialise for logging

Cause: Async driver unable to initialise for logging I or O

Action: Contact your customer support representative.

ORA-06027: NETASY: channel close failure

ORA-06027: NETASY: channel close failure

Cause: Async driver unable to close channel

Action: Check log file for OS-specific error code

ORA-06026: NETASY: port close failure

ORA-06026: NETASY: port close failure

Cause: Async driver unable to close port

Action: Check log file for OS-specific error code

ORA-06025: NETASY: Configuration error

ORA-06025: NETASY: Configuration error

Cause: Async driver genned for server-only, but client service requested

Action: Contact your customer support representative.

ORA-06024: NETASY: VTM error

ORA-06024: NETASY: VTM error

Cause: Virtual Terminal Manager unable to read or write to port

Action: Check log file for OS-specific error code

ORA-06023: NETASY: port open failure

ORA-06023: NETASY: port open failure

Cause: Async driver unable to open port

Action: Check log file for OS-specific error code

ORA-06022: NETASY: channel open failure

ORA-06022: NETASY: channel open failure

Cause: no free channel (should never happen(

Action: Contact your customer support representative.

ORA-06021: NETASY: connect failed

ORA-06021: NETASY: connect failed

Cause: Async driver unable to establish connection with partner

Action: Check log file for OS-specific error code

ORA-06020: NETASY: initialisation failure

ORA-06020: NETASY: initialisation failure

Cause: Async driver unable to complete initialisation

Action: Check log file for OS-specific error code

ORA-06019: NETASY: invalid login (connect) string

ORA-06019: NETASY: invalid login (connect) string

Cause: Syntax error in login string.

Action: Resubmit with correct string.

ORA-06018: NETASY: message send failure

ORA-06018: NETASY: message send failure

Cause: Async driver gets I or O error while doing network write operation

Action: Check log file for OS-specific error code and contact your customer support representative.

ORA-06017: NETASY: message receive failure

ORA-06017: NETASY: message receive failure

Cause: Async driver gets I or O error while doing network read operation

Action: Check log file for OS-specific error code and contact your customer support representative.

ORA-06011: NETASY: dialogue too long

ORA-06011: NETASY: dialogue too long

Cause: One of two: 1. Dialogue contains more than 24 exchange blocks 2. Dialogue send string exceeds 84 bytes in length

Action: Simplify dialogue or split into two and link with more command

ORA-06010: NETASY: dialogue file too long

ORA-06010: NETASY: dialogue file too long

Cause: Dialogue file exceeds 768 bytes in length

Action: Simplify dialogue (e.g. remove comments, redundant white space), or split into two and link with more command

ORA-06009: NETASY: dialogue filename too long

ORA-06009: NETASY: dialogue filename too long

Cause: Full file spec for dialogue file exceeds 64 bytes

Action: Amend connect string accordingly

ORA-06007: NETASY: bad dialogue format

ORA-06007: NETASY: bad dialogue format

Cause: Dialogue file contains syntax error

Action: Correct the dialogue file

ORA-06006: NETASY: dialogue execute failure

ORA-06006: NETASY: dialogue execute failure

Cause: Expected response never received

Action: None

ORA-06005: NETASY: dialogue file read failure

ORA-06005: NETASY: dialogue file read failure

Cause: Autologin unable to read dialogue file

Action: Check log file for OS-specific error code

ORA-06004: NETASY: dialogue file open failure

ORA-06004: NETASY: dialogue file open failure

Cause: Autologin unable to open dialogue file

Action: Check connect string for accuracy or typos

ORA-06003: NETASY: port write failure

ORA-06003: NETASY: port write failure

Cause: Autologin unable to write to port

Action: Check log file for OS-specific error code

ORA-06002: NETASY: port read failure

ORA-06002: NETASY: port read failure

Cause: Autologin unable to read from port

Action: Check log file for OS-specific error code

ORA-06001: NETASY: port set-up failure

ORA-06001: NETASY: port set-up failure

Cause: Autologin unable to change port attributes

Action: Check log file for OS-specific error code

ORA-06000: NETASY: port open failure

ORA-06000: NETASY: port open failure

Cause: Autologin unable to open port

Action: Check log file for OS-specific error code

ORA-04941: required operating system patch needs to be applied

ORA-04941: required operating system patch needs to be applied

Cause: The operating system could not return the start time of a process.

Action: Check that the operating system kernel has been patched to return process start time. Apply the required operating system patch and restart the instance.

ORA-04940: unsupported optimization of Oracle binary, check alert log for more info

ORA-04940: unsupported optimization of Oracle binary, check alert log for more info

Cause: ORACLE binary has been optimized with unsupported options or a required option has not been used.

Action: Check the documentation for a list of supported and required flags for the optimizing utility that you used to optimize ORACLE. Shutdown the instance, optimize ORACLE again with supported combination of options and restart the instance.

ORA-04935: unable to get or convert SCN recovery lock

ORA-04935: unable to get or convert SCN recovery lock

Cause: A process has timed out trying to get or convert the SCN recovery lock. Another process probably has the lock in EX or SHR mode, but is not releasing it.

Action: Contact Oracle Support.

ORA-04934: unable to obtain the current sequence number

ORA-04934: unable to obtain the current sequence number

Cause: A call to the SSN failed to return its current value. Either there are many errors occurring on the MC hardware, or the sequence number has become invalid and cannot be validated.

Action: Verify that the MC hardware is functioning properly. If it is, contact Oracle Support.

ORA-04933: initial service identifier is non-zero

ORA-04933: initial service identifier is non-zero

Cause: A valid service identifier existed before the sequence number service was opened.

Action: Verify that the instance is completely shut down.

ORA-04932: increment or adjust of sequence number failed

ORA-04932: increment or adjust of sequence number failed

Cause: A call to the SSN failed to increment the sequence number.

Action: Verify that the MC hardware is functioning properly. If it is not, contact Digital s customer support organization. If it is, contact Oracle support.

ORA-04931: unable to set initial sequence number value

ORA-04931: unable to set initial sequence number value

Cause: A call to the SSN failed to set the sequence number to its initial value, possibly caused by an MC hardware problem.

Action: Verify that the MC hardware is functioning properly. If it is not, contact Digital s customer support organization. If it is, contact Oracle support.