Oracle 12c R2 Error Codes and Solution Suggestions from ORA-06600 to ORA-06800
- ORA-06600: LU6.2 Driver: SNA software is not loaded
Cause: The SNA software is not running.
Action: Start the SNA software and try again.
Cause: The database string in the connect was invalid.
Action: Provide a valid database string, as defined in documentation.
Cause: Context area failure.
Action: Contact your local service representative.
Cause: Operating system refused request for memory.
Action: Contact you local service representative.
Cause: Allocate system call failed.
Action: Ensure that the SNA software is running and that sessions are free. If this is the case, then check your SNA configuration data for errors. You may have entered an incorrect parameter.
Cause: SNA software switched from send to receive unexpectedly.
Action: Check the SNA configuration data, particularly parameters associated with a session.
Cause: A parameter in an SNA call returned an unexpected value.
Action: Attempt to reproduce problem, debug and record the value of the ‘what’ data parameter at the time of error. Then contact your service representative.
Cause: A reset was issued whilst in send state.
Action: Check the SNA LOG data, if relevent, for further information.
Cause: A reset was received from the partner whilst in receive state. This may be because the partner deallocated.
Action: Check the SNA LOG data, if relevent, for further information.
Cause: LU6.2 driver was unable to deallocate gracefully.
Action: Check the reason for deallocation. Consult the SNA LOG data.
- ORA-06611: LU6.2 Driver: Request to send error
- ORA-06612: LU6.2 Driver: Send data error
- ORA-06613: LU6.2 Driver: Receive and wait error
- ORA-06614: LU6.2 Driver: Receive Immediate error
- ORA-06615: LU6.2 Driver: Send error
- ORA-06616: LU6.2 Driver: Attach to LU failed
Cause: The SQL*Net LU6.2 driver was unable to attach to the LU specified in the connect string, or was unable to attach to the default LU.
Action: Check that the LU name specified in the connect string, or the default LU name if no LU was specified, is correctly configured and operational.
- ORA-06617: LU6.2 Driver: Attach to PU failed
- ORA-06618: LU6.2 Driver: Activation of subnetwork failed
- ORA-06619: LU6.2 Driver: Unable to activate remote partner
- ORA-06620: LU6.2 Driver: Invalid remote partner
- ORA-06621: LU6.2 Driver: Allocation error
- ORA-06622: LU6.2 Driver: Unable to attach to SNA
Cause: The SQL*Net LU6.2 driver could not attach to the SNA software on your machine. The most likely cause is that the SNA software is not operational.
Action: Check the status of the SNA software, ensure that it is operational and then try again.
Cause: TLI received a message with an unrecognizable message type.
Action: Contact your customer support representative.
Cause: TLI sent a message that was apparently successful, but the number of bytes transmitted did not match the number of bytes supplied to the driver.
Action: Contact your customer support representative.
Cause: TLI could not allocate heap space for the context area.
Action: Contact your customer support representative.
Cause: TLI failed to send a break message across the connection.
Action: Contact your customer support representative.
Cause: TLI failed to receive an expected break message.
Action: Contact your customer support representative.
Cause: TLI could not find your remote host information.
Action: Make sure you specified the hostname correctly on the command line. (Also, check your capitalization and spelling.)
Cause: TLI could not find service information for the specified service name.
Action: If you specified the service name on the command line or with the environment variable TLI_SERVER, make sure you specified it correctly. If the service name is not in the SERVICES file for your protocol, ask your system adminstrator to add it.
Cause: TLI failed to establish the connection to a SQL*Net TCP/IP server due to an error encountered by the remote server, which has supplied a string describing the remote error.
Action: See the SQL*Net TCP/IP User’s Guide section “orasrv Messages” for the specific cause and action.
Cause: TLI encountered an error receiving a message from the communication channel.
Action: Contact your customer support representative.
Cause: TLI encountered an error sending a message across the communication channel.
Action: Contact your customer support representative.
Cause: TLI failed to send a break message while handling an interrupt signal from the user.
Action: Contact your customer support representative.
Cause: TLI failed to assign a network address to the communication channel.
Action: Contact your customer support representative.
Cause: TLI failed to accept a connection request from the client.
Action: Contact your customer support representative.
Cause: TLI failed to connect the client to the remote server. The network line to the remote host may be down.
Action: Use other network login programs to make sure that the remote host is accessible.
Cause: The database SID supplied in the database login string was not recognized by the remote host.
Action: Ask your system administrator to add the appropriate SID entry to oratab on the remote host.
Cause: The remote TLI server received an undefined request.
Action: Contact your customer support representative.
Cause: The remote TLI server rejected the connection request, and the client was unable to retrieve an error code or message.
Action: Contact your customer support representative.
Cause: TLI failed to open the Streams clone device associated with the transport provider.
Action: Contact your customer support representative.
Cause: TLI cannot allocate space for the client’s connection information.
Action: Contact your customer support representative.
Cause: TLI cannot allocate space for the client’s disconnection information.
Action: Contact your customer support representative.
Cause: TLI failed to receive an expected disconnection message during connection release.
Action: Contact your customer support representative.
Cause: TLI failed to connect the client to the remote server.
Action: Check that the remote TLI server is running.
Cause: TLI failed to properly close a connection after an error was received.
Action: Contact your customer support representative.
Cause: TLI timed out while attempting to connect to the remote TLI server.
Action: Check that the remote TLI server is running with the status utility for the transport provider you are using. If it is not, ask your system adminstrator to start it.
Cause: TLI could not establish a connection to the remote TLI server.
Action: Check that the remote TLI server is running with the status utility for the transport provider you are using.
Cause: The TLI server failed to open the Streams device associated with the transport provider.
Action: Contact your customer support representative.
Cause: The TLI server cannot allocate space for its requested network address.
Action: Contact your customer support representative.
Cause: The TLI server cannot allocate space for its actual network address.
Action: Contact your customer support representative.
Cause: The TLI server failed to assign the correct network address on which to listen for connections.
Action: Contact your customer support representative.
Cause: The network address on which the TLI server awaits connection requests is in use, possibly because the server is already running.
Action: Ensure that the TLI server is not already running. If it is not running and this error message recurs, contact your customer support representative.
Cause: TLI cannot allocate space for the TLI server’s connection information.
Action: Contact your customer support representative.
Cause: The TLI server encountered an error while listening for connection requests.
Action: Contact your customer support representative.
Cause: TLI cannot allocate space for the TLI server’s disconnection information.
Action: Contact your customer support representative.
Cause: The requested TLI server command must be issued from the same host on which the server is running.
Action: Log in to the remote host and try again.
Cause: The ORACLE process started by the TLI server was unable to synchronize its inherited connection.
Action: Contact your customer support representative.
Cause: The osn check server address failed. The bound server address was not the same as the requested binding address.
Action: Contact your customer support representative.
Cause: A call to sigaction() returned with a system error.
Action: Contact your customer support representative.
Cause: For SVR4, the netdir_getbyname() call failed for some unknown reason.
Action: Contact your custumer service representative.
Cause: The name of the remote host to connect to was not specified, and the name of the local host cannot be retrieved from the HOSTS file.
Action: Contact your system administrator.
Cause: The TLI server was unable to close a connection after passing it to an ORACLE process.
Action: Contact your customer support representative.
Cause: The TLI server could not open the file used to define the locations of remotely accessible databases.
Action: Ask your system administrator to check that the file exists and has the correct permissions.
Cause: The TLI server received an invalid command.
Action: Contact your customer support representative.
Cause: TLI was not able to retreive an expected disconnect message while closing the communication channel.
Action: Contact your customer support representative.
Cause: TLI encountered an error sending a disconnect message closing the communication channel.
Action: Contact your customer support representative.
Cause: TLI encountered an error receiving an expected disconnect message while closing the communication channel.
Action: Contact your customer support representative.
Cause: TLI encountered an error sending a disconnect message closing the communication channel.
Action: Contact your customer support representative.
Cause: TLI was not able to retreive an expected disconnect message while closing the communication channel.
Action: Contact your customer support representative.
Cause: TLI encountered an error awaiting a disconnect message while closing the communication channel.
Action: Contact your customer support representative.
Cause: TLI failed to close the communication channel after receiving a disconnect message.
Action: Contact your customer support representative.
Cause: TLI cannot allocate space for disconnection information while closing the communication channel.
Action: Contact your customer support representative.
Cause: TLI encountered an error while sending its version information during connection establishment.
Action: Contact your customer support representative.
Cause: TLI encountered an error while awaiting the expected version information during connection establishment.
Action: Contact your customer support representative.
Cause: TLI encountered an error while sending a command message during connection establishment.
Action: Contact your customer support representative.
Cause: TLI encountered an error while awaiting the expected command message during connection establishment.
Action: Contact your customer support representative.
Cause: TLI encountered an error while sending break-mode message during connection establishment.
Action: Contact your customer support representative.
Cause: TLI encountered an error while awaiting the expected break-mode message during connection establishment.
Action: Contact your customer support representative.
Cause: TLI encountered an error while sending the connection parameters during connection establishment.
Action: Contact your customer support representative.
Cause: TLI encountered an error while awaiting the expected connection parameter message during connection establishment.
Action: Contact your customer support representative.
Cause: TLI encountered an error while sending the completion status message during connection establishment.
Action: Contact your customer support representative.
Cause: TLI encountered an error while awaiting the expected completion status message during connection establishment.
Action: Contact your customer support representative.
Cause: TLI encountered an error while awaiting an expected error message during connection establishment.
Action: Contact your customer support representative.
Cause: TLI encountered an error while awaiting the expected negotiation message during connection establishment.
Action: Contact your customer support representative.
Cause: TLI was unable to poll the communication channel for possible incoming messages.
Action: Contact your customer support representative.
Cause: TLI received an unexpected event while polling the communication channel for possible incoming messages.
Action: Contact your customer support representative.
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.
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.
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.
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.