Oracle8 Error Messages Release 8.0.4 A58312-01 |
Library | Product | Contents | Index

## 12530-12629: NS (Session) Error Messages

##### ORA-12531: TNS:cannot allocate memory

Cause: Sufficient memory could not be allocated to perform the desired activity.

Action: Either free some resource for TNS, or add more memory to the machine. For further details, turn on tracing and reexecute the operation.

##### ORA-12532: TNS:invalid argument

Cause: An internal function received an invalid parameter.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.

##### ORA-12533: TNS:illegal ADDRESS parameters

Cause: An illegal set of protocol adapter parameters was specified. In some cases, this error is returned when a connection cannot be made to the protocol transport.

Action: Verify that the destination can be reached using the specified protocol. Check the parameters within the ADDRESS section of TNSNAMES.ORA. Legal ADDRESS parameter formats may be found in the Oracle operating system specific documentation for your platform. Protocols that resolve names at the transport layer (such as DECnet object names) are vulnerable to this error if not properly configured or names are misspelled.

##### ORA-12534: TNS:operation not supported

Cause: An internal function received a request to perform an operation that is not supported (on this machine).

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.

##### ORA-12535: TNS:operation timed out

Cause: The requested connection could not be completed within the timeout period specified by the CONNECT_TIMEOUT parameter in listener.ora. This error arises from the tnslsnr.

Action: Either reconfigure CONNECT_TIMEOUT to be 0, which means wait indefinitely, or reconfigure CONNECT_TIMEOUT to be some higher value. Or, if the timeout is unacceptably long, turn on tracing for further information.

##### ORA-12536: TNS:operation would block

Cause: An internal operation did not commence because to do so would block the current process and the user has requested that operations be non-blocking.

Action: None needed; this is an information message.

##### ORA-12537: TNS:connection closed

Cause: "End of file" condition has been reached; partner has disconnected.

Action: None needed; this is an information message.

##### ORA-12538: TNS:no such protocol adapter

Cause: The protocol adapter requested (by way of the "(PROTOCOL=..)" keyword-value pair in a TNS address) is unknown. If the supplied address is typographically correct then the protocol adaptor is not installed.

Action: Install the protocol adapter or correct typographical error, as appropriate. Note: if the supplied address was derived from resolving the service name, check the address in the appropriate file (TNSNAMES.ORA, LISTENER.ORA or TNSNET.ORA).

##### ORA-12539: TNS:buffer over- or under-flow

Cause: Buffer too small for incoming data or too large for outgoing data.

Action: This restriction (which is associated with CONNECT DATA) is not normally visible to the user. For further details, turn on tracing and reexecute the operation; contact Worldwide Customer Support.

##### ORA-12540: TNS:internal limit restriction exceeded

Cause: Too many TNS connections open simultaneously.

Action: Wait for connections to close and re-try.

##### ORA-12541: TNS:no listener

Cause: The connection request could not be completed because the listener is not running.

Action: Ensure that the supplied destination address matches one of the addresses used by the listener - compare the TNSNAMES.ORA entry with the appropriate LISTENER.ORA file (or TNSNAV.ORA if the connection is to go by way of an Interchange). Start the listener on the remote machine.

##### ORA-12542: TNS:address already in use

Cause: Specified listener address is already being used.

Action: Start your listener with a unique address.

##### ORA-12543: TNS:destination host unreachable

Cause: Contact can not be made with remote party.

Action: Make sure the network driver is functioning and the network is up.

##### ORA-12544: TNS:contexts have different wait/test functions

Cause: Two protocol adapters have conflicting wait/test functions.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.

##### ORA-12545: Connect failed because target host or object does not exist

Cause: The address specified is not valid, or the program being connected to does not exist.

Action: Ensure the ADDRESS parameters have been entered correctly; the most likely incorrect parameter is the node name. Ensure that the executable for the server exists (perhaps "oracle" is missing.) If the protocol is TCP/IP, edit the TNSNAMES.ORA file to change the host name to a numeric IP address and try again.

##### ORA-12546: TNS:permission denied

Cause: User has insufficient privileges to perform the requested operation.

Action: Acquire necessary privileges and try again.

##### ORA-12547: TNS:lost contact

