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

## 12196-12285: NR (Routing) Error Messages

##### 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: 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: 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: 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: 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: TNS:internal navigation error

Cause: Internal navigation error.

Action: Not normally visible to the user. For further details contact Worldwide Customer Support.

##### ORA-12203: TNS:unable to connect to destination

Cause: Invalid TNS address supplied or destination is not listening. This error can also occur because of underlying network transport problems.

Action: Verify that the service name you entered on the command line was correct. Ensure that the listener is running at the remote node and that the ADDRESS parameters specified in TNSNAMES.ORA are correct. Finally, check that all Interchanges needed to make the connection are up and running.

##### ORA-12204: TNS: received data refused from an application

Cause: The application using the Interchange or 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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 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-12222: 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 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 TNSNET.ORA).

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

Cause: The supplied connect descriptor contains illegal syntax.

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

##### ORA-12228: 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 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: 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: 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: 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: 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: 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: 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: 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: 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.

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