TNS-12227: TNS:syntax error
Cause: The supplied connect descriptor contains illegal syntax.
Action: Check the syntax of the connect descriptor in TNSNAMES.ORA.
Category Archives: TNS Database Error Messages
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 resources, or perform a different function.
TNS-12225: TNS:destination host unreachable
TNS-12225: TNS: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-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 retry.
TNS-12222: TNS:no such protocol adapter
TNS-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).
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. 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-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.