Cause: Partner has unexpectedly gone away, usually during process start-up.

Action: Investigate partner application for abnormal termination. On an Interchange, this can happen if the machine is overloaded.

##### ORA-12548: TNS:incomplete read or write

Cause: A data send or receive failed.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.

##### ORA-12549: TNS:operating system resource quota exceeded

Cause: The current user has exceeded the allotted resource assigned in the operating system.

Action: Acquire more operating system resource, or perform a different function.

##### ORA-12550: TNS:syntax error

Cause: The supplied connect descriptor contains illegal syntax.

Action: Check the syntax of the connect descriptor in TNSNAMES.ORA.

##### ORA-12551: TNS:missing keyword

Cause: The supplied connect descriptor is missing one or more TNS keywords.

Action: Check the syntax, and ensure all required keywords are present.

##### ORA-12552: TNS:operation was interrupted

Cause: An internal operation was interrupted and could not complete.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.

##### ORA-12554: TNS:current operation is still in progress

Cause: An internal operation is still in progress.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.

##### ORA-12555: TNS:permission denied

Cause: User has insufficient privileges to perform the requested operation.

Action: Acquire necessary privileges and try again.

##### ORA-12556: TNS:no caller

Cause: TNS detected an incoming connect request but there was no caller.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.

##### ORA-12557: TNS:protocol adapter not loadable

Cause: On some platforms (such as OS/2) protocol adapters are loaded at run-time. If the shared library (or DLL) for the protocol adapter is missing or one of its supporting libraries is missing then this error is returned.

Action: For further details, turn on tracin and reexecute the operation. The trace file will include the name of the shared library (or DLL) that could not be loaded.

##### ORA-12558: TNS:protocol adapter not loaded

Cause: On some platforms (such as OS/2) protocol adapters are loaded at run-time. If the shared library (or DLL) for the protocol adapter has not been loaded, then this error is returned.

Action: For further details, turn on tracing and reexecute the operation. The trace file will have the name of the shared library (or DLL) that has not been loaded.

##### ORA-12560: TNS:protocol adapter error

Cause: A generic protocol adapter error occurred.

Action: Check addresses used for proper protocol specification. Before reporting this error, look at the error stack and check for lower level transport errors.For further details, turn on tracing and reexecute the operation. Turn off tracing when the operation is complete.

##### ORA-12561: TNS:unknown error

Cause: A generic protocol error occurred.

Action: For further details, turn on tracing and reexecute the operation.

##### ORA-12562: TNS:bad global handle

Cause: Internal error - bad 'gbh' argument passed to TNS from caller. System may have been linked with old libraries.

Action: Not normally visible to the user, contact Worldwide Customer Support.

##### ORA-12564: TNS:connection refused

Cause: The connect request was denied by the remote user (or TNS software).

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation.

##### ORA-12566: TNS:protocol error

Cause: An unexpected TNS protocol error has occurred.

Action: For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.

##### ORA-12569: TNS:packet checksum failure

Cause: The data received is not the same as the data sent.

Action: Attempt the transaction again. If the error is persistent, turn on tracing and reexecute the operation.

##### ORA-12570: TNS:packet reader failure

Cause: An error occurred during a data receive.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.

##### ORA-12571: TNS:packet writer failure

Cause: An error occurred during a data send.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.

##### ORA-12574: TNS:redirection denied

Cause: The connect request failed because it would have required redirection and the caller has requested no redirections.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.

##### ORA-12582: TNS:invalid operation

Cause: An internal function received an invalid request.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.

##### ORA-12583: TNS:no reader

Cause: A send operation has been requested but partner has already disconnected.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.

##### ORA-12585: TNS:data truncation

Cause: A receive operation has completed with insufficient data to satisfy the user's request.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.

##### ORA-12589: TNS:connection not bequeathable

Cause: An attempt to hand-off a connection from one process to another has failed because the protocol provider does not support it.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.

##### ORA-12590: TNS:no I/O buffer

Cause: An attempt to perform an I/O operation failed because no buffer was available.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.

##### ORA-12591: TNS:event signal failure

Cause: The TNS software is unable to signal an event occurrence.

Action: For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.

##### ORA-12592: TNS:bad packet

