TNS-12546: TNS:permission denied

TNS-12546: TNS:permission denied

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

Action: Acquire necessary privileges and try again.

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

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

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

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

TNS-12543: TNS:destination host unreachable

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

TNS-12542: TNS:address already in use

TNS-12542: TNS:address already in use

Cause: Specified listener address is already being used.

Action: Start your listener with a unique address.

TNS-12541: TNS:no listener

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

TNS-12540: TNS:internal limit restriction exceeded

TNS-12540: TNS:internal limit restriction exceeded

Cause: Too many TNS connections open simultaneously.

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

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

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

TNS-12538: TNS:no such protocol adapter

TNS-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).

TNS-12537: TNS:connection closed

TNS-12537: TNS:connection closed

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

Action: None needed; this is an information message.

TNS-12536: TNS:operation would block

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

TNS-12535: TNS:operation timed out

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

TNS-12534: TNS:operation not supported

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

TNS-12533: TNS:illegal ADDRESS parameters

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

TNS-12532: TNS:invalid argument

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

TNS-12531: TNS:cannot allocate memory

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

TNS-12519: TNS:no appropriate service handler found

TNS-12519: TNS:no appropriate service handler found

Cause: The listener could not find any available service handlers that are appropriate for the client connection.

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

TNS-12518: TNS:listener could not hand off client connection

TNS-12518: TNS:listener could not hand off client connection

Cause: The process of handing off a client connection to another process failed.

Action: Turn on listener tracing and re-execute the operation. Verify that the listener and database instance are properly configured for direct handoff. If problem persists, call Oracle Support.

TNS-12516: TNS:listener could not find available handler with matching protocol stack

TNS-12516: TNS:listener could not find available handler with matching protocol stack

Cause: None of the known and available service handlers for the given SERVICE_ NAME support the client s protocol stack: transport, session, and presentation protocols.

Action: Check to make sure that the service handlers (e.g. dispatchers) for the given SERVICE_NAME are registered with the listener, are accepting connections, and that they are properly configured to support the desired protocols.

TNS-12515: TNS:listener could not find a handler for this presentation

TNS-12515: TNS:listener could not find a handler for this presentation

Cause: None of the listener s known service handlers are registered as supporting the presentation protocol required by the connecting client.

Action: Check that the destination service is configured to accept the presentation protocol.

TNS-12514: TNS:listener does not currently know of service requested in connect descriptor

TNS-12514: TNS:listener does not currently know of service 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 a service name for a service (usually a database service) 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; service name used specifies a service known by the listener. name specified is a service known by the listener.

TNS-12513: TNS:service handler found but it has registered for a different protocol

TNS-12513: TNS:service handler found but it has registered for a different protocol

Cause: The dispatchers registered for this service are connected to the listener by way of a different network protocol than that of the client.

Action: Contact the DBA to register a dispatcher on your protocol.

TNS-12511: TNS:service handler found but it is not accepting connections

TNS-12511: TNS:service handler found but it is not accepting connections

Cause: The dispatchers notified the listener that they temporarily do not accept new connections.

Action: Attempt the connection again. If error persists, contact the DBA to check the state of the dispatchers and or or ask him to increase the number of dispatchers.

TNS-12510: TNS:database temporarily lacks resources to handle the request

TNS-12510: TNS:database temporarily lacks resources to handle the request

Cause: The dispatchers appear to be busy handling other requests.

Action: Attempt the connection again. If error persists, ask the DBA to increase the number of dispatchers and or or dispatchers limit on number of connections or sessions that they can accept.

TNS-12509: TNS:listener failed to redirect client to service handler

TNS-12509: TNS:listener failed to redirect client to service handler

Cause: The dispatcher terminated unexpectedly

Action: Attempt to connect again and if the same error occurs, contact the DBA to check the state of the dispatchers for this SID. If the problem persists, turn on tracing in the listener to determine the TNS error caused by the redirect.

TNS-12508: TNS:listener could not resolve the COMMAND given

TNS-12508: TNS:listener could not resolve the COMMAND given

Cause: d by incompatible Oracle Net or Net8 versions. Do not include in error manual.

Action: This is not seen in normal use of Oracle Net.

TNS-12505: TNS:listener does not currently know of SID given in connect descriptor

TNS-12505: TNS:listener does not currently know of SID given 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 a SID 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; known by the listener.

TNS-12504: TNS:listener was not given the SID in CONNECT_DATA

TNS-12504: TNS:listener was not given the SID in CONNECT_DATA

Cause: The SID was missing from the CONNECT_DATA.

Action: Check that the connect descriptor corresponding to the service name in TNSNAMES.ORA has an SID component in the CONNECT_DATA.

TNS-12502: TNS:listener received no CONNECT_DATA from client

TNS-12502: TNS:listener received no CONNECT_DATA from client

Cause: No CONNECT_DATA was passed to the listener.

Action: Check that the service name resolved from TNSNAMES.ORA has the CONNECT_DATA component of the connect descriptor.

TNS-12500: TNS:listener failed to start a dedicated server process

TNS-12500: TNS:listener failed to start a dedicated server process

Cause: The process of starting up a dedicated server process failed. The executable could not be found or the environment may be set up incorrectly.

Action: Turn on tracing at the ADMIN level and reexecute the operation. Verify that the ORACLE Server executable is present and has execute permissions enabled. Ensure that the ORACLE environment is specified correctly in LISTENER.ORA. The Oracle Protocol Adapter that is being called may not be installed on the local hard drive. Please check that the correct Protocol Adapter are successfully linked. If error persists, contact Oracle Customer Support.

TNS-12235: TNS:Failure to redirect to destination

TNS-12235: TNS:Failure to redirect to destination

