Oracle 12c R2 Error Codes and Solution Suggestions from ORA-04930 to ORA-06145
- 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.
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.
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.
Cause: A valid service identifier existed before the sequence number service was opened.
Action: Verify that the instance is completely shut down.
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.
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.
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.
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.
Cause: Autologin unable to open port
Action: Check log file for OS-specific error code
Cause: Autologin unable to change port attributes
Action: Check log file for OS-specific error code
Cause: Autologin unable to read from port
Action: Check log file for OS-specific error code
Cause: Autologin unable to write to port
Action: Check log file for OS-specific error code
Cause: Autologin unable to open dialogue file
Action: Check connect string for accuracy/typos
Cause: Autologin unable to read dialogue file
Action: Check log file for OS-specific error code
Cause: Expected response never received
Action: None
Cause: Dialogue file contains syntax error
Action: Correct the dialogue file
Cause: Full file spec for dialogue file exceeds 64 bytes
Action: Amend connect string accordingly
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
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
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.
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.
Cause: Syntax error in login string.
Action: Resubmit with correct string.
Cause: Async driver unable to complete initialisation
Action: Check log file for OS-specific error code
Cause: Async driver unable to establish connection with partner
Action: Check log file for OS-specific error code
Cause: no free channel [should never happen]
Action: Contact your customer support representative.
Cause: Async driver unable to open port
Action: Check log file for OS-specific error code
Cause: Virtual Terminal Manager unable to read/write to port
Action: Check log file for OS-specific error code
Cause: Async driver genned for server-only, but client service requested
Action: Contact your customer support representative.
Cause: Async driver unable to close port
Action: Check log file for OS-specific error code
Cause: Async driver unable to close channel
Action: Check log file for OS-specific error code
Cause: Async driver unable to initialise for logging I/O
Action: Contact your customer support representative.
Cause: Async driver unable to assign port to channel [should never happen]
Action: Contact your customer support representative.
Cause: Node name specified in host string is unknown (probably misspelled)
Action: Retry with correct node name
Cause: Host string contains reference to object (which doesn’t exist): @d:node–obj => object is ORDNobj; when node is VMS, the object is ORDNobj.COM when node is UNIX, the object is ORDNobj@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
Cause: Host string contains invalid username/password
Action: Retry with correct username/password
Cause: Connection with partner was made but was rejected.
Action: Contact your network administrator.
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.
Cause: Insufficient system resources are available to complete the connection; for example, all DECnet channels are in use.
Action: Contact your network administrator.
- ORA-06036: NETDNT: connect failed, no response from object
- ORA-06037: NETDNT: connect failed, node unreachable
Cause: Host node is down.
Action: Contact your network administrator.
Cause: Connect failed for unexpected reason (see OSD error).
Action: Contact your customer support representative.
Cause: Syntax error in login string.
Action: Resubmit with correct string.
Cause: Driver gets error while doing network close operation
Action: Contact your customer support representative.
Cause: Driver gets I/O error while doing network read operation
Action: Contact your customer support representative.
Cause: Driver gets I/O error while doing network write operation
Action: Contact your customer support representative.
Cause: Connect failed because of insufficient byte count quota.
Action: Increase byte count quota.
Cause: Insufficient dynamic memory available for connection context area.
Action: Contact your customer support representative.
Cause: Host name specified in the login (connect) string is unknown.
Action: Check spelling; make sure name is in the TCP/IP HOST file.
Cause: Process open file quota probably exceeded.
Action: Contact your customer support representative.
Cause: No entry in SERVICES file for ORACLE server.
Action: Add (“orasrv”) entry to the TCP/IP SERVICES file.
Cause: Connection attempt to remote host has failed. Probably means that the SQL*Net TCP/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/IP server process on the remote host.
Cause: I/O error occurred while attempting network read operation.
Action: Contact your customer support representative.
Cause: I/O error occurred while attempting network write operation.
Action: Contact your customer support representative.
Cause: Error occurred while closing a socket.
Action: Contact your customer support representative.
Cause: The buffer size specified in the login string exceeds the allowed maximum (of 4096).
Action: Re-submit with valid buffer size.
Cause: The maximum no. of concurrently open connections has been reached.
Action: Exit an application with an open connection which is no longer required.
Cause: From the remote host’s SQL*Net TCP/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/IP server).
Cause: The host’s SQL*Net TCP/IP server was unable to create the necessary logicals required by the ORACLE server process. See the SQL*Net TCP/IP server log file for more details.
Action: Contact your system administrator.
Cause: The host’s SQL*Net TCP/IP server was unable to create the ORACLE server process. See the SQL*Net TCP/IP server log file for more details.
Action: Contact your system administrator.
Cause: The host’s SQL*Net TCP/IP server was unable to create the ORACLE server process because of quota depletion.
Action: Increase quota allocations to the SQL*Net TCP/IP server process.
Cause: The ORACLE server process was started but failed to complete its initialization.
Action: Contact your customer support representative.
Cause: The host’s SQL*Net TCP/IP server was unable to recognize this connection request. See the SQL*Net TCP/IP server log file for more details.
Action: Contact your customer support representative.
Cause: The TCP/IP network driver is not loaded.
Action: Check that the TCP/IP driver is loaded correctly.
Cause: The host’s SQL*Net TCP/IP server was unable to test the accessibility of the SID mapping file (specified in CONFIG.ORA) associated with this connection request. See the SQL*Net TCP/IP server log file for more details.
Action: Contact your customer support representative.
Cause: The host’s SQL*Net TCP/IP server was unable to set up the appropriate environment to service this connection request. See the SQL*Net TCP/IP server log file for more details.
Action: Contact your customer support representative.
Cause: The host’s SQL*Net TCP/IP server was unable to set the socket KEEPLIVE option. See the SQL*Net TCP/IP server log file for more details.
Action: Contact your customer support representative.
Cause: The ORACLE server process was started but failed to respond after N secs.
Action: For heavily loaded systems this is not an uncommon occurrence. Increase the value of N (the default is 30) by placing the following entry in the CONFIG.ORA file: SQLNET ORASRV_WAIT = <no. of secs> which will come into effect the next time the SQL*Net TCP/IP server is started.
Cause: The ORACLE server process was started but exited unexpectedly. Possible causes: 1. Insufficient quotas to run ORASRV 2. ORACLE is not installed See the ORASRV output file for more details; the file will be in the ORA_SQLNET directory and will have a name of the form: ORA_SRVTnn_SID.OUT
Action: If appropriate action is not obvious from the ORASRV output file then contact your customer support representative.
Cause: The ORACLE server process was started but was unable to open the socket passed to it by TCPSRV.
Action: Contact your customer support representative.
Cause: The host’s SQL*Net TCP/IP server could not establish a PROXY LOGIN connection because the client username is unknown (to the host OS).
Action: Create new user account on host.
Cause: The host’s SQL*Net TCP/IP server was unable to create a mailbox (needed for IPC communication with the ORACLE server process). See the SQL*Net TCP/IP server log file for more details.
Action: Contact your customer support representative.
Cause: The host’s SQL*Net TCP/IP server was unable to transfer the network communication handle to the ORACLE server process. See the SQL*Net TCP/IP server log file for more details.
Action: Contact your customer support representative.
Cause: The host’s SQL*Net TCP/IP server rejected this connection request because the client node does not have access privilege – as determined by the contents of the Valid Node Table (VNT), a component of the host’s CONFIG.ORA.
Action: To grant access, add appropriate entry to the host’s VNT.
Cause: The host’s SQL*Net TCP/IP server rejected this connection request because the client user(name) does not have access privilege – as determined by the contents of the Username Mapping Table (UMT), a component of the host’s CONFIG.ORA.
Action: To grant access, add appropriate entry to the host’s UMT.
Cause: The host SQL*Net TCP/IP server rejected this connection request because the client password did not match the host password.
Action: To grant access, get passwords in sync.
Cause: The host’s SQL*Net TCP/IP server could not find the SID mapping file (specified in CONFIG.ORA) associated with this connection request.
Action: Check CONFIG.ORA for spelling; make correct entry.
Cause: The host’s SQL*Net TCP/IP server did not have READ/ EXECUTE permission for the SID mapping file (specified in CONFIG.ORA) associated with this connection request.
Action: Change protection on SID mapping file.
Cause: The host’s SQL*Net TCP/IP server rejected this connection request because it is in the process of stopping.
Action: Re-start SQL*Net TCP/IP server.
Cause: Network I/O failure occurred while communicating with the host’s SQL*Net TCP/IP server. See the SQL*Net TCP/IP server log file for more details.
Action: Contact your customer support representative.
Cause: Network I/O failure occurred while communicating with the host’s SQL*Net TCP/IP server. See the SQL*Net TCP/IP server log file for more details.
Action: Contact your customer support representative.
Cause: Network I/O failure occurred while communicating with the host’s SQL*Net TCP/IP server. See the SQL*Net TCP/IP server log file for more details.
Action: Contact your customer support representative.
Cause: A proxy login connect attempt failed because the client username has no counterpart on the host.
Action: n/a
Cause: A proxy login connect attempt failed because the SQL*Net TCP/IP server had insufficient privileges to access the proxy account.
Action: Change account protection; change server privilges.
Cause: A proxy login connect attempt failed because the SQL*Net TCP/IP server was unable to access the proxy account. See the SQL*Net TCP/IP server log file for more details.
Action: Contact your customer support representative.
Cause: The connect failed because the maximum conncurrent connections supported by the host’s SQL*Net TCP/IP server has already been reached.
Action: Wait for a short period and re-try.
Cause: The database administrator on the host has varied the SID offline.
Action: Wait for it to be varied back on-line.
Cause: The host’s SQL*Net TCP/IP server was unable to start the ORACLE server process because the ORACLE protected images were not installed.
Action: Install the images.