ORA-12323: unable to open database (link name string)

ORA-12323: unable to open database (link name string)

Cause: This message should be accompanied by additional error messages that indicate the cause of the problem.

Action: Follow the steps outlined in the accompanying error messages to resolve the problem.

ORA-12322: unable to mount database (link name string)

ORA-12322: unable to mount database (link name string)

Cause: This message should be accompanied by additional error messages that indicate the cause of the problem.

Action: Follow the steps outlined in the accompanying error messages to resolve the problem.

ORA-12321: database (link name string) is not open and AUTO_ MOUNTING=FALSE

ORA-12321: database (link name string) is not open and AUTO_ MOUNTING=FALSE

Cause: The secondary database that your instance is attempting to mount is not open and automatic mounting has not been enabled.

Action: Manually mount and open the secondary database using ALTER DATABASE lamp;lt;lamp;nbsp;linknamelamp;gt; with the OPEN and MOUNT options. Alternately, to allow your instance to automatically mount and open secondary databases, set the AUTO_MOUNTING parameter in the parameter file to TRUE.

ORA-12319: database (link name string) is already open

ORA-12319: database (link name string) is already open

Cause: You are attempting to open a secondary database that is already open.

Action: The database is open and you need not take additional action to establish access.

ORA-12318: database (link name string) is already mounted

ORA-12318: database (link name string) is already mounted

Cause: You are attempting to mount a secondary database that has already been mounted by your instance.

Action: to mount it. To establish access, use the ALTER DATABASE lamp;lt;lamp;nbsp;linknamelamp;gt; OPEN command to open the database.

ORA-12317: logon to database (link name string) denied

ORA-12317: logon to database (link name string) denied

Cause: There are several possible causes for this error. First, you can get this error if your username (and password, if you are using database instead of operating system authentication) in the secondary database are not identical to your username (and password) in the primary database. Second, you can get this error if your username in the secondary database is invalid (has not been created). Third, you can get this error if the username or password combination specified in the connect string of the database link definition is invalid (either not created or has an invalid password).

Action: In the first case, ensure that the secondary database contains a username (and password, if you are using database authentication) identical to the one you are using in the primary database. In general, you should always use operating system authentication in Trusted ORACLE (see the Trusted ORACLE RDBMS Guide to Security Features for more information about the advantages of OS authentication). In the second case, ensure that your username in the secondary database has been created. In the third case, ensure that the username specified in the connect string has been created in the secondary database.

ORA-12316: syntax error in database link s connect string

ORA-12316: syntax error in database link s connect string

Cause: The connect string in the CREATE DATABASE LINK statement has a syntactical error.

Action: Drop the database link and recreate it using valid syntax. See the SQL Language Reference Manual for more information about the connect string portion of the CREATE DATABASE LINK statement.

ORA-12315: database link type is invalid for the ALTER DATABASE statement

ORA-12315: database link type is invalid for the ALTER DATABASE statement

Cause: The database link name you specified on the ALTER DATABASE statement is not an ROM: link. You must specify an ROM: link when using the ALTER DATABASE statement to mount or open a secondary database.

Action: Re-issue the ALTER DATABASE statement using a valid ROM: link to the database you want to mount or open. If a valid ROM: link does not exist, create one using the CREATE DATABASE LINK command. See the Trusted ORACLE RDBMS Guide to Security Features for more information about creating database links using the ROM: link type.

ORA-12236: TNS:protocol support not loaded

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.

ORA-12235: TNS:Failure to redirect to destination

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-12234: TNS:Redirect to destination

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-12233: TNS:Failure to accept a connection

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-12232: TNS:No path available to destination

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-12231: TNS:No connection possible to destination

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-12230: TNS:Severe Network error occurred in making this connection

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-12229: TNS:Interchange has no more free connections

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-12228: TNS:protocol adapter not loadable

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

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

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-12225: TNS:destination host unreachable

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-12224: TNS:no listener

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

ORA-12223: TNS:internal limit restriction exceeded

Cause: Too many TNS connections open simultaneously.

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

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

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-12221: TNS:illegal ADDRESS parameters

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-12219: TNS:missing community name from address in ADDRESS_LIST

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-12218: TNS:unacceptable network configuration data

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-12217: TNS:could not contact PREFERRED_CMANAGERS in TNSNAV.ORA

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-12216: TNS:poorly formed PREFERRED_CMANAGERS addresses 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-12215: TNS:poorly formed PREFERRED_NAVIGATORS Addresses in TNSNAV.ORA

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-12214: TNS:missing local communities entry in TNSNAV.ORA

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-12213: TNS:incomplete PREFERRED_CMANAGERS binding in TNSNAV.ORA

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-12212: TNS:incomplete PREFERRED_CMANAGERS binding in TNSNAV.ORA

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-12211: TNS:needs PREFERRED_CMANAGERS entry in TNSNAV.ORA

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-12210: TNS:error in finding Navigator data

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-12209: TNS:encountered uninitialized global

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-12208: TNS:could not find the TNSNAV.ORA file

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-12207: TNS:unable to perform navigation

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-12206: TNS:received a TNS error during navigation

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-12205: TNS:could not get failed addresses

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-12204: TNS:received data refused from an application

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-12203: TNS:unable to connect to destination

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

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-12201: TNS:encountered too small a connection buffer

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-12200: TNS:could not allocate memory

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-12198: TNS:could not find path to destination

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-12197: TNS:keyword-value resolution 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-12196: TNS:received an error from TNS

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-12171: TNS:could not resolve connect identifier: string

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) accessible. 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). is configured in the directory. 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). Administrators Guide or the Oracle operating system specific guide for more information on naming.

ORA-12170: TNS:Connect timeout occurred

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 or IP).

ORA-12169: TNS:Net service name given as connect identifier is too long

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-12168: TNS:Unable to contact LDAP Directory Server

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-12166: TNS:Client can not connect to HO agent.

ORA-12166: TNS:Client can not connect to HO agent.

Cause: NVstring contained DESCRIPTION or HO.

Action: Call HO agent from integrating server.

ORA-12165: TNS:Trying to write trace file into swap space.

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-12164: TNS:Sqlnet.fdf file not present

ORA-12164: TNS:Sqlnet.fdf file not present

Cause: The sqlnet.fdf file doesn t exist in $ORACLE_HOME or network or admin.

Action: The sqlnet.fdf file is required for Oracle Tracing to occur. Either install the sqlnet.fdf file in $ORACLE_HOME or network or admin or turn off tracing in your ORA file.

ORA-12163: TNS:connect descriptor is too long

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-12162: TNS:net service name is incorrectly specified

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-12161: TNS:internal error: partial data received

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-12160: TNS:internal error: Bad error number

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-12159: TNS:trace file not writeable

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-12158: TNS:could not initialize parameter subsystem

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.