Wednesday 29 February 2012

ORA-12600: TNS: string open failed

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

ORA-12599: TNS:cryptographic checksum mismatch

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-12598: TNS:banner registration failed

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

ORA-12597: TNS:connect descriptor already in use

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

ORA-12596: TNS:internal inconsistency

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

ORA-12595: TNS:no confirmation

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

ORA-12593: TNS:no registered connection

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

ORA-12592: TNS:bad packet

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

ORA-12591: TNS:event signal failure

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

ORA-12590: TNS:no I or O buffer

ORA-12590: TNS:no I or O buffer

Cause: An attempt to perform an I or 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 Oracle Customer Support.

ORA-12589: TNS:connection not bequeathable

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

ORA-12585: TNS:data truncation

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

ORA-12583: TNS:no reader

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

ORA-12582: TNS:invalid operation

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

ORA-12574: TNS:redirection denied

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

ORA-12571: TNS:packet writer failure

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

ORA-12570: TNS:packet reader failure

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

ORA-12569: TNS:packet checksum failure

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-12566: TNS:protocol error

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

ORA-12564: TNS:connection refused

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-12562: TNS:bad global handle

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

ORA-12561: TNS:unknown error

ORA-12561: TNS:unknown error

Cause: A generic protocol error occurred.

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

ORA-12560: TNS:protocol adapter error

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-12558: TNS:protocol adapter not loaded

ORA-12558: TNS:protocol adapter not loaded

