Overblog Suivre ce blog
Editer la page Administration Créer mon blog
/ / /

 

Error ORA TNS Cause et Action

 

ORA-12150 ORA-12150: TNS:unable to send data
Cause Unable to send data. Connection probably disconnected.
Action Reestablish connection. If the error is persistent, turn on tracing and reexecute the operation.

 

ORA-12151 ORA-12151: TNS:received bad packet type from network layer
Cause Internal error.
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-12152 ORA-12152: TNS:unable to send break message
Cause Unable to send break message. Connection probably disconnected.
Action Reestablish connection. If the error is persistent, turn on tracing and reexecute the operation.

 

ORA-12153 ORA-12153: TNS:not connected
Cause Not currently connected to a remote host.
Action Reestablish connection.

 

ORA-12154 ORA-12154: TNS:could not resolve the connect identifier specified
Cause A connection to a database or other service was requested using a connect identifier, and the connect identifier specified could not be resolved into a connect descriptor using one of the naming methods configured. For example, if the type of connect identifier used was a net service name then the net service name could not be found in a naming method repository, or the repository could not be located or reached.
Action If you are using local naming (TNSNAMES.ORA file):
- Make sure that "TNSNAMES" is listed as one of the values of the NAMES.DIRECTORY_PATH parameter in the Oracle Net profile (SQLNET.ORA)
- Verify that a TNSNAMES.ORA file exists and is in the proper directory and is accessible.
- Check that the net service name used as the connect identifier exists in the TNSNAMES.ORA file.
- Make sure there are no syntax errors anywhere in the TNSNAMES.ORA file. Look for unmatched parentheses or stray characters. Errors in a TNSNAMES.ORA file may make it unusable.

If you are using directory naming:
- Verify that "LDAP" is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA).
- Verify that the LDAP directory server is up and that it is accessible.
- Verify that the net service name or database name used as the connect identifier is configured in the directory.
- Verify that the default context being used is correct by specifying a fully qualified net service name or a full LDAP DN as the connect identifier
- If you are using easy connect naming:
- Verify that "EZCONNECT" is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA).
- Make sure the host, port and service name specified are correct.
- Try enclosing the connect identifier in quote marks. See the Oracle Net Services Administrators Guide or the Oracle operating system specific guide for more information on naming.

 

ORA-12155 ORA-12155: TNS:received bad datatype in NSWMARKER packet
Cause Internal error during break handling.
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-12156 ORA-12156: TNS:tried to reset line from incorrect state
Cause Internal error during break handling.
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-12157 ORA-12157: TNS:internal network communication error
Cause Internal error during network communication.
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-12158 ORA-12158: TNS:could not initialize parameter subsystem
Cause Unable to locate parameter file.
Action Verify that a valid parameter file exists, and is readable.

 

ORA-12159 ORA-12159: TNS:trace file not writeable
Cause The trace file to be generated is not writeable by this user.
Action If the user does not have write permissions in the directory to which the trace file will be written, contact an administrator to get the proper permissions or set the TRACE_DIRECTORY_CLIENT parameter in the net profile (SQLNET.ORA file) to a directory the user can write to.

 

ORA-12160 ORA-12160: TNS:internal error: Bad error number
Cause Corrupt error reporting subsystem.
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-12161 ORA-12161: TNS:internal error: partial data received
Cause The connection may be terminated.
Action Reconnect and try again. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.

 

ORA-12162 ORA-12162: TNS:net service name is incorrectly specified
Cause The connect descriptor corresponding to the net service name in TNSNAMES.ORA or in the directory server (Oracle Internet Directory) is incorrectly specified.
Action If using local naming make sure there are no syntax errors in the corresponding connect descriptor in the TNSNAMES.ORA file. If using directory naming check the information provided through the administration used for directory naming.

 

ORA-12163 ORA-12163: TNS:connect descriptor is too long
Cause The connect descriptor corresponding to the net service name specified as the connect identifier is too long. The maximum length for a connect descriptor is 512 bytes and this limit has been exceeded.
Action Check the net service name"s connect descriptor in the local naming file (TNSNAMES.ORA) or in the directory server (Oracle Internet Directory). Use a smaller connect descriptor. If this is not possible, contact Worldwide Customer Support.

 

ORA-12164 ORA-12164: TNS:Sqlnet.fdf file not present
Cause The sqlnet.fdf file doesn"t exist in $ORACLE_HOME/network/admin.
Action The sqlnet.fdf file is required for Oracle Tracing to occur. Either install the sqlnet.fdf file in $ORACLE_HOME/network/admin or turn off tracing in your ORA file.

 