Cause: An ill-formed packet has been detected by the TNS software.

Action: For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.

##### ORA-12593: TNS:no registered connection

Cause: An attempt to solicit network event activity has failed because no connections are registered for event notification.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.

##### ORA-12595: TNS:no confirmation

Cause: TNS is unable to get requested confirmation acknowledgment from remote partner.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.

##### ORA-12596: TNS:internal inconsistency

Cause: TNS has detected an internal inconsistency.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Worldwide Customer Support.

##### ORA-12597: TNS:connect descriptor already in use

Cause: Internal error - illegal use of connect descriptor.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.

##### ORA-12598: TNS:banner registration failed

Cause: The registration of a product banner with the Oracle server failed.

Action: This is an error which is not normally visible externally. Enable tracing and attempt to repeat the error. If it occurs again, contact Worldwide Customer Support.

##### ORA-12599: TNS:cryptographic checksum mismatch

Cause: The data received is not the same as the data sent.

Action: Attempt the transaction again. If error persists, check (and correct) the integrity of your physical connection.

##### ORA-12600: TNS: string open failed

Cause: The creation of a string in ORACLE NLS format failed.

Action: This is an internal error, enable tracing and attempt to repeat the error. If it occurs again, contact Worldwide Customer Support.

##### ORA-12601: TNS:information flags check failed

Cause: The TNS information flags set by the process prior to connection negotiation were not present after the negotiation was finished.

Action: This is an internal error. Enable tracing and attempt to repeat the error. If it occurs again, contact Worldwide Customer Support.

##### ORA-12611: TNS:operation is not portable

Cause: Attempted operton is not portable.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.

##### ORA-12612: TNS:connection is busy

Cause: Attempted operation failed because it conflicts with an ongoing action or status of the connection.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.

##### ORA-12615: TNS:preempt error

Cause: A request to service an event failed because no event notification has yet been posted.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.

##### ORA-12616: TNS:no event signals

Cause: The TNS software is unable to enable event signals.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.

##### ORA-12617: TNS:bad `what' type

Cause: The operation failed because the type of data specified is unknown.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.

##### ORA-12618: TNS:versions are incompatible

Cause: The two machines are running incompatible versions of TNS.

Action: Check the version numbers, and upgrade the machine with the smaller one.

##### ORA-12619: TNS:unable to grant requested service

Cause: The connect request failed because requested service could not be provided by the local TNS software.

Action: If appropriate, reexecute with reduced service requirements.

##### ORA-12620: TNS:requested characteristic not available

Cause: The connect request failed because a requested transport characteristic could not be supported by the remote TNS software.

Action: If appropriate, reexecute with reduced requirements.

##### ORA-12622: TNS:event notifications are not homogeneous

Cause: An attempt to register a connection for event notification failed because the event notification type conflicts with existing registrations.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Worldwide Customer Support.

##### ORA-12623: TNS:operation is illegal in this state

Cause: Connection is half-duplex and a full-duplex operation was attempted.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.

##### ORA-12624: TNS:connection is already registered

Cause: An attempt to register a connection for event notification failed because the connection is already registered.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Worldwide Customer Support.

##### ORA-12625: TNS:missing argument

Cause: An operation failed because an argument was missing"

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Worldwide Customer Support.

##### ORA-12626: TNS:bad event type

Cause: An attempt to register a connection for event notification failed because the event type is unknown.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Worldwide Customer Support.

##### ORA-12628: TNS:no event callbacks

Cause: An attempt to register a connection for event notification failed because asynchronous callbacks are not available.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Worldwide Customer Support.

##### ORA-12629: TNS:no event test

Cause: An attempt to register a connection for event notification failed because the ability to test for events is not available.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Worldwide Customer Support.

##### ORA-12611: TNS:operation is not portable

Cause: Attempted operation is not portable.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.

##### ORA-12612: TNS:connection is busy

Cause: Attempted operation failed because it conflicts with an ongoing action or status of the connection.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.

##### ORA-12616: TNS:no event signals

Cause: The TNS software is unable to enable event signals.

Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.

Prev | Top | Next
| Copyright © 1997 Oracle Corporation. All Rights Reserved. |
Library | Product | Contents | Index