Oracle 11g Error Codes and Solution Suggestions from ORA-06300 to ORA-06500
- ORA-06300: IPA: Disconnect failure
- Cause: A fatal error occurred during the disconnect from the server. This was probably caused by inaccessible message queues.
- Action: If there is no message queue, restart the SQL*Net IPA servers using ipactl. Otherwise contact your customer support representative.
- ORA-06301: IPA: Cannot allocate driver context
- Cause: The memory pool is exhausted.
- Action: Check the circumstances and try to allocate less memory in your program or adjust the init parameters in your INIT.ORA file and retry.
- ORA-06302: IPA: Cannot connect to remote host
- Cause: found.
- Action: Check sequentially for the above causes and eliminate the actual
- ORA-06303: IPA: Message send error
- Cause: The SQL*Net IPA driver could not write the message into the message queue.
- Action: Make sure that the message queue exists and is accessible. If necessary rerun ipactl.
- ORA-06304: IPA: Message receive error
- Cause: The SQL*Net IPA driver could not read a message from the message queue.
- Action: Make sure that the message queue exists and is accessible. If necessary rerun ipactl.
- ORA-06305: IPA: Illegal message type
- Cause: The communication between user and ORACLE is out of synchronization. This message should not normally be issued.
- Action: Contact your customer support representative.
- ORA-06306: IPA: Message write length error
- Cause: The IPA driver tried to write a message in the queue that was too big for the queue.
- Action: Contact your customer support representative.
- ORA-06307: IPA: Cannot reset connection
- Cause: A fatal error occurred during the resetting of the connection.
- Action: Contact your customer support representative.
- ORA-06308: IPA: No more connections available
- Cause: You have exhausted all your connections.
- Action: Try again when some of the current users have logged off.
- ORA-06309: IPA: No message queue available
- Cause: The SQL*Net IPA servers have not been started.
- Action: Run ipactl.
- ORA-06310: IPA: Environment variable(s) not set
- Cause: Environment variable(s) not set correctly.
- Action: Check and correct.
- ORA-06311: IPA: Maximum number of servers reached
- Cause: Maximum number of servers reached.
- Action: Shutdown and restart with an increased maximum number of servers. Note that database links consume one server per link. Be sure to start up enough servers to support database links.
- ORA-06312: IPA: Incorrect outgoing service name supplied
- Cause: Incorrect outgoing service name supplied.
- Action: Check and correct the service name.
- ORA-06313: IPA: Shared memory failed to initialise
- Cause: The shared memory has not been set up correctly.
- Action: Contact your system manager.
- ORA-06314: IPA: Event set up failure
- Cause: Fatal interprocess communication error.
- Action: Contact your system manager.
- ORA-06315: IPA: Invalid connect string
- Cause: The connect string is malformed.
- Action: Check and correct.
- ORA-06316: IPA: Invalid database SID
- Cause: The SID is unknown at the remote side.
- Action: Either the database does not exist, is not running, or there are no reserved servers for that SID.
- ORA-06317: IPA: Local maximum number of users exceeded
- Cause: The maximum number of simultaneous users of SQL*Net IPA has been exceeded on the local side.
- Action: Wait for free connections to become available. If the problem persists, contact your system manager.
- ORA-06318: IPA: Local maximum number of connections exceeded
- Cause: The maximum number of simultaneous connections that SQL*Net IPA can handle to different hosts has been exceeded on the local side.
- Action: Wait for free connections to become available. If the problem persists, contact your system manager.
- ORA-06319: IPA: Remote maximum number of users exceeded
- Cause: The maximum number of simultaneous users of SQL*Net IPA has been exceeded on the remote side.
- Action: Wait for free connections to become available. If the problem persists, contact your system manager.
- ORA-06320: IPA: Remote maximum number of connections exceeded
- Cause: The maximum number of simultaneous connections that SQL*Net IPA can handle from different hosts has been exceeded on the remote side.
- Action: Wait for free connections to become available. If the problem persists, contact your system manager.
- ORA-06321: IPA: Cannot reach the remote side
- Cause: There has been a timeout on an attempt to connect to a remote server the reason for which is most likely to be the remote SQL*Net IPA software is not running. An alternative reason could be that the remote initiator service name is incorrect.
- Action: Check and start the remote SQL*Net software. Check that it is started with the correct service names supplied.
- ORA-06322: IPA: Fatal shared memory error
- Cause: An internal error has occurred in the shared memory handling.
- Action: Contact customer support.
- ORA-06323: IPA: Cause event error
- Cause: Fatal interprocess communication error.
- Action: Contact your system manager.
- ORA-06400: NETCMN: No default host string specified
- Cause: There was no default host string specified in the configuration and the user didn’t specify any explicit connect string.
- Action: Either reconfigure the system specifying a default connect string or use an explicit connect string.
- ORA-06401: NETCMN: invalid driver designator
- Cause: The login (connect) string contains an invalid driver designator.
- Action: Correct the string and re-submit.
- ORA-06402: NETCMN: error receiving break message
- Cause: Error occurred while attempting to read a break message.
- Action: Contact your customer support representative.
- ORA-06403: Unable to allocate memory.
- Cause: System unable to allocate needed virtual memory.
- Action: Configure more memory, reduce load, or simply try again.
- ORA-06404: NETCMN: invalid login (connect) string
- Cause: Syntax error in login string.
- Action: Correct string and re-submit.
- ORA-06405: NETCMN: reset protocol error
- Cause: Unable to reset out of break state.
- Action: Contact your customer support representative.
- ORA-06406: NETCMN: error sending break message
- Cause: Error occurred while attempting to send a break message.
- Action: Contact your customer support representative.
- ORA-06407: NETCMN: unable to set up break handling environment
- Cause: Error occurred while attempting to set up asynchronous handlers for in-coming, out-of-band break messages.
- Action: Contact your customer support representative.
- ORA-06408: NETCMN: incorrect message format
- Cause: Message from partner contains bad header.
- Action: Contact your customer support representative.
- ORA-06413: Connection not open.
- Cause: Unable to establish connection.
- Action: Use diagnostic procedures to ascertain exact problem.
- ORA-06416: NETCMN: error on test
- Cause: Error occurred while testing I/O status of the network connection.
- Action: Contact your customer support representative.
- ORA-06419: NETCMN: server can not start oracle
- Cause: The remote 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.
- ORA-06420: NETCMN: SID lookup failure
- Cause: From the remote host’s server: the database SID, specified in the login (connect) string, was not recognized.
- Action: Add the appropriate SID entry to the CONFIG.ORA or oratab file on the remote host (restarting the remote server may be needed).
- ORA-06421: NETCMN: Error detected in the read-in data
- Cause: Error found during recomputation of checksum or CRC.
- Action: Possible hardware failures of communication nodes. Contact system administrator immediately.
- ORA-06422: NETCMN: Error in sending data
- Cause: Unable to transmit data to remote host.
- Action: Try reconnect to remote host, and contact your system administrator.
- ORA-06423: NETCMN: Error in receiving data
- Cause: Unable to receive data from remote host.
- Action: Try reconnect to remote host, and contact your system administrator.
- ORA-06430: ssaio: Seals do not match
- Cause: A function was called with an invalid argument.
- Action: Contact your Oracle Customer Support Representative.
- ORA-06431: ssaio: Invalid Block number
- Cause: The file block number is out of range of the file. The additional information returns the block number.
- Action: Verify that the block number is correct. Run dbfsize and check if the block number is in that range. Contact your Oracle Customer Support Representative.
- ORA-06432: ssaio: Buffer Not Aligned
- Cause: The I/O buffer was not aligned on a 2K boundary.
- Action: Contact your Oracle Customer Support Representative.
- ORA-06433: ssaio: LSEEK error, unable to seek to requested block.
- Cause: The additional information returns the block number
- Action: Look up the additional information returned in your operating system reference manual. Verify that the block number is correct.
- ORA-06434: ssaio: read error, unable to read requested block from database file.
- Cause: The read system call returned an error.
- Action: The additional information indicates the block number. Look up the additional information returned in your operating system manual.
- ORA-06435: ssaio: write error, unable to write requested block to database file.
- Cause: The write system call returned an error.
- Action: The additional information indicates the block number. Look up the additional information returned in your operating system manual.
- ORA-06436: ssaio: asynchronous I/O failed due to incorrect parameters.
- Cause: The Asynchronous I/O system call returned an error.
- Action: The additional information indicates the block number. Look up the additional information returned in your operating system manual.
- ORA-06437: ssaio: the asynchronous write was unable to write to the database file.
- Cause: The Asynchronous I/O system call returned an error.
- Action: The additional information indicates the block number. Look up the additional information returned in your operating system manual.
- ORA-06438: ssaio: the asynchronous read was unable to read from the database file.
- Cause: The Asynchronous I/O system call returned an error.
- Action: The additional information indicates the block number. Look up the additional information returned in your operating system manual.
- ORA-06439: ssaio: the asynchronous write returned incorrect number of bytes
- Cause: This write call may have been truncated. The additional information returns the block number and number of bytes.
- Action: Verify that the block number and the number of bytes written are correct.
- ORA-06440: ssaio: the asynchronous read returned incorrect number of bytes
- Cause: This read call may have been truncated. The additional information returns the block number and number of bytes.
- Action: Verify that the block number and the number of bytes read are correct.
- ORA-06441: ssvwatev: Incorrect parameter passed to function call
- Cause: Either the ORACLE process id, or wait time or event ID is invalid.
- Action: The additional information indicates the process id, time and event id.
- ORA-06442: ssvwatev: Failed with unexpected error number.
- Cause: Some system problems may exists on your system, please check error logs.
- Action: The additional information indicates the error number. Look up the additional information returned in your operating system manual.
- ORA-06443: ssvpstev: Incorrect parameter passed to function call
- Cause: An invalid event ID is passed in to this routine.
- Action: The additional information indicates the event id.
- ORA-06444: ssvpstev: Failed with unexpected error number.
- Cause: Some system problems may exist on your system, please check error logs.
- Action: The additional information indicates the error number. Look up the additional information returned in your operating system manual.
- ORA-06445: ssvpstevrg: Incorrect parameters passed to function call
- Cause: An invalid event id, or the low and high event ID do not exist.
- Action: The additional information indicates the error number. It also contains the event id, low boundary and high boundary.
- ORA-06446: ssvpstevrg: Failed with unexpected error number.
- Cause: Some system problems may exist on your system, please check error logs.
- Action: The additional information indicates the error number. Look up the additional information returned in your operating system manual.
- ORA-06447: ssvpstp: Incorrect parameter passed to function call
- Cause: Invalid oracle process ID is passed in to this routine.
- Action: The additional information indicates the process id.
- ORA-06448: ssvpstp: Failed with unexpected error number.
- Cause: Some system problems may exists on your system, please check error logs.
- Action: The additional information indicates the error number. Look up the additional information returned in your operating system manual.
- ORA-06449: The list IO or the sysvendor is not installed.
- Cause: ORACLE tries to use the sysvendor interface (INIT.ORA parameter use_sysvendor=true) but the UNIX kernel does not have the ORACLE sysvendor interface linked in.
- Action: Set use_sysvendor=false in INIT.ORA, if you don’t want to use this interface or link the UNIX kernel with this interface so that ORACLE can use it.
- ORA-06500: PL/SQL: storage error
- Cause: PL/SQL was unable to allocate additional storage. This message normally appears with an ORA-4030 or ORA-4031 error which gives additional information. Sometimes this error can be caused by runaway programs.
- Action: 1) Ensure there are no issues or bugs in your PL/SQL program which are causing excessive amounts of memory to be used. 2) Programmatically cause unused objects to be freed (e.g. by setting them to NULL). 3) Increase the amount of shared or process memory (as appropriate) available to you.