ORA-12165 ORA-12165: TNS:Trying to write trace file into swap space.
Cause Oracle Trace doesn"t allow writing trace information into your swap space.
Action Oracle Trace cannot write trace information into swap space so either disable tracing or redirect trace files to be written to another area of your disk.

 

ORA-12166 ORA-12166: TNS:Client can not connect to HO agent.
Cause NVstring contained DESCRIPTION/HO.
Action Call HO agent from integrating server.

 

ORA-12168 ORA-12168: TNS:Unable to contact LDAP Directory Server
Cause Cannot contact LDAP directory server to get Oracle Net configuration.
Action Verify that the directory server is up and accessible from the network. Verify that directory access configuration is correct. For more information see the Oracle Internet Directory Administrators Guide or the Oracle Net Administrators Guide.

 

ORA-12169 ORA-12169: TNS:Net service name given as connect identifier is too long
Cause The net service name you are attempting to resolve is too long.
Action The maximum length of a net service name is 255 bytes; this limit has been exceeded. Use a smaller net service name. If this is not possible, contact Worldwide Customer Support.

 

ORA-12170 ORA-12170: TNS:Connect timeout occurred
Cause The server shut down because connection establishment or communication with a client failed to complete within the allotted 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 server.
Action If the error occurred because of a slow network or system, reconfigure one or all of the parameters SQLNET.INBOUND_CONNECT_TIMEOUT, SQLNET.SEND_TIMEOUT, SQLNET.RECV_TIMEOUT in sqlnet.ora to larger values. If a malicious client is suspected, use the address in sqlnet.log to identify the source and restrict access. Note that logged addresses may not be reliable as they can be forged (e.g. in TCP/IP).

 

ORA-12171 ORA-12171: TNS:could not resolve connect identifier: string
Cause A connection to a database or other service was requested using a connect identifier, and the connect identifier specified could not be resolved into a connect descriptor using one of the naming methods configured. For example, if the type of connect identifier used was a net service name then the net service name could not be found in a naming method repository, or the repository could not be located or reached.
Action If you are using local naming (TNSNAMES.ORA file):
- Make sure that "TNSNAMES" is listed as one of the values of the NAMES.DIRECTORY_PATH parameter in the Oracle Net profile (SQLNET.ORA)
- Verify that a TNSNAMES.ORA file exists and is in the proper directory and is accessible.
- Check that the net service name used as the connect identifier exists in the TNSNAMES.ORA file.
- Make sure there are no syntax errors anywhere in the TNSNAMES.ORA file. Look for unmatched parentheses or stray characters. Errors in a TNSNAMES.ORA file may make it unusable.

If you are using directory naming:
- Verify that "LDAP" is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA).
- Verify that the LDAP directory server is up and that it is accessible.
- Verify that the net service name or database name used as the connect identifier is configured in the directory.
- Verify that the default context being used is correct by specifying a fully qualified net service name or a full LDAP DN as the connect identifier
- If you are using easy connect naming:
- Verify that "EZCONNECT" is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA).
- Make sure the host, port and service name specified are correct.
- Try enclosing the connect identifier in quote marks. See the Oracle Net Services Administrators Guide or the Oracle operating system specific guide for more information on naming.

 

ORA-12196 ORA-12196: TNS:received an error from TNS
Cause The navigation layer received an error from TNS.
Action See the error log file for the specific TNS error.

 

ORA-12197 ORA-12197: TNS:keyword-value resolution error
Cause The navigation layer received an error while trying to look up a value for a keyword.
Action Check the syntax of the connect descriptor.

 

ORA-12198 ORA-12198: TNS:could not find path to destination
Cause Could not navigate a path through Interchanges to the destination. This error occurs if an invalid community is in the address string, or the address includes a protocol that is not available or the TNSNAV.ORA file does not have a correct CMANAGER address specified or the Interchange is down.
Action Assure that Interchanges necessary to get to the desired destination are up and have available capacity for an additional connection. Also check that the correct community and protocol have been specified in the CMANAGER address used.

 

ORA-12200 ORA-12200: TNS:could not allocate memory
Cause Out of memory on machine.
Action Reconfigure machine to have more storage or run fewer applications while the Interchange is running.

 

ORA-12201 ORA-12201: TNS:encountered too small a connection buffer
Cause TNS connection buffer supplied by the application was too small to retrieve the data sent back.
Action Supply a larger connection buffer. If problem persists, call Worldwide Customer Support.

 

