TNS-12213: TNS:incomplete PREFERRED_CMANAGERS binding in TNSNAV.ORA

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

TNS-12212: TNS:incomplete PREFERRED_CMANAGERS binding in TNSNAV.ORA

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

TNS-12211: TNS:needs PREFERRED_CMANAGERS entry in TNSNAV.ORA

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

TNS-12210: TNS:error in finding Navigator data

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

TNS-12209: TNS:encountered uninitialized global

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

TNS-12208: TNS:could not find the TNSNAV.ORA file

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

TNS-12207: TNS:unable to perform navigation

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

TNS-12206: TNS:received a TNS error during navigation

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

TNS-12205: TNS:could not get failed addresses

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

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

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

TNS-12203: TNS:unable to connect to destination

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

TNS-12202: TNS:internal navigation error

TNS-12202: TNS:internal navigation error

Cause: Internal navigation error.

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

TNS-12201: TNS:encountered too small a connection buffer

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

TNS-12200: TNS:could not allocate memory

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

TNS-12198: TNS:could not find path to destination

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

TNS-12197: TNS:keyword-value resolution error

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

TNS-12196: TNS:received an error from TNS

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

TNS-12171: TNS:could not resolve connect identifier: string

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

TNS-12170: TNS:Connect timeout occurred

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

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

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

TNS-12168: TNS:Unable to contact LDAP Directory Server

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

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

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

Cause: NVstring contained DESCRIPTION or HO.

Action: Call HO agent from integrating server.

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

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

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

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

TNS-12163: TNS:connect descriptor is too long

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

TNS-12162: TNS:net service name is incorrectly specified

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

TNS-12161: TNS:internal error: partial data received

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

TNS-12160: TNS:internal error: Bad error number

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

TNS-12159: TNS:trace file not writeable

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

TNS-12158: TNS:could not initialize parameter subsystem

TNS-12158: TNS:could not initialize parameter subsystem

Cause: Unable to locate parameter file.

Action: Verify that a valid parameter file exists, and is readable.

TNS-12157: TNS:internal network communication error

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

TNS-12156: TNS:tried to reset line from incorrect state

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

TNS-12155: TNS:received bad datatype in NSWMARKER packet

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

TNS-12154: TNS:could not resolve the connect identifier specified

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

TNS-12153: TNS:not connected

TNS-12153: TNS:not connected

Cause: Not currently connected to a remote host.

Action: Reestablish connection.

TNS-12152: TNS:unable to send break message

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

TNS-12151: TNS:received bad packet type from network layer

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

TNS-12150: TNS:unable to send data

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

TNS-04235: Trace Assistant WARNING: Unknown TTC protocol

TNS-04235: Trace Assistant WARNING: Unknown TTC protocol

Cause: Trace Assistant has reached a point in which the TTC protocol can not be understood.

Action: None.

TNS-04234: Trace Assistant WARNING: won t decode TTC

TNS-04234: Trace Assistant WARNING: won t decode TTC

Cause: Trace assistant does not have enough information to decode TTC data. This maybe an old trace file or from a platform that trace assistant does not understand.

Action: None.

TNS-04233: Trace Assistant WARNING: Going beyond Packet length

TNS-04233: Trace Assistant WARNING: Going beyond Packet length

Cause: Trying to read beyond packet length. The trace file may be corrupted

Action: None.

TNS-04232: Trace Assistant WARNING: Not retrieving all rows

TNS-04232: Trace Assistant WARNING: Not retrieving all rows

Cause: Trace Assitante won t retrieve all the rows data.

Action: None.

TNS-04231: Trace Assistant WARNING: Assuming Oracle trace format

TNS-04231: Trace Assistant WARNING: Assuming Oracle trace format

Cause: This trace file may not be a Network trace file. The default format (Oracle Trace) will be assumed.

Action: None.

TNS-04212: Trace Assistant Internal ERROR: NACOM Type Error

TNS-04212: Trace Assistant Internal ERROR: NACOM Type Error

Cause: Not able to decode Network Authentication information

Action: Contact World Wide Support.

TNS-04211: Trace Assistant Internal ERROR: CORE