Cause: This error is reported by an interchange which fails to redirect a connection to another interchange along the path to the destination.

Action: Report the problem to your Network Administrator so that he may fix the problem.

TNS-12234: TNS:Redirect to destination

TNS-12234: TNS:Redirect to destination

Cause: This error is reported by an interchange which determines that this interchange is not the right gateway and needs to redirect the connection to another gateway along the path to the destination.

Action: None.

TNS-12233: TNS:Failure to accept a connection

TNS-12233: TNS:Failure to accept a connection

Cause: This error is reported by an interchange which fails to accept a connection due to a redirect failure.

Action: Report the problem to your Network Administrator so that he may isolate the interchange problem.

TNS-12232: TNS:No path available to destination

TNS-12232: TNS:No path available to destination

Cause: This error is reported by an interchange which fails to find a possible path to the destination.

Action: Report the problem to your Network Administrator so that he may fix the problem.

TNS-12231: TNS:No connection possible to destination

TNS-12231: TNS:No connection possible to destination

Cause: This error is reported by an interchange which fails to find a possible connection along the path to the destination.

Action: Report the problem to your Network Administrator so that he may fix the problem.

TNS-12230: TNS:Severe Network error occurred in making this connection

TNS-12230: TNS:Severe Network error occurred in making this connection

Cause: This error is reported by an interchange which fails to make contact with the destination due to a physical network error while calling a destination.

Action: Try again later when the network service may have been fixed or report the problem to your Network Administrator so that he may fix the problem.

TNS-12229: TNS:Interchange has no more free connections

TNS-12229: TNS:Interchange has no more free connections

Cause: One or more Interchanges along the path to the destination desired has no more free connections available to be used for this call.

Action: Try again later when the Interchanges are less busy, or contact your network administrator to have him determine which interchange it is, and increase the number of connections available on that interchange.

TNS-12227: TNS:syntax error

TNS-12227: TNS:syntax error

Cause: The supplied connect descriptor contains illegal syntax.

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

TNS-12226: TNS:operating system resource quota exceeded

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

TNS-12225: TNS:destination host unreachable

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

TNS-12224: TNS:no listener

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

TNS-12223: TNS:internal limit restriction exceeded

TNS-12223: TNS:internal limit restriction exceeded

Cause: Too many TNS connections open simultaneously.

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

TNS-12222: TNS:no support is available for the protocol indicated

TNS-12222: TNS:no support is available for the protocol indicated

Cause: The protocol requested in the ADDRESS portion of the connect descriptor identified through the net service name is not available. If the supplied ADDRESS is typographically correct then support for that protocol is not installed.

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

TNS-12221: TNS:illegal ADDRESS parameters

TNS-12221: 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 or in the directory. Legal ADDRESS parameter formats may be found in the Oracle operating system specific documentation or the Oracle Net Administrator s Guide. Protocols that resolve names at the transport layer are vulnerable to this error if not properly configured or names are misspelled.

TNS-12219: TNS:missing community name from address in ADDRESS_LIST

TNS-12219: TNS:missing community name from address in ADDRESS_LIST

Cause: This error occurs when an ADDRESS_LIST has some ADDRESSes in it that have no COMMUNITY component and others that do have a COMMUNITY component.

Action: Check that in the connect descriptors you are using either all the ADDRESSes have a COMMUNITY component or all do not.

TNS-12218: TNS:unacceptable network configuration data

TNS-12218: TNS:unacceptable network configuration data

Cause: Poorly formed network configuration data. For example, a PREFERRED_ CMANAGERS entry may have an incorrect CMANAGER_NAME in the client s TNSNAV.ORA file. Or an Interchange downtime parameter (TIMEOUT_ INTERVAL) on the Navigator may be set to zero in INTCHG.ORA.

Action: Check the entries in TNSNAV.ORA and the Interchange configuration files and correct them. If necessary, talk with your network administrator to determine if the specified Interchanges (Connection Managers) are available and properly configured. Use the Oracle Network Manager to generate the configuration files if necessary.

TNS-12217: TNS:could not contact PREFERRED_CMANAGERS in TNSNAV.ORA

TNS-12217: TNS:could not contact PREFERRED_CMANAGERS in TNSNAV.ORA

Cause: There is a syntax error in the PREFERRED_CMANAGERS entry, or addresses specified are wrong, or the intended Connection Managers are unavailable.

Action: Check the PREFERRED_CMANAGERS entries in the client s TNSNAV.ORA file and correct them or talk with your network administrator to determine if the specified Connection Managers are available. Verify that the Interchanges are active by using the INTCTL STATUS command.

TNS-12216: TNS:poorly formed PREFERRED_CMANAGERS addresses in TNSNAV.ORA

TNS-12216: TNS:poorly formed PREFERRED_CMANAGERS addresses in TNSNAV.ORA

Cause: Address binding for the PREFERRED_CMANAGERS entry in the client s TNSNAV.ORA file is improperly entered.

Action: Define the ADDRESS as part of the PREFERRED_CMANAGERS binding.

TNS-12215: TNS:poorly formed PREFERRED_NAVIGATORS Addresses in TNSNAV.ORA

TNS-12215: TNS:poorly formed PREFERRED_NAVIGATORS Addresses in TNSNAV.ORA

Cause: Address binding for PREFERRED_NAVIGATORS entry is improperly entered. entry.

Action: Check your PREFERRED_NAVIGATORS entry and fix it in TNSNAV.ORA

TNS-12214: TNS:missing local communities entry in TNSNAV.ORA

TNS-12214: TNS:missing local communities entry in TNSNAV.ORA

Cause: There is no LOCAL_COMMUNITIES entry in TNSNAV.ORA.

Action: Define the LOCAL_COMMUNITIES for this node in the TNSNAV.ORA file.