ORA-12202 ORA-12202: TNS:internal navigation error
Cause Internal navigation error.
Action Not normally visible to the user. For further details contact Worldwide Customer Support.

 

ORA-12203 ORA-12203: TNS:unable to connect to destination
Cause Invalid address specified or destination is not listening. This error can also occur because of underlying network or network transport problems.
Action Verify that the net service name you entered was correct. Verify that the ADDRESS portion of the connect descriptor which corresponds to the net service name is correct. Ensure that the destination process (for example the listener) is running at the remote node.

 

ORA-12204 ORA-12204: TNS:received data refused from an application
Cause The application using Connection Manager refused the connection at the listener.
Action Make sure that the application listener at the destination is functioning correctly. If it is and the problem persists, contact Worldwide Customer Support.

 

ORA-12205 ORA-12205: TNS:could not get failed addresses
Cause Internal navigation error.
Action Not normally visible to the user. For further details contact Worldwide Customer Support.

 

ORA-12206 ORA-12206: TNS:received a TNS error during navigation
Cause Internal navigation error because of an unexpected TNS error.
Action Look at the log file to find the TNS error. If necessary, turn on tracing and repeat the operation.

 

ORA-12207 ORA-12207: TNS:unable to perform navigation
Cause Improperly configured navigation file TNSNAV.ORA.
Action Check the syntax of the TNSNAV.ORA file on the application`s machine, and verify that it lists the correct communities.

 

ORA-12208 ORA-12208: TNS:could not find the TNSNAV.ORA file
Cause Either the ORACLE environment is not set up correctly, or the TNSNAV.ORA file is not present.
Action Ensure that the ORACLE environment is set up appropriately on your platform and that a TNSNAV.ORA file is present.

 

ORA-12209 ORA-12209: TNS:encountered uninitialized global
Cause Application calling navigation routine has not properly configured the global variables. There are no TNSNAV.ORA files available, or they are defective.
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-12210 ORA-12210: TNS:error in finding Navigator data
Cause Application calling navigation routine has not properly configured the TNSNAV.ORA file.
Action Check the syntax of the TNSNAV.ORA file.

 

ORA-12211 ORA-12211: TNS:needs PREFERRED_CMANAGERS entry in TNSNAV.ORA
Cause TNSNAV.ORA does not have a PREFERRED_CMANAGERS defined.
Action Add a PREFERRED_CMANAGERS entry to the TNSNAV.ORA file.

 

ORA-12212 ORA-12212: TNS:incomplete PREFERRED_CMANAGERS binding in TNSNAV.ORA
Cause The PREFERRED_CMANAGERS binding in the client"s TNSNAV.ORA file does not have a CMANAGER_NAME specified.
Action Define the CMANAGER_NAME as part of the PREFERRED_CMANAGERS binding. Use of the Oracle Network Manager should eliminate this error.

 

ORA-12213 ORA-12213: TNS:incomplete PREFERRED_CMANAGERS binding in TNSNAV.ORA
Cause The PREFERRED_CMANAGERS binding in the client"s TNSNAV.ORA file does not have an ADDRESS specified.
Action Define the ADDRESS as part of the PREFERRED_CMANAGERS binding.

 

ORA-12214 ORA-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.

 

ORA-12215 ORA-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

 

ORA-12216 ORA-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.

 

ORA-12217 ORA-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.

 

ORA-12218 ORA-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.

 

ORA-12219 ORA-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.

 

ORA-12221 ORA-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.

 

ORA-12222 ORA-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.

 

ORA-12223 ORA-12223: TNS:internal limit restriction exceeded
Cause Too many TNS connections open simultaneously.
Action Wait for connections to close and re-try.

 

ORA-12224 ORA-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.

 

ORA-12225 ORA-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.

 

ORA-12226 ORA-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.

 

ORA-12227 ORA-12227: TNS:syntax error
Cause The supplied connect descriptor contains illegal syntax.
Action Check the syntax of the connect descriptor in TNSNAMES.ORA.

 

ORA-12228 ORA-12228: TNS:protocol adapter not loadable
Cause On some platforms (such as Windows) protocol support is 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-12229 ORA-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.

 

ORA-12230 ORA-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.

 

ORA-12231 ORA-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.

 

ORA-12232 ORA-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.

 

ORA-12233 ORA-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.

 

ORA-12234 ORA-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.

 

ORA-12235 ORA-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.

 

ORA-12236 ORA-12236: TNS:protocol support not loaded
Cause On some platforms (such as Windows) protocol support is 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.

Partager cette page

Repost 0
Published by