Oracle Error Messages

TNS-00514: Contexts have different wait or test functions

TNS-00514: Contexts have different wait or test functions

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

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

TNS-00513: Destination host unreachable

TNS-00513: Destination host unreachable

Cause: Contact cannot be made with remote party.

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

TNS-00512: Address already in use

TNS-00512: Address already in use

Cause: Specified listener address is already being used.

Action: Start your listener with an unused address.

TNS-00511: No listener

TNS-00511: No listener

Cause: The connect request could not be completed because no application is listening on the address specified, or the application is unable to service the connect request in a sufficiently timely manner.

Action: Ensure that the supplied destination address matches one of the addresses used by the listener - compare the TNSNAMES.ORA entry with 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.

TNS-00510: Internal limit restriction exceeded

TNS-00510: Internal limit restriction exceeded

Cause: Too many files or sockets open simultaneously (or some other resource has been depleted).

Action: For further details, trace the operation for protocol details.

TNS-00509: Buffer overflow

TNS-00509: Buffer overflow

Cause: Too much data for buffer.

Action: Reexecute with larger receive buffer or smaller send buffer.

TNS-00508: No such protocol adapter

TNS-00508: No such protocol adapter

Cause: The protocol adapter requested for this connection does not exist.

Action: Install the protocol adapter or use one that is available. Be sure that the correct protocols are listed in the configuration files.

TNS-00507: Connection closed

TNS-00507: Connection closed

Cause: Normal end of file condition has been reached; partner has disconnected.

Action: None needed; this is an information message.

TNS-00506: Operation would block

TNS-00506: 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.

TNS-00505: Operation timed out

TNS-00505: Operation timed out

Cause: The requested operation could not be completed within the timeout period.

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

TNS-00504: Operation not supported

TNS-00504: 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 Oracle Customer Support.

TNS-00503: Illegal ADDRESS parameters

TNS-00503: Illegal ADDRESS parameters

Cause: An illegal set of protocol adapter parameters was specified.

Action: Check the parameters within the ADDRESS section of the TNSNAMES.ORA file. It may be helpful to turn on tracing and look at the addresses specified in the trace file, checking for spelling or other errors. Be sure to turn tracing off when the trace is complete.

TNS-00502: Invalid argument

TNS-00502: 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 Oracle Customer Support.

TNS-00501: Cannot allocate memory

TNS-00501: 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.

TNS-00317: Failed to contact Connection Manager

TNS-00317: Failed to contact Connection Manager

Cause: Connection Manager is not running.

Action: Start the Connection Manager and retry

TNS-00316: Ran out of data buffers in the pump

TNS-00316: Ran out of data buffers in the pump

Cause: The Interchange is resource limited by having too few data buffers in the pump.

Action: If the problem persists (that is, there are a lot of log messages), increase the number of pump buffers by increasing the value of the parameter PUMP_ BUFFERS in INTCHG.ORA. Then shutdown and restart the Interchange to make the changes take effect.