Cause: On some platforms (such as OS or 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-12557: TNS:protocol adapter not loadable

ORA-12557: TNS:protocol adapter not loadable

Cause: On some platforms (such as OS or 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 tracing and reexecute the operation. The trace file will include the name of the shared library (or DLL) that could not be loaded.

ORA-12556: TNS:no caller

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

ORA-12555: TNS:permission denied

ORA-12555: TNS:permission denied

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

Action: Acquire necessary privileges and try again.

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

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

ORA-12552: TNS:operation was interrupted

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

ORA-12551: TNS:missing keyword

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-12550: TNS:syntax error

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-12549: TNS:operating system resource quota exceeded

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-12548: TNS:incomplete read or write

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

ORA-12547: TNS:lost contact

ORA-12547: TNS:lost contact

Cause: Partner has unexpectedly gone away, usually during process startup.

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

ORA-12546: TNS:permission denied

ORA-12546: TNS:permission denied

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

Action: Acquire necessary privileges and try again.

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

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 or IP, edit the TNSNAMES.ORA file to change the host name to a numeric IP address and try again.

ORA-12544: TNS:contexts have different wait or test functions

ORA-12544: TNS: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.

ORA-12543: TNS:destination host unreachable

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-12542: TNS:address already in use

ORA-12542: TNS:address already in use

Cause: Specified listener address is already being used.

Action: Start your listener with a unique address.

ORA-12541: TNS:no listener

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-12540: TNS:internal limit restriction exceeded

ORA-12540: TNS:internal limit restriction exceeded

Cause: Too many TNS connections open simultaneously.

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

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

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

ORA-12538: TNS:no such protocol adapter

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 adapter is not installed.

Action: Install the protocol adapter or correct typographically 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 SQLNET.ORA).

ORA-12537: TNS:connection closed

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-12536: TNS:operation would block

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-12535: TNS:operation timed out

ORA-12535: TNS:operation timed out

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

Action: Look at the documentation on the secondary errors for possible remedy. See SQLNET.LOG to find secondary error if not provided explicitly. Turn on tracing to gather more information.

ORA-12534: TNS:operation not supported

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

ORA-12533: TNS:illegal ADDRESS parameters

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-12532: TNS:invalid argument

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

ORA-12531: TNS:cannot allocate memory

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-12529: TNS:connect request rejected based on current filtering rules

ORA-12529: TNS:connect request rejected based on current filtering rules

Cause: Connection Manager and its listener were configured with filtering rules specifying that the connect request be rejected.

Action: If this connect request should be allowed, then contact the administrator to modify the filtering rules.

ORA-12528: TNS:listener: all appropriate instances are blocking new connections

ORA-12528: TNS:listener: all appropriate instances are blocking new connections

Cause: All instances supporting the service requested by the client reported that they were blocking the new connections. This condition may be temporary, such as at instance startup.

Action: Attempt the connection again. If error persists, then contact the administrator to check the status of the instances.

ORA-12527: TNS:listener: all instances are in restricted mode or blocking new connections

ORA-12527: TNS:listener: all instances are in restricted mode or blocking new connections

Cause: All appropriate database instances supporting the service requested by the client reported that they either were in restricted mode or were blocking the new connections. The Listener does not allow connections to such instances. This condition may be temporary, such as at instance startup.

Action: Attempt the connection again. If error persists, then contact the database administrator to check the status of the instances.

ORA-12526: TNS:listener: all appropriate instances are in restricted mode

ORA-12526: TNS:listener: all appropriate instances are in restricted mode

Cause: Database instances supporting the service requested by the client were in restricted mode. The Listener does not allow connections to instances in restricted mode. This condition may be temporary, such as during periods when database administration is performed.

Action: Attempt the connection again. If error persists, then contact the database administrator to change the mode of the instance, if appropriate.

ORA-12525: TNS:listener has not received client s request in time allowed

ORA-12525: TNS:listener has not received client s request in time allowed

Cause: The listener disconnected the client because the client failed to provide the necessary connect information within the allowed time interval. This may be a result of network or system delays; or this may indicate that a malicious client is trying to cause a Denial of Service attack on the listener.

Action: If the error occurred because of a slow network or system, reconfigure INBOUND_CONNECT_TIMEOUT to a larger value. If a malicious client is suspected, use the address in listener.log to identify the source and restrict access. Turn on tracing for more information.

ORA-12524: TNS:listener could not resolve HANDLER_NAME given in connect descriptor

ORA-12524: TNS:listener could not resolve HANDLER_NAME given in connect descriptor

Cause: The HANDLER_NAME in the CONNECT_DATA was not found in the listener s tables for the specified SERVICE_NAME and INSTANCE_NAME.

Action: Check to make sure that the HANDLER_NAME specified is correct.

ORA-12523: TNS:listener could not find instance appropriate for the client connection

ORA-12523: TNS:listener could not find instance appropriate for the client connection

Cause: The listener could not find any available (database) instances, that are appropriate for the client connection.

Action: Run lsnrctl services to ensure that the instance(s) are registered with the listener, and have status READY.

ORA-12522: TNS:listener could not find available instance with given INSTANCE_ ROLE

ORA-12522: TNS:listener could not find available instance with given INSTANCE_ ROLE

Cause: There are not any available and appropriate database instances registered with the listener, that are part of the service identified by SERVICE_NAME given in the connect descriptor and that have the specified INSTANCE_ROLE (and INSTANCE_NAME, if specified).

Action: Check to make sure that the INSTANCE_ROLE specified is correct. Run lsnrctl services to ensure that the instance(s) have registered with the listener and that they are ready to accept connections.

ORA-12521: TNS:listener does not currently know of instance requested in connect descriptor

ORA-12521: TNS:listener does not currently know of instance requested in connect descriptor

Cause: The listener received a request to establish a connection to a database or other service. The connect descriptor received by the listener specified in addition to the service name an instance name for an instance (usually a database instance) that either has not yet dynamically registered with the listener or has not been statically configured for the listener. This may be a temporary condition such as after the listener has started, but before the database instance has registered with the listener.

Action: services lamp;lt;lamp;nbsp;listener namelamp;gt; an instance name known by the listener.

ORA-12520: TNS:listener could not find available handler for requested type of server

ORA-12520: TNS:listener could not find available handler for requested type of server

Cause: None of the known and available service handlers for requested type of server (dedicated or shared) are appropriate for the client connection.

Action: Run lsnrctl services to ensure that the instance(s) have registered with the listener and that the appropriate handlers are accepting connections.