TNS-04211: Trace Assistant Internal ERROR: CORE

Cause: Internal System Error

Action: Contact World Wide Support.

TNS-04210: Trace Assistant Internal ERROR: End of File

TNS-04210: Trace Assistant Internal ERROR: End of File

Cause: Reaching End of File to soon. Not able to decode trace file. Your trace file appears to be truncated.

Action: Generate another trace file. This trace file can not be decoded.

TNS-04209: Trace Assistant Internal ERROR: Type Error

TNS-04209: Trace Assistant Internal ERROR: Type Error

Cause: Internal type error,

Action: Contact World Wide Support.

TNS-04208: Trace Assistant Internal ERROR: Fatal

TNS-04208: Trace Assistant Internal ERROR: Fatal

Cause: Fatal internal error

Action: Contact World Wide Support.

TNS-04207: Trace Assistant Internal ERROR: Packet Length

TNS-04207: Trace Assistant Internal ERROR: Packet Length

Cause: The packet being decode is corrupted.

Action: Verify that your trace file is not corrupted. If trace file looks OK, with not strange characters in it, contact World Wide Support and provide trace file to them.

TNS-04206: Trace Assistant Internal ERROR: Packet Type

TNS-04206: Trace Assistant Internal ERROR: Packet Type

Cause: The packet type read by trcAsst is not valid.

Action: Verify that your trace file is not corrupted. If trace file looks OK, with not strange characters in it, contact World Wide Support and provide trace file to them.

TNS-04205: Trace Assistant Internal ERROR: Memory

TNS-04205: Trace Assistant Internal ERROR: Memory

Cause: Possible memory problem

Action: Verify the amount of available memory on the system.

TNS-04204: Trace Assistant Internal ERROR: Couldn t Open trace file

TNS-04204: Trace Assistant Internal ERROR: Couldn t Open trace file

Cause: The trace file name given doesn t exist or it is not accessible for this user.

Action: Check the spelling, and permissions of the trace file.

TNS-04203: Trace Assistant Usage ERROR: Invalid options

TNS-04203: Trace Assistant Usage ERROR: Invalid options

Cause: The options provided are not valid

Action: Check the valid options for this tool.

TNS-04202: Trace Assistant Usage ERROR: Not enough arguments

TNS-04202: Trace Assistant Usage ERROR: Not enough arguments

Cause: The lamp;lt;lamp;nbsp;file namelamp;gt; and or or the lamp;lt;lamp;nbsp;optionslamp;gt; arguments are missing

Action: Put the right number of command line arguments.

TNS-04201: Trace Assistant Usage ERROR: Missing File name

TNS-04201: Trace Assistant Usage ERROR: Missing File name

Cause: Trace file name argument is missing

Action: Put the trace file name as the last command line argument for for this tool.

TNS-04144: Nothing to migrate

TNS-04144: Nothing to migrate

Cause: CMMIGR did not find anything in the old CMAN.ORA file that has an equivalent in the new format.

Action: None

TNS-04143: Unable to write the new CMAN.ORA file.

TNS-04143: Unable to write the new CMAN.ORA file.

Cause: CMMIGR was unable to create the new CMAN.ORA file due to insufficient perimissions.

Action: Set WRITE permissions to the directory in which CMAN.ORA file is to be written.

TNS-04142: CMAN.ORA file has an invalid format.

TNS-04142: CMAN.ORA file has an invalid format.

Cause: CMMIGR was unable to recognize the format of CMAN.ORA file.

Action: Check for the syntax errors in CMAN.ORA file, and correct them.

TNS-04141: Unable to find CMAN.ORA file.

TNS-04141: Unable to find CMAN.ORA file.

Cause: CMMIGR was not able to find CMAN.ORA file.

Action: Check whether CMAN.ORA file is present in $TNS_NAME or admin, or in $ORACLE_HOME or network or admin, or in the path specified in the command line.

TNS-04140: Migration completed successfully.

TNS-04140: Migration completed successfully.

Cause: CMMIGR has successfully completed the migration of the old CMAN.ORA file to the new format.

Action: None