Oracle 11g Error Codes and Solution Suggestions from ORA-04900 to ORA-06100
- ORA-04930: open sequence number failed or initial state is valid
- Cause: Either Shared Sequence Number OS component was not installed properly, or an MC hardware failure may have occurred or a previous instance was not shut down properly.
- Action: Verify that there are no background or foreground Oracle processes from a previous instance on this node using the OS command ps -ef|grep <instance_name>. Verify that there are no shared memory segments belonging to the user which owns the Oracle installation by isuing the ipcs -b OS command. If there are shared memory segments or processes still on the system, use svrmgrl to shutdown the instance with the abort option. If the instance is not up, verify that the cluster software and/or the hardware is installed and working. Log in as superuser and issue the cnxshow command. Are all of the nodes in the cluster listed? Are they members of the cluster? Is the communications between nodes okay? If the answer to any of these questions is false, contact Digital’s customer support organization.
- 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.
- 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-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-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-04935: unable to get/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-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-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-06000: NETASY: port open failure
- Cause: Autologin unable to open port
- Action: Check log file for OS-specific error code
- ORA-06001: NETASY: port set-up failure
- Cause: Autologin unable to change port attributes
- Action: Check log file for OS-specific error code
- ORA-06002: NETASY: port read failure
- Cause: Autologin unable to read from port
- Action: Check log file for OS-specific error code
- ORA-06003: NETASY: port write failure
- Cause: Autologin unable to write to port
- Action: Check log file for OS-specific error code
- ORA-06004: NETASY: dialogue file open failure
- Cause: Autologin unable to open dialogue file
- Action: Check connect string for accuracy/typos
- ORA-06005: NETASY: dialogue file read failure
- Cause: Autologin unable to read dialogue file
- Action: Check log file for OS-specific error code
- ORA-06006: NETASY: dialogue execute failure
- Cause: Expected response never received
- Action: None
- ORA-06007: NETASY: bad dialogue format
- Cause: Dialogue file contains syntax error
- Action: Correct the dialogue file
- ORA-06009: NETASY: dialogue filename too long
- Cause: Full file spec for dialogue file exceeds 64 bytes
- Action: Amend connect string accordingly
- 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-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-06017: NETASY: message receive failure
- Cause: Async driver gets I/O error while doing network read operation
- Action: Check log file for OS-specific error code and contact your customer support representative.
- ORA-06018: NETASY: message send failure
- Cause: Async driver gets I/O error while doing network write operation
- Action: Check log file for OS-specific error code and contact your customer support representative.
- ORA-06019: NETASY: invalid login (connect) string
- Cause: Syntax error in login string.
- Action: Resubmit with correct string.
- ORA-06020: NETASY: initialisation failure
- Cause: Async driver unable to complete initialisation
- Action: Check log file for OS-specific error code
- ORA-06021: NETASY: connect failed
- Cause: Async driver unable to establish connection with partner
- Action: Check log file for OS-specific error code
- ORA-06022: NETASY: channel open failure
- Cause: no free channel [should never happen]
- Action: Contact your customer support representative.
- ORA-06023: NETASY: port open failure
- Cause: Async driver unable to open port
- Action: Check log file for OS-specific error code
- ORA-06024: NETASY: VTM error
- Cause: Virtual Terminal Manager unable to read/write to port
- Action: Check log file for OS-specific error code
- ORA-06025: NETASY: Configuration error
- Cause: Async driver genned for server-only, but client service requested
- Action: Contact your customer support representative.
- ORA-06026: NETASY: port close failure
- Cause: Async driver unable to close port
- Action: Check log file for OS-specific error code
- ORA-06027: NETASY: channel close failure
- Cause: Async driver unable to close channel
- Action: Check log file for OS-specific error code
- ORA-06028: NETASY: unable to intialise for logging
- Cause: Async driver unable to initialise for logging I/O
- Action: Contact your customer support representative.
- 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-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-06031: NETDNT: connect failed, unrecognized object name
- Cause: Host string contains reference to object (which doesn’t exist): @d:<node>-<obj> => object is ORDN<obj>; when <node> is VMS, the object is ORDN<obj>.COM when <node> is UNIX, the object is ORDN<obj> @d:<node>::”task=<obj>” => object is <obj>; when <node> is VMS, the object is <obj>.COM when <node> is UNIX, the object is <obj>
- Action: Retry with correct object name or create the required object on host node
- ORA-06032: NETDNT: connect failed, access control data rejected
- Cause: Host string contains invalid username/password
- Action: Retry with correct username/password
- ORA-06033: NETDNT: connect failed, partner rejected connection
- Cause: Connection with partner was made but was rejected.
- Action: Contact your network administrator.
- 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/node is under stress – in this case a retry often works.
- 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-06037: NETDNT: connect failed, node unreachable
- Cause: Host node is down.
- Action: Contact your network administrator.
- ORA-06039: NETDNT: connect failed
- Cause: Connect failed for unexpected reason (see OSD error).
- Action: Contact your customer support representative.
- ORA-06040: NETDNT: invalid login (connect) string
- Cause: Syntax error in login string.
- Action: Resubmit with correct string.
- ORA-06041: NETDNT: disconnect failed
- Cause: Driver gets error while doing network close operation
- Action: Contact your customer support representative.
- ORA-06042: NETDNT: message receive failure
- Cause: Driver gets I/O error while doing network read operation
- Action: Contact your customer support representative.
- ORA-06043: NETDNT: message send failure
- Cause: Driver gets I/O error while doing network write operation
- Action: Contact your customer support representative.
- ORA-06044: NETDNT: connect failed, byte count quota exceeded
- Cause: Connect failed because of insufficient byte count quota.
- Action: Increase byte count quota.