Oracle Network Products Troubleshooting Guide

Library

Product

Contents

Index

Networking Error Messages

Interchange Control Utility (NR) Error Messages (TNS-00001 to 00099)
Interchange Error Messages (TNS-00100 to 00499)
NT Error Messages (TNS-00501 to 00999)
Listener Error Messages (TNS-01000 to 02500)
NA Internal Messages (TNS-02501 to 03500)
OSN Error Messages (ORA-12150 to 12195)
NR Error Messages (ORA-12196 to 12285)
TNS Listener Error Messages (ORA-12500 to 12530)
NS Error Messages (ORA-12531 to 12629)
NA Error Messages (ORA-12630 to 12699)

This chapter lists the error messages that may be returned by the following Oracle network components:

SQL*Net release 2.0 and later

client

server

listener

MultiProtocol Interchange release 2.0 and later

Connection Manager

Pump

Navigator

MultiProtocol Interchange Control Program

Transparent Network Substrate (TNS)

Oracle Protocol Adapters

Secure Network Services

Native Naming

Oracle network product error messages are identified by two prefixes. The first prefix is "ORA-" and the other is "TNS-." Error messages beginning with the "ORA-" prefixes are generated by the Oracle Server and other Oracle utilities. The error numbers within the range from 12150 through 12629 are network related errors, and these errors contain text that begins with "TNS:" Error messages from 12630 through 12699 are generated by Secure Network Services.

Please consult the appropriate documentation for detailed information on other "ORA-" prefixed errors outside this range. For more information on the error message prefixes, please refer to Chapter 1, "Coping with Error Messages."

Table 3-1 shows the networking software components that generate error messages with "ORA" or "TNS"prefixes.

Table 6 - 1. Error Message Prefix, Numbers, and Components

Prefix Error Number Component Type of Error
TNS 1 to 500 NR (routing) MultiProtocol Interchange
TNS 501 to 1000 NT (transport) Protocol Adapter
TNS 1001 to 1500 Listener Control Program Listener Control Program
ORA/TNS 12150 to 12195 SQL*Net Oracle SQL*Net
ORA/TNS 12196 to 12285 NR (routing) TNS
ORA/TNS 12500 to 12530 Listener Listener to client
ORA/TNS 12531 to 12629 NS (session) TNS
ORA 12630 to 12699 NA Native Services

Interchange Control Utility (NR) Error Messages (TNS-00001 to 00099)

TNS-00001 INTCTL: error while getting command line from the terminal

Cause: Improper standard input connection from the terminal.

Action: Normally not visible to the user. Start the INTCTL program again. If error persists, contact Worldwide Customer Support.
TNS-00002 INTCTL: error while starting the Interchange

Cause: The Interchange could not be started.

Action: Check the Interchange configuration files (INTCHG.ORA, TNSNET.ORA, and TNSNAV.ORA) for errors and confirm that no other programs are using the ADDRESS(es) specified. If error continues, turn on tracing in the Interchange components and examine the trace files to determine the cause of the problem. Be sure to turn tracing off when the problem has been rectified.
TNS-00003 INTCTL: error while sending the request to the Interchange

Cause: Improper command sent to the Interchange or the Interchange is not responding. Not normally visible to the user.

Action: Verify that the command sent to the Interchange is valid. Also check that the Interchange is running by using the INTCTL STATUS command. If necessary, start the Interchange using the INTCTL START command.
TNS-00004 INTCTL: error while starting the Navigator

Cause: The Navigator could not be started.

Action: Check to make sure that executables for the Navigator (navgatr) are present in the ORACLE executable directory on your platform. Check the configuration files TNSNET.ORA and TNSNAV.ORA for errors. If error continues, turn on tracing in the Interchange components and examine the trace files to determine the cause of the problem. Be sure to turn tracing off when the problem has been rectified.
TNS-00005 INTCTL: error while sending request to the Navigator

Cause: The Navigator is not responding. Either the Navigator is not running or another process is responding. Not normally visible to the user.

Action: Check that the Navigator is running by using the STATUS command of the Interchange Control Utility. Verify that the correct addresses are listed in the TNSNAMES.ORA, TNSNET.ORA, and TNSNAV.ORA configuration files.
TNS-00006 INTCTL: HOST variable is not defined

Cause: The HOST variable was not set.

Action: Set the HOST variable properly and restart the INTCTL program.
TNS-00007 INTCTL: unknown host

Cause: The pointer HOST is set to an unknown hostname.

Action: Set the pointer HOST properly and restart INTCTL program.
TNS-00008 INTCTL: could not contact destination Navigator

Cause: Connection could not be established to a Navigator. This may be because the Navigator specified is not running or the Navigator addresses are incorrect.

Action: Check that the Navigator is running by using the STATUS command of the Interchange Control Utility; if necessary, start the Navigator using the START command of the Interchange Control Utility. If it is running and the error persists, contact Worldwide Customer Support.
TNS-00009 INTCTL:could not contact destination Connection Manager

Cause: Connection could not be established to a Connection Manager. This may be because the Connection Manger (Interchange) specified is not running or the Connection Manger addresses are incorrect.

Action: Make sure that the Connection Manager is running by using the STATUS command of the Interchange Control Utility; if necessary, start the Connection Manager using the START command of the Interchange Control Utility. If it is running and the error persists, contact Worldwide Customer Support.
TNS-00010 INTCTL: Error while flushing NS context

Cause: Internal NS error; connection may be lost.

Action: Make sure the connection is properly established. If the error persists, then contact Worldwide Customer Support.
TNS-00011 INTCTL: error while starting the Connection Manager

Cause: The Connection Manager could not be started.

Action: Assure that the executable can be found in the standard Oracle executable area. Check the configuration file INTCHG.ORA for errors and confirm that no other process is using the ADDRESS(es) for this Connection Manager as specified in TNSNET.ORA.

MultiProtocol Interchange Administrator's Guide

TNS-00012 INTCTL: error while processing Connection Manager request

Cause: An improper command was sent to the Connection Manager or it is not responding. Not normally visible to the user.

Action: Verify that the correct addresses are listed in the TNSNAMES.ORA, TNSNET.ORA, and TNSNAV.ORA configuration files. Also check that the Connection Manager is running by using the STATUS command of the Interchange Control Utility. If the error persists, contact Worldwide Customer Support.
TNS-00013 INTCTL: error while performing NS disconnect command

Cause: Internal NS error. Error in closing down connections.

Action: Make sure the networking protocol being used is properly installed on the machine. If the error persists, contact Worldwide Customer Support.
TNS-00014 INTCTL: error while opening terminal input channel

Cause: Could not open standard terminal input. Internal error.

Action: Normally not visible to the user. Restart the INTCTL program. If error persists, contact Worldwide Customer Support.
TNS-00015 INTCTL: error while closing terminal input channel

Cause: Could not close terminal input channel. Internal error.

Action: Normally not visible to the user. Restart the INTCTL program. If the error persists, contact Worldwide Customer Support.
TNS-00016 INTCTL: error while performing NS send command

Cause: Internal NS error. Connection may be lost.

Action: If error persists contact Worldwide Customer Support.
TNS-00017 INTCTL: error while performing NS receive command

Cause: Internal NS error. Connection may be lost.

Action: If error persists contact Worldwide Customer Support.
TNS-00018 INTCTL: TNS_ADMIN not defined

Cause: The TNS_ADMIN pointer is improperly set.

Action: No action necessary; TNS_ADMIN need only be set if you want to use a different network environment.
TNS-00019 INTCTL: error initializing the national language interface

Cause: The message file could not be found.

Action: Make sure that the ORACLE environment is set and that the message file is in the correct place.
TNS-0020 INTCTL: missing NAVIGATOR_DATA in TNSNAV.ORA

Cause: TNSNAV.ORA does not contain the NAVIGATOR_DATA component.

Action: Define the ADDRESS(es) for the Navigator, then restart the INTCTL program.
TNS-0021 INTCTL: missing INTERCHANGE_DATA in INTCHG.ORA

Cause: INTCHG.ORA does not contain an INTERCHANGE_DATA component.

Action: Define the correct data for the Connection Manager, then restart the INTCTL program.
TNS-00022 INTCTL: missing CMANAGER_NAME in INTCHG.ORA

Cause: The file INTCHG.ORA does not contain a CMANAGER_NAME component.

Action: Define the correct name for the CMANAGER_NAME, then restart the INTCTL program. Use of the Oracle Network Manager should eliminate this error.
TNS-00023 INTCTL: missing ADDRESS(es) in config files

Cause: onfiguration files do not contain an ADDRESS/ADDRESS_LIST component.

Action: Define the Connection Manager ADDRESS(es) in the TNSNET.ORA file and check the Navigator ADDRESS(es) in the TNSNAV.ORA file, then restart the INTCTL program.
TNS-00024 INTCTL: unable to contact the Navigator to obtain Connection Manager address

Cause: The Navigator is not running.

Action: Verify that the Navigator is running by doing a status request on the Navigator (use the Interchange Control Utility command STATUS). If necessary, start the Navigator, using the Interchange Control Utility. Verify that the network is properly configured; if possible, use the Oracle Network Manager to generate the configuration files. If the error persists, contact Worldwide Customer Support.
TNS-00025 INTCTL: the ORACLE environment is not set up correctly

Cause: The ORACLE environment is incorrectly set up.

Action: Refer to the Oracle operating system specific documentation for your platform for information on how the ORACLE environment should be set. Correct it and rerun INTCTL. Make sure the ORACLE environment includes the correct directories.
TNS-00026 INTCTL: TNS_ADMIN directory set, and is being used

Cause: The TNS_ADMIN environment variable is set properly. INTCTL will use the TNS_ADMIN directory. This is only an informative message. If you do not want it to be used, and want the default directory to be used instead, then unset TNS_ADMIN and reexecute.

Action: None.
TNS-00027 INTCTL: could not resolve Navigator's name/address

Cause: The Navigator's name to address definition is missing.

Action: Check TNSNAMES.ORA file and make sure to include a definition for the name specified.
TNS-00028 INTCTL: could not resolve Connection Manager's name/address

Cause: The Connection Manager's name does not have a definition that the Navigator knows about, nor is the name/address available in the TNSNAMES.ORA file. The name may also be incorrect in the INTCHG.ORA file.

Action: Verify that the Connection Manager's name is in the TNSNET.ORA file read by the Navigator or in the TNSNAMES.ORA file. Be sure that INTCHG.ORA is correct.
TNS-00031 INTCTL: internal NT error

Cause: Problem interfacing to the protocol adapters installed.

Action: Normally not visible to the user. Try starting INTCTL again. If the error persists, check the product installation. If it is correct, contact Worldwide Customer Support.
TNS-00032 INTCTL:internal NS error

Cause: Problem interfacing with TNS.

Action: Normally not visible to the user. Try starting INTCTL again. If the error persists, check the product installation. If it is correct, contact Worldwide Customer Support.
TNS-00033 INTCTL:internal NL error

Cause: Problem with internal TNS module NL.

Action: Normally not visible to the user. Try starting INTCTL again. If the error persists, check the product installation. If it is correct, contact Worldwide Customer Support.
TNS-00034 INTCTL :internal NR error

Cause: Problem with internal Interchange routines.

Action: Normally not visible to the user. Try starting INTCTL again. If the error persists, check the product installation. If it is correct, contact Worldwide Customer Support.
TNS-00035 INTCTL: error while constructing full file name

Cause: Problem while constructing the full path for a file name because the path name to the file or the environment variables are incorrect. Files looked up include TNSNAMES.ORA, TNSNAV.ORA, INTCHG.ORA, and the error files for the Navigator and Connection Manager.

Action: Check that all environment variables are defined correctly and that all configuration files exist in their correct places.
TNS-00036 INTCTL: error reading from Navigator or Connection Manager error files

Cause: Problem while reading from error files generated by the Navigator or Connection Manager when they fail to start.

Action: Check that a standard Network Error directory exists and that all privileges on the directory are appropriate.
TNS-00037 INTCTL: error opening Navigator or Connection Manager error files

Cause: Failed to open Navigator or Connection Manager error files when they have failed to start.

Action: Check that a Network Error directory exists and that all privileges on the directory are appropriate.
TNS-00038 INTCTL: poorly formed address or command string

Cause: An unacceptable string was encountered while attempting to send a message to either the Navigator or Connection Manager. The addresses provided for either the Navigator or Connection Manager may be incorrectly constructed.

Action: Check all address strings in configuration files (TNSNAMES.ORA, TNSNAV.ORA, or TNSNET.ORA) and assure that they are properly formed. Regenerate the files using the Oracle Network Manager, if possible. If all addresses are correct and the problem persists, please contact Worldwide Customer Support.
TNS-00039 INTCTL: error while spawning a process

Cause: An error was encountered while spawning a process, due to an internal operating system dependent problem. Machine resources may be limited.

Action: Retry command. Check permissions on Interchange executables and the current setting of the search path. If necessary, terminate other applications to free up machine resources. If the error persists, contact Worldwide Customer Support.
TNS-00040 INTCTL: failed to initialize trace context- Continuing anyway

Cause: Problem while opening specified trace file because of errors in INTCHG.ORA or because the user has incorrect privileges, or the file does not exist.

Action: Check the privileges on the configuration files and ensure that all of them exist in their proper locations.
TNS-00041 INTCTL: Navigator already running. Start operation cancelled

Cause: There is a Navigator already running and listening on the same addresses.

Action: None; the Navigator is already running.
TNS-00042 INTCTL: Cmanager already running. Start operation cancelled

Cause: There is a Connection Manager already running and listening on the same addresses.

Action: None; the Connection Manager is already running.
TNS-00043 INTCTL: the CMANAGER has active connections, do you still want to stop it (y/n)?

Cause: The CMANAGER that is being stopped has active connections going through. This is a confirmation message.

Action: Respond by pressing y or n. Answering y will cause the active database connection to be dropped; this is not generally recommended.
TNS-00044 INTCTL: you must have an INTCHG.ORA file to contact the Connection Manager

Cause: There was an attempt to contact a default Connection Manager (Interchange) where there was no INTCHG.ORA present in the correct directory.

Action: Create an INTCHG.ORA file using the Oracle Network Manager and make sure it is placed in the correct directory and includes the correct name for the Connection Manager you wish to contact.
TNS-00045 INTCTL: could not contact the Navigator on address

Cause: There was an attempt to contact a Navigator on a specific address, which is not responding.

Action: Check that a TNSNAV.ORA file containing the correct local communities exists for that address. Also check that the Navigator is actually listening on that address by using the INTCTL STATUS command. If necessary, start the Navigator using the INTCTL START command.
TNS-00046 INTCTL: Could not contact the Connection Manager on address

Cause: There was an attempt to contact a CMANAGER on a specific address, which is not responding.

Action: Verify that the TNSNET.ORA file contains that address. Also check that the CMANAGER is actually listening on that address by using the INTCTL STATUS command. If necessary, start the Connection Manager using the INTCTL START command.
TNS-00060 INTCTL: Bad command: only the STATUS command can be used on remote Interchanges

Cause: The user entered a command that does not exist, or the user tried to make a request other than STATUS to a remote Interchange.

Action: Check the MultiProtocol Interchange Administrator's Guide for a list of INTCTL commands or type HELP for a list of valid commands.
TNS-00061 INTCTL: Bad command or syntax error: you must specify a trace level

Cause: The user did not specify a trace level.

Action: Specify a trace level and retry command.
TNS-00062 INTCTL: Bad command or syntax error: For help type "help" or "h" or "?"

Cause: The user entered an invalid command.

Action: Check the MultiProtocol Interchange Administrator's Guide or type HELP for a list of valid commands.
TNS-00063 INTCTL: Failed to allocate memory for buffers

Cause: INTCTL was unable to allocate memory for internal buffers.

Action: Check the amount of available memory on your machine to ensure that there is enough memory to run this executable. If necessary, free up memory by running fewer programs, then try again.
TNS-00064 INTCTL: Failed to find CMANAGER_NAME in INTCHG.ORA

Cause: INTCTL was unable to find the CMANAGER_NAME parameter in INTCHG.ORA.

Action: Check that the INTCHG.ORA file is properly constructed.
TNS-00065 INTCTL: Command cannot be executed remotely

Cause: A command other than status and version has been attempted remotely.

Action: If you desire to execute any command other that status and version, you must run INTCTL on the Interchange machine.

Interchange Error Messages (TNS-00100 to 00499)

TNS-00100 Unable to allocate memory

Cause: Error in accessing, reading, or writing a particular file.

Action: Check the existence of, or operating system access to, the log and trace file locations.
TNS-00102 Keyword-Value binding operation error

Cause: Not normally visible to the user. May indicate a shortage of memory.

Action: If error persists contact Worldwide Customer Support.
TNS-00103 Parameter file load error

Cause: Parameter file process failed.

Action: Check to make sure that all parameter files necessary for the Interchange are present (TNSNAV.ORA, TNSNET.ORA and INTCHG.ORA). If these files are present and properly configured, turn on tracing and repeat the operation. Turn off tracing when the trace is complete. Look in the trace file for errors in the parameter loading process. If error persists contact Worldwide Customer Support.
TNS-00104 Data stream open/access error

Cause: Unable to open or access data stream for either log or trace files for the Interchange.

Action: Check read/write permissions on Oracle trace and log files and directories. Check for sufficient available space on disk.
TNS-00105 Could not initialize tracing

Cause: The INTCHG.ORA file is improperly configured. Verify the trace parameters specified in INTCHG.ORA.

Action: If error persists contact Worldwide Customer Support.
TNS-00106 Failed to open log file

Cause: Unable to access or obtain write permission to create log file.

Action: Check existence of or access to log file directory.
TNS-00107 Unable to initialize TNS global data

Cause: Not normally visible to the user. This error may be caused by insufficient memory on machine

Action: Add more resources. If error persists contact Worldwide Customer Support.
TNS-00108 TNS_ADMIN not defined

Cause: TNS_ADMIN pointer is not set.

Action: Set the TNS_ADMIN pointer before running application.
TNS-00109 Message could not be printed; not enough memory

Cause: Printing of message failed due to lack of memory. Not normally visible to the user.

Action: Increase the resources on your machine. If error persists contact Worldwide Customer Support.
TNS-00110 Could not initialize network from file TNSNET.ORA

Cause: Poorly formed network information in network file.

Action: Check network configuration data to assure that at least one Interchange is defined in TNSNET.ORA. Regenerate the file using the Oracle Network Manager if possible.
TNS-00111 Failed to get configuration data from TNSNET.ORA or TNSNAV.ORA

Cause: Poorly formed configuration information in network files TNSNET.ORA or TNSNAV.ORA.

Action: Check TNSNET.ORA and TNSNAV.ORA to confirm that they are correct.
TNS-00112 Failed to find configuration file name

Cause: Name specified for configuration file was incorrect.

Action: Check for presence of the configuration file.
TNS-00113 Failed to open error log file

Cause: Could not open error log file during startup of Navigator or Connection Manager due to read or write permission problems or non-existent error directory.

Action: Create the standard error directory or assure that if one is present the Interchange executables can write to it.
TNS-00114 Internal error- Allocation of addresses not performed

Cause: Internal error. Should not normally occur.

Action: Contact Worldwide Customer Support.
TNS-00115 Could not allocate pump global buffers

Cause: Not enough memory to allocate pump buffers.

Action: Decrease the number of PUMP_BUFFERS in INTCHG.ORA.
TNS-00116 Pump failed during initial bequeath

Cause: Error in assigning connection to a new pump. This error may be caused by insufficient machine resources.

Action: Attempt the connection again. The pump should recover from such a failure. If machine resources appear to be the problem, add more resources or shut down some active applications. If the problem persists, contact Worldwide Customer Support.
TNS-00117 Internal error- No data passed through pump

Cause: Internal error. Data expected has not arrived yet.

Action: If error persists, contact Worldwide Customer Support.
TNS-00119 Missing PUMP_CONNECTIONS in INTCHG.ORA

Cause: No PUMP_CONNECTIONS parameter specified in INTCHG.ORA.

Action: Add PUMP_CONNECTIONS parameter to INTCHG.ORA. If the file is generated by the Oracle Network Manager, this error should not occur.
TNS-00120 Missing PUMPS in INTCHG.ORA

Cause: No PUMPS parameter specified.

Action: Add an appropriate number of PUMPS to INTCHG.ORA. Use the Oracle Network Manager to generate the configuration files.
TNS-00121 Missing CMANAGER_NAME in INTCHG.ORA

Cause: No CMANAGER_NAME specified in INTCHG.ORA.

Action: Define the CMANAGER_NAME parameter in INTCHG.ORA; it must match the CMANAGER_NAME parameter used in TNSNET.ORA for that Interchange. This will happen automatically if the Oracle Network Manager is used.
TNS-00122 Missing ADDRESS(es) in TNSNET.ORA file

Cause: No ADDRESS or ADDRESS_LIST parameter specified in TNSNET.ORA.

Action: Define a valid set of ADDRESSes for the Connection Manager in the TNSNET.ORA file.
TNS-00123 Unable to perform a listen on configured ADDRESS(es)

Cause: Another process is already listening on this address or the ADDRESS is incorrectly defined.

Action: Check the ADDRESS(es) defined in TNSNET.ORA (for the Connection Manager) for errors. Verify that another program is not using them.
TNS-00124 Internal error - Unable to create empty address

Cause: Internal error. Should not normally occur.

Action: If problem persists contact Worldwide Customer Support.
TNS-00125 Failed to get number of Interchanges in TNSNET.ORA

Cause: Error in the TNSNET.ORA file.

Action: Check the contents of TNSNET.ORA and eliminate errors. Regenerate TNSNET.ORA using the Oracle Network Manager.
TNS-00126 Missing Connection Manager name and address in TNSNET.ORA

Cause: The Interchange name specified in INTCHG.ORA is not defined in the TNSNET.ORA file.

Action: Define one Connection Manager name and set of addresses for each Interchange in the network. Regenerate the SQL*Net configuration files using the configuration tool.
TNS-00127 Missing Connection Manager name in TNSNET.ORA

Cause: One or more Connection Manager names are missing from TNSNET.ORA.

Action: Ensure that each Connection Manager name is defined in TNSNET.ORA. Regenerate TNSNET.ORA using the Oracle Network Manager.
TNS-00128 Missing COMMUNITY in TNSNET.ORA

Cause: One or more ADDRESSes do not have a COMMUNITY assigned.

Action: Ensure that all addresses have a COMMUNITY defined in TNSNET.ORA.
TNS-00129 Internal error - Failed to create new community

Cause: Internal Error. Should not normally occur. There may be a resource limitation problem on the machine.

Action: Stop and restart Interchange. If possible, make more memory available on the machine. If problem persists, contact Worldwide Customer Support.
TNS-00130 Failed to create Interchange's internal address

Cause: There is an error in one of the addresses listed in TNSNET.ORA.

Action: Check the file for errors in defining Interchanges.
TNS-00131 Missing COMMUNITY in COMMUNITY_COST_LIST in TNSNET.ORA

Cause: A COMMUNITY keyword-value pair is missing within the COMMUNITY_COST_LIST in TNSNET.ORA.

Action: Define the communities with a COMMUNITY name and associated COST in COMMUNITY_COST_LIST.
TNS-00132 COST value must be an integer greater than 0

Cause: A community has been defined in TNSNET.ORA with a COST of 0.

Action: Assign an alternate value that is greater than 0.
TNS-00133 Missing LOCAL_COMMUNITIES field in TNSNAV.ORA

Cause: Improperly configured TNSNAV.ORA file.

Action: Define the LOCAL_COMMUNITIES fields correctly in TNSNAV.ORA.
TNS-00135 Missing TNS error message file

Cause: No error message file is present.

Action: Ensure that the ORACLE environment is correctly set for your platform and that there is a message directory that contains the correct error message file.
TNS-00136 Did not register product/facility for TNS error message

Cause: Error message file error.

Action: Ensure that the ORACLE environment is correctly set for your platform and that there is a message directory that contains the correct error message file.
TNS-00137 Failed to get TNS error message file entry

Cause: No TNS error message file present.

Action: Ensure that the ORACLE environment is correctly set for your platform and that there is a message directory that contains the correct error message file.
TNS-00138 Failed to find ORACLE executable directory

Cause: The ORACLE environment is not correctly set.

Action: Ensure that the ORACLE environment is correctly set and the error messages file is in the correct place.
TNS-00139 Internal - Data passed from the Interchange listener is poorly formed

Cause: Internal error in Interchange.

Action: Check that you are using compatible components of the Interchange product, using the INTCTL VERSION command. If the problem persists, call Worldwide Customer Support.
TNS-00140 Interchange specified was not found in network tables

Cause: Could not find the Interchange specified in a control request.

Action: Check that the Interchange specified is in TNSNET.ORA.
TNS-00141 Failed to get file stream information

Cause: Error in the file stream package.

Action: None.
TNS-00144 PUMP_CONNECTIONS value in INTCHG.ORA is too large

Cause: The number of PUMP_CONNECTIONS specified in INTCHG.ORA is too large to be supported on this platform.

Action: Consult the Oracle operating system specific manual for the value for the number of PUMP_CONNECTIONS.
TNS-00145 PUMPS value in INTCHG.ORA is too large

Cause: The number of PUMPS specified in INTCHG.ORA is too large to be supported on this platform.

Action: Consult the Oracle operating system specific manual for the value for the number of PUMP_CONNECTIONS.
TNS-00146 Internal-- Retry data request within pump

Cause: The data space provided in order to receive data from the pump is too small.

Action: Operation must be retried with a larger buffer.
TNS-00147 Failed to start a pre-spawned pump

Cause: The Connection Manager was unable to start a pump during startup.

Action: Check all configuration parameters and assure that they are correct. Turn on tracing to determine the area that the failure ocurred in.
TNS-00200 Unable to do nsanswer on context: result=string

Cause: Requester of service may have aborted or options negotiation failed.

Action: Try making the connection again. If the problem persists call Worldwide Customer Support.
TNS-00201 Unable to read answer connection data: string

Cause: Improperly formed connect data sent to the Interchange listener.

Action: If problem persists, check the application using the Interchange (it may be closing down or crashing). Call Worldwide Customer Support.
TNS-00202 Failure in redirecting call: Original to string Redirect to string

Cause: Internal error: could not redirect call to a pump or other Interchange listener. The cause may be insufficient network or machine resources.

Action: Add resources or close some running applications in order to free up resources. If error persists, call Worldwide Customer Support.
TNS-00203 Unable to start tracing in intlsnr

Cause: Failure in setting up tracing for Interchange listener.

Action: Check file permissions in Network trace directory. Also check to make sure that if trace file names and directories are specified in INTCHG.ORA, they are correct.
TNS-00224 No more connections available

Cause: More connections were attempted to the Interchange than are configured in INTCHG.ORA.

Action: Wait until the Interchange is not as busy or change the number of connections allowed in INTCHG.ORA and restart the Interchange.
TNS-00225 Unable to bequeath connection to pump

Cause: Unable to start a pump because either the executable cannot be found or too many processes are currently running on a particular machine.

Action: Reduce the number of processes on the machine or increase the resources on the machine.
TNS-00226 Unable to contact pump num to send broadcast message string

Cause: Could not call a particular pump.

Action: None, but if the problem persists, call Worldwide Customer Support.
TNS-00227 Unable to contact pump; Connection Manager declared pump dead

Cause: A pump became an orphaned process. A protocol adapter is not working properly or machine network resources are being overused.

Action: This error is not immediately fatal; the orphaned pump may continue to function. Restart the Interchange when convenient. If the problem persists, call Worldwide Customer Support.
TNS-00228 Failure in finding pump data

Cause: Internal problem with data passed back from pump

Action: None.
TNS-00229 Error in nscall: unable to deliver message: string: error num

Cause: Destination for call is unavailable.

Action: None.
TNS-00230 Cannot start new pump process: error string

Cause: Unable to create a new process; possibly there are too many processes on the machine.

Action: Free machine resources by exiting other applications on the Interchange machine. If the problem continues you may need more memory on the machine. If you believe there are sufficient resources on the machine but the problem persists, contact Worldwide Customer Support.
TNS-00232 Unable to set up connection

Cause: Error log message sent from pump to indicate failure in initiating connection because of errors in the call string: network problem or resource limitations.

Action: None.
TNS-00233 Interchange failed to make contact with destination with errors: string

Cause: Pump call to destination failed.

Action: Check destination.
TNS-0235 Aborting connection: Protocol Adapter errors:error error

Cause: Pump aborting connection because connection has been up too long, or there is some other network error on the connection.

Action: None.
TNS-00236 Failed to initialize tracing

Cause: Pump failed to initialize tracing.

Action: Check that INTCHG.ORA is properly configured.
TNS-00237 Failed to refuse connection

Cause: Connection may have aborted before error took place in pump.

Action: None.
TNS-00245 Connection Manager: Failed to open log file

Cause: Message sent back to control program from Interchange.

Action: None.
TNS-00246 Connection Manager: Failed to start tracing

Cause: Message sent back to control program from Interchange.

Action: None.
TNS-00247 Unable to allocate memory for configuration data from TNSNET.ORA file

Cause: Navigator failed to allocate enough memory for TNSNET.ORA configuration file.

Action: Increase machine resources available for running the Interchange or remove some other running applications from the machine.
TNS-00248 Unable to get information from file: string: Exiting with NR error: string

Cause: TNSNAV.ORA is poorly configured or addresses provided are already being used by another application.

Action: Check the syntax of the TNSNAV.ORA file; if necessary, assign new addresses.
TNS-00249 Unable to read network configuration data from file: string NR error: string

Cause: Network configuration file TNSNET.ORA is missing or poorly configured.

Action: Check to make sure that TNSNET.ORA is properly configured.
TNS-00251 Failure in nstest

Cause: NS test operation failed due to internal error.

Action: If the problem persists there may be a network problem or resource limitations on the machine. If these do not seem to be causing the problem, call Worldwide Customer Support.
TNS-00252 Unable to handle route request

Cause: Command requested did not exist.

Action: None.
TNS-00253 Error in reading network configuration data from file string NR error string

Cause: TNSNET.ORA is poorly configured or nonexistent.

Action: Check to make sure that TNSNET.ORA is properly configured.
TNS-00305 The Navigator encountered an invalid/unknown trace level

Cause: Message sent back by the Navigator indicating an invalid trace level.

Action: Reattempt the request with a correct trace level.
TNS-00306 Connection Manager encountered an invalid/ unknown trace level

Cause: Message sent back by the Connection Manager indicating an invalid trace level.

Action: Reattempt the request with a correct trace level.
TNS-00308 Navigator: Failed to open log while rereading parameter data

Cause: Request sent by the Navigator to control program indicating that it could not reopen log file after rereading parameter data.

Action: None.
TNS-00309 Connection Manager: Failed to open log while rereading parameter data

Cause: Request sent by the Connection Manager to control program indicating that it could not reopen log file after rereading parameter data.

Action: None.
TNS-00310 Navigator: Failed to start tracing after rereading parameter data

Cause: Message sent back to control program from Navigator.

Action: None.
TNS-00311 Connection Manager: Failed to start tracing after rereading parameter data

Cause: Message sent back to control program from Connection Manager.

Action: None.
TNS-00312 Connection Manager: Failed to get version information

Cause: Message sent back to control program from Connection Manager.

Action: None.
TNS-00313 Navigator: Failed to get version information

Cause: Message sent back to control program from Navigator.

Action: None.
TNS-00315 Failed to allocate larger connect data area for getting pump data:

Cause: Could not allocate a large enought area to get pump statistics; continue without them.

Action: None
TNS-00316 Ran out of data buffers in the pump

Cause: The Interchange is resource limited by having too few data buffers in the pump.

Action: If the problem persists (that is, if there are a lot of log messages), increase the number of pump buffers by increasing the value of the parameter PUMP_BUFFERS in INTCHG.ORA. Then shutdown and restart the Interchange to make the changes take effect.
TNS-00317 Failed to contact Connectio Manager

Cause: Connection Manager is not running.

Action: Start the Connection Manager and retry.

NT Error Messages (TNS-00501 to 00999)

TNS-00501 Cannot allocate memory

Cause: Sufficient memory could not be allocated to perform the desired activity.

Action: Either free some resource for TNS or add more memory to the machine. For further details, turn on tracing and reexecute the operation.
TNS-00502 Invalid argument

Cause: An internal function received an invalid parameter.

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-00503 Illegal ADDRESS parameters

Cause: An illegal set of protocol adapter parameters was specified.

Action: Check the parameters within the ADDRESS section of the TNSNAMES.ORA file. It may be helpful to turn on tracing and look at the addresses specified in the trace file, checking for spelling or other errors. Be sure to turn tracing off when the trace is complete.
TNS-00504 Operation not supported

Cause: An internal function received a request to perform an operation that is not supported (on this machine).

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-00505 Operation timed out

Cause: The requested operation could not be completed within the timeout period.

Action: For further details, turn on tracing and reexecute the operation.
TNS-00506 Operation would block

Cause: An internal operation did not commence because to do so would block the current process and the user has requested that operations be non-blocking.

Action: None needed; this is an information message.
TNS-00507 Connection closed

Cause: Normal "end of file" condition has been reached; partner has disconnected.

Action: None needed; this is an information message.
TNS-00508 No such protocol adapter

Cause: The protocol adapter requested for this connection does not exist.

Action: Install the protocol adapter or use one that is available. Be sure that the correct protocols are listed in the configuration files.
TNS-00509 Buffer overflow

Cause: Too much data for buffer.

Action: Reexecute with larger receive buffer or smaller send buffer.
TNS-00510 Internal limit restriction exceeded

Cause: Too many files or sockets open simultaneously (or some other resource has been depleted).

Action: For further details, trace the operation for protocol details.
TNS-00511 No listener

Cause: The connection request could not be completed because no application is listening on the address specified, or the application is unable to service the connect request in a sufficiently timely manner.

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-00512 Address already in use

Cause: Specified listener address is already being used.

Action: Start your listener with an unused address.
TNS-00513 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-00514 Contexts have different wait/test functions

Cause: Two protocol adapters have conflicting wait/test functions.

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-00515 Name lookup failure

Cause: A protocol specific ADDRESS parameter cannot be resolved.

Action: Ensure the ADDRESS parameters have been entered correctly; the most likely incorrect parameter is the node name.
TNS-00516 Permission denied

Cause: User has insufficient privileges to perform the requested operation.

Action: Acquire necessary privileges and try again.
TNS-00517 Lost contact

Cause: Partner has unexpectedly gone away.

Action: Investigate partner application for abnormal termination.
TNS-00518 Incomplete read or write

Cause: A data send or receive failed.

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-00519 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.
TNS-00520 Syntax error

Cause: The supplied connect descriptor contains illegal syntax.

Action: Check the syntax of the connect descriptor for correct syntax.
TNS-00521 Missing keyword

Cause: The supplied connect descriptor is missing one or more TNS keywords.

Action: Check the syntax, and ensure all required keywords are present.
TNS-00522 Operation was interrupted

Cause: An internal operation was interrupted and could not complete.

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-00523 Previous operation was busy

Cause: Operation tried could not be successfully completed because the requested resource was busy.

Action: Attempt the operation again. If the error persists, contact Worldwide Customer Support.
TNS-00524 Current operation is still in progress

Cause: Internal operation is still in progress but will complete.

Action: None; wait for operation to complete.
TNS-00525 Insufficient privilege for operation

Cause: Operating system failed to complete operation because user lacked sufficient privileges.

Action: Check your platform-specific privileges.
TNS-00526 No caller (false async event)

Cause: Internal error.

Action: For further details, turn on tracing and reexecute the operation.
TNS-00527 Protocol Adapter not loadable

Cause: On some platforms (for example 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 have the name of the shared library (or DLL) that could not be loaded.
TNS-00528 Protocol Adapter not loaded

Cause: On some platforms (for example 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.
TNS-00530 Protocol adapter error

Cause: A generic protocol adapter error occurred.

Action: For further details, turn on tracing and reexecute the operation.
TNS-00532 No previous async operation to wait on

Cause: Internal protocol adapter error.

Action: For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.
TNS-00533 Connection dissolved or not yet made

Cause: The network services on or from your node are not running or have stopped running.

Action: Restart your network and protocol services on this platform. If error persists, contact Worldwide Customer Support.

Listener Error Messages (TNS-01000 to 02500)

TNS-1064 Listener configuration changes will not be persistent

Cause: Configuration changes to the listener will not be visible when the listener starts up again as the check-pointing has been turned off in listener.ora

Action: Edit LISTENER.ORA setting USE_CKPFILE_LISTENER=true
TNS-01100 TNS returned error num when attempting to start the listener

Cause: The bequeath (BEQ) mechanism that LSNRCTL uses to start the listener failed.

Action: Check to ensure that the BEQ driver is installed - if it is not then the nserror code returned will be 12538 (NSENODRIVER). To fix this, reinstall SQL*Net V2 and make sure that the BEQ driver is selected when it is installed. If this is not the problem then the error is probably caused by the fact that the TNSLSNR executable cannot be found in the place expected in your platform's ORACLE environment. Verify that the full pathname of the TNSLSNR executable as displayed by LSNRCTL is correct.
TNS-01101 Could not find service name string

Cause: The service name could not be resolved by name-lookup.

Action: Verify that the listener name or service name specified to LSNRCTL has the correct name and address defined in LISTENER.ORA or in TNSNAMES.ORA.
TNS-01102 TNS application contacted was not the listener

Cause: Another TNS application such as the Interchange was listening at the address contacted. There may be another TNS application listening at the address contacted and the data returned is not in the appropriate format.

Action: Verify that the listener name or service name specified to LSNRCTL has the correct name and address defined in LISTENER.ORA or in TNSNAMES.ORA.
TNS-01103 Protocol specific component of the address is incorrectly specified

Cause: The ADDRESS used to contact the listener is not correctly specified. This error occurs because the address fails to specify the destination of the listener. The address is well-formed (for example, there are no missing parentheses) but it is missing a protocol specific component. For example, this is the error returned when the HOST component is missing from a TCP/IP address string.

Action: Edit the ADDRESS in LISTENER.ORA to include the required protocol-specific keywords. For more information about the keywords required by different protocol adapters, see the Oracle operating system specific documentation for your platform.
TNS-01106 Listener using listener_name listener_name has already been started

Cause: Another listener is already listening on one of the ADDRESSes specified.

Action: Shutdown the previous listener specified by the listener_name before starting this one.
TNS-01107 A valid trace level was not specified

Cause: Failed to specify a valid trace level for the LSNRCTL trace command.

Action: Specify one of OFF, USER, or ADMIN. Type "lsnrctl help trace" for more information or consult Chapter 2 of this manual for an introduction to the concepts of tracing.
TNS-01108 Listener password prompt failed

Cause: Password not entered via tty.

Action: Enter the listener password on a tty device.
TNS-01109 Listener password encryption failed

Cause: Possibly garbled password entered.

Action: Re-enter the listener password, using valid ASCII characters. If problem persists, contact Worldwide Customer Support.
TNS-01110 Mismatch - password unchanged

Cause: New password and reentered new password are different

Action: Re-enter the listener password, make sure that New password and reentered new password are the same
TNS-01111 Log status can either be ON or OFF

Cause: Failed to specify a log status value for the LSNRCTL log_status command.

Action: Specify one of ON or OFF. Type "LSNRCTL help set log_status" for more information or consult Chapter 2 of this manual for an introduction to the concepts of logging.
TNS-01150 The address of the specified listener name is incorrect

Cause: The address on which the listener attempted to listen contains a syntax error.

Action: For the listener name or service name specified to LSNRCTL, check that the address or connect descriptor is well-formed. You can find the listener name in LISTENER.ORA, or you can access the listener through the service name in TNSNAMES.ORA.
TNS-01151 Missing listener name listener_name in LISTENER.ORA

Cause: The listener could not find the listener name specified.

Action: Make sure that valid addresses on which to listen are specified for the listener name in LISTENER.ORA.
TNS-01152 All addresses specified for the listener name listener_name failed

Cause: The listener failed to listen on any of the specified addresses.

Action: Make sure that another application is not listening on the addresses specified or check that the appropriate protocol adapters are installed. Turn on tracing and execute again for more information.
TNS-01154 SID detected in old format that is no longer supported

Cause: One of the SIDs was specified in an obsolete format.

Action: Check LISTENER.ORA for a line of the form:

sid

oracle_home

sid

oracle_home

listener_name

SQL*Net Administrator's Guide

sid

oracle_home

TNS-01155 Incorrectly specified SID_LIST_listener_name parameter in LISTENER.ORA

Cause: SID_LIST_listener_name in LISTENER.ORA contains an error.

Action: Be sure this parameter is specified as described in the SQL*Net Administrator's Guide. For example, (SID_LIST_LISTENER = (SID_DESC=(SID_NAME=sid) (ORACLE_HOME=oracle_home))).
TNS-01156 Missing or inappropriate PROTOCOL, TIMEOUT, or POOL_SIZE parameter from PRESPAWN_DESC

Cause: PRESPAWN_DESC in each SID_DESC does not have required fields.

Action: Be sure the parameters required for PRESPAWN_DESC are specified in each SID_DESC. For example:

SID_LIST_LISTENER = (SID_LIST= (SID_NAME=sid) (PRESPAWN_MAX=5) (ORACLE_HOME=oracle_home) (PRESPAWN_DESC=(PROTOCOL=tcp)(POOL_SIZE=10)(TIMEOUT=30))))

TNS-01157 Can only listen on num addresses - ignoring remaining addresses

Cause: Too many addresses were given to listen on.

Action: Reduce the number of addresses to listen on and use another listener to listen on the remaining addresses.
TNS-01158 Internal connection limit has been reached, preventing dispatcher from connecting

Cause: The internal SQL*Net connection list is full. Too many dispatchers are connected to the listener; therefore, no more dispatchers are allowed to connect.

Action: For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.
TNS-01159 Internal connection limit has been reached; listener has shut down

Cause: The internal SQL*Net connection list is full. The listener is configured to use too many SQL*Net connections.

Action: Reduce the number of listen addresses or services connected to the listener. For further details, turn on tracing and reexecute to operation. If error persists, contact Worldwide Customer Support.
TNS-01167 The command string is not supported by the listener contacted

Cause: The listener does not recognize the command.

Action: This is caused when a newer version of LSNRCTL contacts an old listener. Upgrade listener if executing this command is important.
TNS-01168 Cannot allocate memory

Cause: Sufficient memory could not be allocated to perform the desired activity.

Action: Either free some resource for TNS, or add more memory to the machine. For further details, turn on tracing and reexecute the operation.
TNS-01169 The listener did not recognize the password

Cause: The security feature of the listener is preventing the intended operation.

Action: Some commands like stopping the listener are only intended to be used by DBAs. A client can only use LSNRCTL to get the status of a listener and the version of the listener software running. The command that the client attempted may not have been appropriate. If a DBA is attempting the command then use the "set password" command at the LSNRCTL prompt to one of the appropriate passwords in the PASSWORDS_listener_name entry in LISTENER.ORA. If you do not know a password then you are trying to execute an inappropriate command.
TNS-01170 Event detection broke for address: addrress

Cause: he event detection mechanism for the address specified returned an error.

Action: Future attempts to detect events on this address will fail. The listener will deallocate the listen address and connections will no long be accepted for this address. This error is not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.
TNS-01171 Event detection broke for dispatcher: dispatcher

Cause: The event detection mechanism for the dispatcher specified returned an error.

Action: Future attempts to detect events on this dispatcher will fail. The listener will deallocate the dispatcher and connections will no long be redirected to this dispatcher. This error is not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.
TNS-01172 Listener has shut down since all listen addresses have been deallocated

Cause: The event detection mechanism broke and caused all listen addresses to be removed.

Action: Error 1170 has occured and caused all the listen addresses to be deallocated. Since all the listen addresses have been removed, no more connections can be established to this listener so it shuts itself down. This error is not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.
TNS-01173 Missing or inappropriate PRESPAWN_MAX parameter from SID_DESC

Cause: PRESPAWN_MAX in each SID_DESC does not have required fields.

Action: Be sure the parameters required for PRESPAWN_DESC are specified in each SID_DESC. For example:

SID_LIST_LISTENER = (SID_LIST= (SID_NAME=sid) (PRESPAWN_MAX=15) (ORACLE_HOME=oracle_home) (PRESPAWN_DESC=(PROTOCOL=tcp)(POOL_SIZE=10)(TIMEOUT=30))))

TNS-1174 The sum of the POOL_SIZEsfrom each PRESPAWN_DESC is greater than the PRESPAWN_MAX

Cause: The minimum value for PRESPAWN_MAX should be the sum of the POOL_SIZEs in each SID_DESC. For example:

SID_LIST_LISTENER = (SID_LIST= (SID_NAME=sid) (PRESPAWN_MAX=15) (ORACLE_HOME=oracle_home) (PRESPAWN_DESC=(PROTOCOL=tcp)(POOL_SIZE=10)(TIMEOUT=30) (PRESPAWN_DESC=(PROTOCOL=icp)(POOL_SIZE=5)(TIMEOUT=30))))

TNS-01175 Password unchanged

Cause: Unable to set the new password.

Action: Be sure to see that the new password has legal ASCII characters. Try to set the password again.
TNS-01176 Error in loading the new parameter value

Cause: Illegal values given for the parameters.

Action: Make sure that the parameter values are valid. Refer to the manual for the legal values for parameters.
TNS-01177 Log Status is OFF. Log file/directory unchanged

Cause: Log status needs to be set ON for changing the log file

Action: Use command set log_status ON to set the log status of the listener ON.
TNS-01178 Trace Level is 0. Trace file/directory unchanged

Cause: Trace Levelneeds to be set for changing the trace file/directory.

Action: Use command set trc_level ON to set the trace level.
TNS-01200 The listener must be suid root

Cause: The ownership privileges of the TNSLSNR executable are incorrect.

Action: Contact your DBA or system administrator to change the ownership of the file to be suid root and restart the listener. This action is necessary because the user that started the process should claim ownership.

Comment: This error is reported only on Trusted Oracle platforms. TNS-01201 Listener cannot find executable string for SID string

Cause: The executable for the Oracle dedicated server process cannot be found.

Action: Check the appropriate SID_DESC in LISTENER.ORA to make sure that the ORACLE_HOME component is pointing to a valid location. If this component is not set, then check the value of the ORACLE_HOME environment variable.

Comment: This error is reported only on UNIX platforms. TNS-01202 Missing the dba group (string) specified by DBA_GROUP in SID_DESC

Cause: The dba group specified is missing from /ETC/GROUP.

Action: Check the DBA_GROUP parameter in the SID_DESC in LISTENER.ORA and verify it has a valid entry in /ETC/GROUP.

Comment: This error is reported only on UNIX platforms. TNS-01203 Missing the account string specified by DEFAULT_USER_ACCOUNT in SID_DESC

Cause: The unprivileged OS account is missing from /ETC/PASSWD.

Action: Check the DEFAULT_USER_ACCOUNT parameter in the SID_DESC in LISTENER.ORA and verify it has a valid entry in /ETC/PASSWD. This is the account that the ORACLE shadow process will be started with if the connecting client has database privileges or does not exist on this machine.

Comment: This error is reported only on UNIX platforms. TNS-01204 Unprivileged account string is in dba group string

Cause: The unprivileged account has DBA privileges. The unprivileged account specified by DEFAULT_USER_ACCOUNT in the SID_DESC in LISTENER.ORA is a member of the dba group specified by DBA_GROUP in the SID_DESC. The unprivileged account cannot belong to the dba group because this would be a security violation with OPS$ logins.

Action: Remove the unprivileged account from the dba group.

Comment: This error is reported only on UNIX platforms.

NA Internal Messages (TNS-02501 to 03500)

TNS-02501 Authentication: no more roles

Cause: When a process attempted to retrieve a role from the authentication service, no more were available.

Action: None. This error is used internally and occurs in the normal course of events.
TNS-02502 Authentication: unable to find initialization function

Cause: he native authentication service was unable to call the initialization function for the specified service because it does not exist.

Action: If this service adaptor came directly from Oracle, contact Worldwide Customer Support, as this error should never happen. Otherwise, add an initialization function for the service being used.
TNS-02503 Parameter retrieval failed

Cause: The native service layer was unable to retrieve a parameter from a configuration file.

Action: If it is possible, enable tracing and attempt to reproduce the problem. In any event, contact Worldwide Customer Support.
TNS-02504 Parameter count retrieval failed

Cause: The native service layer was unable to determine the number of arguments given for a configuration parameter.

Action: If it is possible, enable tracing and attempt to reproduce the problem. In any event, contact Worldwide Customer Support.
TNS-02505 Authentication: null context pointer provided

Cause: nau_ini() was passed a null pointer for the context that it is supposed to use.

Action: Call nau_ini() with a pointer to a context structure.
TNS-02506 Authentication: no type string

Cause: An authentication context structure does not contain a string that describes the authentication service being used.

Action: Contact Worldwide Customer Support
TNS-02507 Encryption: algorithm not installed

Cause: After picking an algorithm, the server was unable to find an index for it in its table of algorithms. This should be impossible because the algorithm was chosen (indirectly) from that list.

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-0208 Encryption: server negotiation response in error

Cause: The server's response in negotiation was in 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-02509 Authentication: invalid process state

Cause: The state in which a process is running does not correspond to any of the values which are valid.

Action: If it is possible, enable tracing and attempt to reproduce the problem. In any event, contact Worldwide Customer Support.
TNS-02510 Invalid numeric data type

Cause: The type of a piece of numeric data that was received does not correspond to one of the valid values.

Action: If it is possible, enable tracing and attempt to reproduce the problem. In any event, contact Worldwide Customer Support.
TNS-02511 Invalid data type

Cause: The type of a piece of data that was received or to be transmitted did not correspond to any of the correct values.

Action: If it is possible, enable tracing and attempt to reproduce the problem. In any event, contact Worldwide Customer Support.
TNS-02512 Invalid status received

Cause: A process received a value as a status flag which was unknown.

Action: If it is possible, enable tracing and attempt to reproduce the problem. In any event, contact Worldwide Customer Support.

TNS-02513 Requested data type does not match retrieved type

Cause: A service requested data whose type does not match that of the segment which was sent from the other process.

Action: If it is possible, enable tracing and attempt to reproduce the problem. In any event, contact Worldwide Customer Support.
TNS-02514 Invalid packet received

Cause: A process received a data packet which was not meant for the native services layer.

Action: If it is possible, enable tracing and attempt to reproduce the problem. In any event, contact Worldwide Customer Support.
TNS-02515 Encryption/crypto-checksumming: unknown control type

Cause: An encryption or crypto-checksumming algorithm "control" function was called, but did not recognize the "type" argument it was given.

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-02516 No data available

Cause: A native service attempt to retrieve data but no data was available to be received.

Action: The error is not normally visible as it usually is only used to signal the end of a data stream. If the error becomes visible, enable tracing to reproduce the problem and contact Worldwide Customer Support.
TNS-02517 Key smaller than requested size

Cause: The key returned by SNS key negotiation was smaller than the size requested by some service (either encryption or crypto-check-summing).

Action: The error is not normally visible. If the error persists, enable tracing, reproduce the problem, and contact Worldwide Customer Support.
TNS-02518 key negotiation error

Cause: An error occurred while the two sides of the connection were negotiating an SNS key.

Action: he error is not normally visible. If the error persists, enable tracing to reproduce the problem and contact Worldwide Customer Support.
TNS-02519 no appropriate key-negotiation parameters

Cause: No appopriate key-negotiation parameters are available for the key size requested either by encryption or by crypto-checksumming.

Action: The error is not normally visible. Enable tracing to reproduce the problem and contact Worldwide Customer Support.
TNS-02520 encryption/crypto-checksumming: no Diffie-Hellman seed

Cause: The "sqlnet.crypto_seed" parameter is missing from the SQLNET.ORA parameters file for SQL*Net.

Action: Add this line to SQLNET.ORA, perhaps by using Network Manager: sqlnet.crypto_seed = "randomly-chosen text"
TNS-02521 encryption/crypto-checksumming: Diffie-Hellman seed too small

Cause: The "sqlnet.crypto_seed" parameter in the SQLNET.ORA parameter file for SQL*Net is too small.

Action: Add more randomly-chosen text to it, perhaps using Network Manager.
TNS-02524 Authentication: privilege check failed

Cause: An error occurred when the SQL*Net authentication service attempted to verify that a user had a specific database privilege.

Action: This error should not happen normally. Enable tracing and attempt to repeat the error. Contact Customer Support.
TNS-02525 encryption/crypto-checksumming: self test failed

Cause: The SNS system detected an error while running tests on the active encryption or checksumming algorithm.

Action: Contact Customer Support.
TNS-02526 server proxy type does not match client type

Cause: The authentication type selected by the server does not match that picked by the client.

Action: Contact Worldwide Customer Support
TNS-03502 Insufficient arguments. Usage: tnsping <address> [<count>]

Cause: Some required command-line arguments are missing.

Action: Re-enter the command using the correct arguments.
TNS-03503 Could not initialize NL

Cause: The network library could not be initialized.

Action: This is an internal error which should not normally be visible. Ensure that memory is available to run the application and that there are no other operating system problems, and then attempt the command again.
TNS-03504 Service name too long

Cause: The service name you are attempting to ping is too long.

Action: Re-enter the command using the correct service name.
TNS-03505 Failed to resolve name

Cause: The service name you provided could not be found in TNSNAMES.ORA, an Oracle Names server, or a native naming service.

Action: Verify that you entered the service name correctly. You may need to ensure that the name was entered correctly into the network configuration using Oracle Network Manager.
TNS-03506 Failed to create address binding

Cause: The TNSPING utility found the requested address or service name, but received an internal error when trying to use it.

Action: This is an internal error which should not normally be visible. Ensure that memory is available to run the application and that there are no other operating system problems, and then attempt the command again.
TNS-03507 Failure looking for ADDRESS keyword

Cause: The TNS address did not contain an ADDRESS keyword.

Action: If you entered the TNS address on the command line, be sure that the syntax is correct. If you entered a service name on the command line, the address contains the wrong information. You should verify that the information was entered correctly with Oracle Network Manager.
TNS-03508 Failed to create address string

Cause: The TNSPING utility received an internal error when generating an address.

Action: This is an internal error which should not normally be visible. Ensure that memory is available to run the application and that there are no other operating system problems, and then attempt the command again.
TNS-03509 OK (decimal msec)

Cause: The operation succeeded, in this amount of time.

Action: No action necessary.
TNS-03510 Failed doe to I/O error

Cause: An I/O operation failed perhaps due to resource failure of premature window termination.

Action: This is an internal error which should not normally be visible. Do not close the TNSPING window before all I/O operations have completed.
TNS-03601 Failed in route information collection

Cause: The route could either not connect or encountered an unsupported version of SQL*Net.

Action: Check if SQL*Net along all node is version 2.3 or greater.
TNS-03602 Insufficient arguments. Usage: trcroute address

Cause: Some required command-line arguments are missing.

Action: Re-enter the command using the correct arguments.
TNS-03603 Encountered a node with pre-2.3 version of SQL*Net

Cause: Any version of SQL*Net before 2.3 doesn't support trcroute.

Action: Find the node that isn't responding to trcroute.

OSN Error Messages (ORA-12150 to 12195)

ORA-12150 TNS:Unable to send data

Cause: Unable to send data. Connection probably disconnected.

Action: Re-establish connection. If the error is persistent, turn on tracing and reexecute the operation.
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 TNS:Unable to send break message

Cause: Unable to send break message. Connection probably disconnected.

Action: Re-establish connection. If the error is persistent, turn on tracing and reexecute the operation.
ORA-12153 TNS:Not connected

Cause: Not currently connected to a remote host.

Action: Re-establish connection.
ORA-12154 TNS:Could not resolve service name

Cause: The service name specified is not defined in the TNSNAMES.ORA file.

Action: Make the following checks and correct the error:

Verify that a TNSNAMES.ORA file exists and is in the proper place and accessible. See the operating system specific manual for details on the required name and location.

Check to see that the service name exists in one of the TNSNAMES.ORA files and add it if necessary.

Make sure there are no syntax errors anywhere in the file. Particularly look for unmatched parentheses or stray characters. Any error in a TNSNAMES.ORA file makes it unusable. See Chapter 4 in the SQL*Net Administrator's Guide. If possible regenerate the configuration files using the Oracle Network Manager.

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 TNS:Tried to reset line from incorrect state

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 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 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 the DBA to get the proper permissions or use TRACE_DIRECTORY_CLIENT in SQLNET.ORA to specify a directory the user can write to.
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 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 TNS:service name is incorrectly specified

Cause: The connect descriptor corresponding to the service name in TNSNAMES.ORA is incorrectly specified.

Action: Make sure there are no syntax errors in the connect descriptor. Particularly look for unmatched parentheses or stray characters. Any error in the TNSNAMES.ORA file makes it unusable. See the SQLNet V2 Administrator's Guide.
ORA-12163 TNS:Connect descriptor is too long.

Cause: The connect descriptor corresponding to the service name in TNSNAMES.ORA is too long.

Action: The maximum length for a connect descriptor is 512 bytes and this limit has been exceeded. Use a smaller connect descriptor. If this is not possible, contact Worldwide Customer Support.
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 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 TNS:client cannot connect to HO agent

Cause: NVstring contained DESCRIPTION/HO.

Action: Call HO agent from integrating server.

NR Error Messages (ORA-12196 to 12285)

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 the TNSNAV.ORA file does not have a correct CMANAGER address specified, or the Interchange is down.

Action: Assure that the 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 refused the connection at the listener.

Action: Make sure that the 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 occurred 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.
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-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 to 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 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 ocurred 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.

TNS Listener Error Messages (ORA-12500 to 12530)

ORA-12500 TNS:listener failed to start a dedicated server process

Cause: The process of starting up a dedicated server process failed. The executable could not be found or the environment may be set up incorrectly.

Action: Turn on tracing at the ADMIN level and reexecute the operation. Verify that the ORACLE Server executable is present and has execute permissions enabled. Ensure that the ORACLE environment is specified correctly in LISTENER.ORA. If error persists, contact Worldwide Customer Support.
ORA-12502 TNS:listener received no CONNECT_DATA from client

Cause: No CONNECT_DATA was passed to the listener.

Action: Check that the service name resolved from TNSNAMES.ORA has the CONNECT_DATA component of the connect descriptor.
ORA-12504 TNS:listener was not given the SID in CONNECT_DATA

Cause: The SID was missing from the CONNECT_DATA.

Action: Check that the connect descriptor corresponding to the service name in TNSNAMES.ORA has an SID component in the CONNECT_DATA.
ORA-12505 TNS:Listener could not resolve SID given in connect descriptor

Cause: The SID in the CONNECT_DATA was not found in the listener's tables.

Action: Check to make sure that the SID specified is correct. The SIDs that are supported can be obtained by typing LSNRCTL STATUS SERVICE_NAME and matching the SID specified in TNSNAMES.ORA with one of the SIDs displayed in the services summary.
ORA-12509 TNS:listener failed to redirect client to service handler

Cause: The dispatcher terminated unexpectedly.

Action: Attempt to connect again and if the same error occurs, contact the DBA to check the state of the dispatchers for this SID. If the problem persists, turn on tracing in the listener to determine the TNS error caused by the redirect.
ORA-12510 TNS:database lacks resources to handle the request for this SID

Cause: The dispatchers are busy handling other requests.

Action: Contact the DBA to increase the number of dispatchers servicing this SID.
ORA-12511 TNS:service handler found but it is not accepting connections

Cause: The dispatchers are busy handling other requests and they notified the listener that they were temporarily busy.

Action: Attempt the connection again. If the error persists, ask the DBA to increase the number of dispatchers.
ORA-12512 TNS:service handler found but it has not registered a redirect address

Cause: The dispatcher just came up and has not had time yet to register the address that a client should be redirected to.

Action: Attempt the connection again. If the error persists, ask the DBA to increase the number of dispatchers.
ORA-12513 TNS:service handler found but it has registered on a different protocol

Cause: The dispatchers registered for this service are connected to the listener by way of a different network protocol than that of the client.

Action: Contact the DBA to register a dispatcher on your protocol.

NS Error Messages (ORA-12531 to 12629)

ORA-12531 TNS:cannot allocate memory

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. Check the protocol parameters and verify that the destination can be reached using the specified protocol.

Action: 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-12534 TNS:operation not supported

Cause: The requested operation could not be completed within the timeout period specified by the CONNECT_TIMEOUT parameter in LISTENER.ORA. This error arises from the tnslsnr.

Action: Either reconfigure CONNECT_TIMEOUT to be 0, which means wait indefinitely, or reconfigure CONNECT_TIMEOUT to be some higher value. Or, if the timeout is unacceptably long, turn on tracing for further information.
ORA-12536 TNS:operation would block

Cause: Normal "end of file" condition has been reached; partner has disconnected.

Action: None needed; this is an information message.
ORA-12538 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 adapter is not installed.

Action: Install the protocol adapter or correct the typographical error, as appropriate. Note: if the supplied address was derived from resolving the service name resolution, check the address in the appropriate file (TNSNAMES.ORA, LISTENER.ORA, or TNSNET.ORA).
ORA-12539 TNS:buffer over- or under- flow

Cause: Buffer too small for incoming data or too large for outgoing data.

Action: This restriction (which is associated with CONNECT DATA) is not normally visible to the user. For further details, turn on tracing and reexecute the operation; contact Worldwide Customer Support.
ORA-12540 TNS:internal limit restriction exceeded

Cause: Too many TNS connections open simultaneously.

Action: Wait for connections to close and re-try.
ORA-12541 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-12542 TNS:address already in use

Cause: Specified listener address is already being used.

Action: Start your listener with a unique address.
ORA-12543 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.
ORA-12544 TNS:contexts have different wait/test functions

Cause: A protocol specific ADDRESS parameter cannot be resolved.

Action: Ensure the ADDRESS parameters have been entered correctly; the most likely incorrect value is the node name.
ORA-12546 TNS:permission denied

Cause: User has insufficient privileges to perform the requested operation.

Action: Acquire necessary privileges and try again.
ORA-12547 TNS:lost contact

Cause: Partner has unexpectedly gone away, usually during process startup.

Action: Investigate partner application for abnormal termination. On an Interchange, this can happen if the machine is overloaded.
ORA-12548 TNS:incomplete read or write

Cause: A data send or receive failed.

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

Cause: The supplied connect descriptor contains illegal syntax.

Action: Check the syntax of the connect descriptor in TNSNAMES.ORA.
ORA-12551 TNS:missing keyword

Cause: The supplied connect descriptor is missing one or more TNS keywords.

Action: Check the syntax, and ensure all required keywords are present.
ORA-12552 TNS:operation was interrupted

Cause: An internal operation is still in progress.

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-12555 TNS:permission denied

Cause: User has insufficient privileges to perform the requested operation.

Action: Acquire necessary privileges and try again.
ORA-12556 TNS:no caller

Cause: TNS detected an incoming connect request but there was no caller.

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-12557 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-12558 TNS:protocol adpter not loaded

Cause: On some platforms (such as OS/2) protocol adapters ae 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-12560 TNS:protocol adapter error

Cause: A generic protocol adapter error occurred.

Action: Check addresses used for proper protocol specification. Before reporting this error, look at the error stack and check for lower level transport errors. For further details, turn on tracing and reexecute the operation. Turn off tracing when the operation is complete.
ORA-12561 TNS:unknown error

Cause: A generic protocol error occurred.

Action: For further details, turn on tracing and reexecute the operation.
ORA-12562 TNS:bad global handle

Cause: Internal error--bad "gbh" argument passed to TNS from caller. System may have been linked with old libraries.

Action: Not normally visible to user. Contact Worldwide Customer Support.
ORA-12564 TNS:connection refused

Cause: The connect request was denied by the remote user (or TNS software).

Action: Not normally visible to user. For further details, turn on tracing and reexecute the operation.
ORA-12566 TNS:protocol error

Cause: An unexpected TNS protocol error has occurred.

Action: Not normally visible to user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.
ORA-12569 TNS:packet checksum failure

Cause: The data received is not the same as the data sent.

Action: Attempt the transaction again. If the error is persistent, turn on tracing and reexecute the operation.
ORA-12570 TNS:packet reader failure

Cause: An error occurred during a data receive.

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-12571 TNS:packet writer failure

Cause: An error occurred during a data send.

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-12574 TNS:redirection denied

Cause: The connect request failed because it would have required redirection and the caller has requested no redirections.

Action: Not normally visible to user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.
ORA-12582 TNS:invalid operation

Cause: An internal function received an invalid request.

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-12583 TNS:no reader

Cause: A send operation has been requested but partner has already disconnected.

Action: Not normally visible to user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.
ORA-12585 TNS:data truncation

Cause: A receive operation has completed with insufficient data to satisfy the user's request.

Action: Not normally visible to user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.
ORA-12589 TNS:connection not bequeathable

Cause: An attempt to hand-off a connection from one process to another has failed because the protocol provider does not support it.

Action: Not normally visible to user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.
ORA-12590 TNS:no I/O buffer

Cause: An attempt to perform an I/O operation failed because no buffer was available.

Action: Not normally visible to user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.
ORA-12591 TNS:event signal failure

Cause: The TNS software is unable to signal an event occurrence.

Action: Not normally visible to user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.
ORA-12592 TNS:bad packet

Cause: An ill-formed packet has been detected by the TNS software.

Action: Not normally visible to user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.
ORA-12593 TNS:no registered connection

Cause: An attempt to solicit network event activity has failed because no connections are registered for event notification.

Action: Not normally visible to user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.
ORA-12595 TNS:no confirmation

Cause: TNS is unable to get requested confirmation acknowledgement from remote partner.

Action: Not normally visible to user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.
ORA-12596 TNS:internal inconsistency

Cause: TNS has detected an internal inconsistency

Action: Not normally visible to user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.
ORA-12597 TNS:connect descriptor already in use

Cause: Internal error - illegal use of connect descriptor.

Action: Not normally visible to user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.
ORA-12598 TNS:banner registration failed

Cause: The registration of the product banner with the Oracle server failed.

Action: This is an error which is not normally visible externally. Enable tracing and attempt to repeat the error. If it occurs again, contact Worldwide Customer Support.
ORA-12599 TNS:cryptographic checksum mismatch

Cause: The data received is not the same as the dat sent.

Action: Attempt the transaction again. If error persists, check (and correct) the integrity of your physical connection.
ORA-12600 TNS:string open failed

Cause: The creation of the string in ORACLE NLS format failed.

Action: This is an internal error. Enable tracing and attempt to repeat the error. If it occurs again, contact Worldwide Customer Support.
ORA-12601 TNS:information flags check failed

Cause: The TNS information flags set by the process prior to connection negotiation were not present after the negotiation was finished.

Action: This is an internal error. Enable tracing and attempt to repeat the error. If it occurs again, contact Worldwide Customer Support.
ORA-12611 TNS:operation is not portable

Cause: Attempted operation is not portable

Action: Not normally visible to user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.
ORA-12612 TNS:connection is busy

Cause: Attempted operation failed because it conflicts with an on-going action or status of the connection.

Action: Not normally visible to user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.
ORA-12615 TNS:preempt error

Cause: A request to service an event failed because no event notification has yet been posted.

Action: Not normally visible to user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.
ORA-12616 TNS:no event signals

Cause: The TNS software is unable to enable event signals.

Action: Not normally visible to user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.
ORA-12617 TNS:bad 'what' type

Cause: The operation failed because the type of data specified is unknown.

Action: Not normally visible to user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.
ORA-12618 TNS:versions are incompatible

Cause: The two machines are running incompatible versions of TNS.

Action: Check the version numbers, and upgrade the machine with the smaller one.
ORA-12619 TNS:unable to grant requested service

Cause: The connect request failed because requested service could not be provided by the local TNS software.

Action: If appropriate, reexecute with reduced service requirements.
ORA-12620 TNS:requested characteristic not available

Cause: The connect request failed because a requested transport characteristic could not be supported by the remote TNS software.

Action: If appropriate, reexecute with reduced requirements.
ORA-12622 TNS:event notifications are not homogeneous

Cause: An attempt to register a connection for event notification failed because the event notification type conflicts with existing registrations.

Action: Not normally visible to user. For further details, turn on tracing and reexecute the operation and contact Worldwide Customer Support.
ORA-12623 TNS:operation is illegal in this state

Cause: Connection is half-duplex and a full-duplex operation was attempted.

Action: Not normally visible to user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.
ORA-12624 TNS:connection is already registered

Cause: An attempt to register a connection for event notification failed because the connection is already registered.

Action: Not normally visible to user. For further details, turn on tracing and reexecute the operation and contact Worldwide Customer Support.
ORA-12625 TNS:missing argument

Cause: An operation failed because an argument was missing.

Action: Not normally visible to user. For further details, turn on tracing and reexecute the operation and contact Worldwide Customer Support.
ORA-12626 TNS:bad event type

Cause: An attempt to register a connection for event notification failed because the event type is unknown.

Action: Not normally visible to user. For further details, turn on tracing and reexecute the operation and contact Worldwide Customer Support.
ORA-12628 TNS:no event callbacks

Cause: An attempt to register a connection for event modification failed because asynchronous callbacks are not available.

Action: Not normally visible to user. For further details, turn on tracing and reexecute the operation and contact Worldwide Customer Support.
ORA-12629 TNS:no event test

Cause: An attempt to register a connection for event notification failed because the ability to test for events is not available.

Action: Not normally visible to user. For further details, turn on tracing and reexecute the operation and contact Worldwide Customer Support.

NA Error Messages (ORA-12630 to 12699)

ORA-12630 Native service operation not supported

Cause: An operation requested by a user is not supported by the native services component.

Action: This may be an internal error if the operation should have been supported.
ORA-12631 Username retrieval failed

Cause: The authentication service failed to retrieve the name of a user.

Action: Enable tracing to determine which routine is failing.
ORA-12632 Role fetch failed

Cause: The authentication service failed to retrieve one of the user's roles.

Action: Enable tracing to determine which routine is failing.
ORA-12633 No shared authentication services

Cause: The list of authentication services specified by the user does not match those supported by the process.

Action: Either specify another list or relink the executable with the desired services.
ORA-12634 Memory allocation failed

Cause: Process was unable to allocate memory.

Action: Terminate other processes in order to reclaim needed memory.
ORA-12635 No authentication adapters available

Cause: The executable was not linked with any authentication service adapters but the sqlnet.ora parameter that determines whether or not authentication is required was set to true.

Action: Either disable the parameter or relink the executable with service adapters.
ORA-12636 Packet send failed

Cause: A process was unable to send a packet to another process. Possible causes are:

1. The other process was terminated.

2. The machine on which the other process is running went down.

3. Some other communications error occurred.

Action:

If the cause is not obvious, contact Worldwide Customer Support.

ORA-12637 Packet receive failed

Cause: A process was unable to receive a packet from another process. Possible causes are:

1. The other process was terminated.

2. The machine on which the other process is running went down.

3. Some other communications error occurred.

Action:

If the cause is not obvious, contact Worldwide Customer Support.

ORA-12638 Credential retrieval failed

Cause: The authentication service failed to retrieve the credentials of a user.

Action: Enable tracing to determine the exact error.
ORA-12639 Authentication service negotiation failed

Cause: No match was found between the types of authentication services that the client supports and those that the server is using.

Action: Possible solutions:

1. Change the entry in sqlnet.ora that determines which services are to be used.

2. Relink the client with at least one of the authentication service adapters that the server supports.

3. Relink the server with at least one of the authentication service adapters that the client supports.

4. Disable authentication on both the client and server. ORA-12640 Authentication service initialization failed

Cause: The function specified in the authentication table entry for the service failed.

Action: Enable tracing to determine the exact error.
ORA-12641 Authentication service failed to initialize

Cause: The authentication service failed during initialization.

Action: Enable tracing to determine the exact error.
ORA-12642 No session key

Cause: A process has no session key associated with it because the authentication service being used does not use one.

Action: If a session key is required, use another authentication service.
ORA-12643 Process communication failed

Cause: A process was unable to communicate with another process. Possible causes are:

1. The other process was terminated.

2. The machine on which the other process is running went down.

3. Some other communications error occurred.

Action:

If the cause is not obvious, contact Worldwide Customer Support.

ORA-12644 Authentication service initialization failed

Cause: The routine called to initialize the authentication adapter failed.

Action: Enable tracing to determine the exact error. A likely cause is that memory is exhausted.
ORA-12645 Parameter does not exist

Cause: A sqlnet.ora parameter from which a value was needed does not exist.

Action: Set the parameter in the parameter file.
ORA-12646 Invalid value specified for boolean parameter

Cause: The value specified for a parameter was set to a value other than true/false or on/off.

Action: Correct the value of the parameter.
ORA-12647 Authentication required

Cause: The parameter that controls whether authentication is required was set to true, but the executable does not have an authentication service linked in.

Action: Either re-link the executable with an authentication service adapter or disable the parameter.
ORA-12648 Encryption or data integrity algorithm list empty

Cause: A SQL*Net list-of-algorithms parameter was empty, e.g. "()".

Action: Change the list to contain the name of at least one installed algorithm, or remove the list entirely if every installed algorithm is acceptable.
ORA-12649 Unknown encryption or data integrity algorithm

Cause: A SQL*Net list-of-algorithms parameter included an algorithm name that was not recognized.

Action: Either remove that algorithm name, correct it if it was misspelled, or install the driver for the missing algorithm.

ORA-12650 No common encryption or data integrity algorithm

Cause: The client and server have no algorithm in common for either encryption or data integrity or both.

Action: Choose sets of algorithms that overlap. In other words, add one of the client's algorithm choices to the server's list or vice versa.
ORA-12651 Encryption or data integrity algorithm unacceptable

Cause: The algorithm the server chose to use for encryption or data integrity was not one of the choices acceptable to the client. This is either the result of an internal error, of a network data transmission error, or of deliberate tampering with the transmitted data.

Action: For further details, turn on tracing, re-execute the operation, and contact Worldwide Customer Support.
ORA-12652 String truncated

Cause: Not enough memory was allocated for a string so it had to be trucated.

Action: If it is OK that the string is truncated, then it is not an error. Otherwise, call the routine that reported the error again with a larger string buffer.
ORA-12653 Authentication control function failed

Cause: The control function utilized by the authentication service driver failed.

Action: Enable tracing to determine the exact error.
ORA-12654 Authentication conversion failed

Cause: The authentication service was unable to convert the credentials of a user from the format specific to the format into the ORACLE format.

Action: Enable tracing to determine the exact error.
ORA-12655 Password check failed

Cause: The authentication service being used was unable to verify the provided password.

Action: Enable tracing to determine the exact error.
ORA-12656 Cryptographic checksum mismatch

Cause: The cryptographic checksum received with a packet of incoming data didn't match the checksum computed by the receiving end. This indicates that the packet was tampered with or otherwise corrupted in transit.

Action: Look for sources of data corruption, perhaps including deliberate tampering.
ORA-12657 No algorithms installed

Cause: The near side of the connection required the use of a service (either encryption or checksumming) when no algorithms for that service were installed.

Action: Remove the "ON" requirement for that service.
ORA-12658 Native service required but TNS version is incompatible

Cause: A process that is running an earlier version of TNS attempted to connect but the connection failed because the server process required that a native service (authentication, encryption, etc.) be used.

Action: Relink the calling executable and retry the connection or eliminate the requirement that the service be used on the server side.
ORA-12659 Error received from other process

Cause: An error was received by one or more services from the process on the other side of the connection.

Action: Enable tracing to determine the exact error(s). The error(s) is (are) not returned directly because an error generated by a server may not make sense on the client side and vice-versa.
ORA-12660 SNSparameters incompatible

Cause: One side of the connection specified "REQUIRED" for encryption or crypto-checksumming, while the other side specified "REJECTED".

Action: Change the "REQUIRED" side to "REQUESTED" if you want encryption or crypto-checksumming to be optional, or change the "REJECTED" side to "ACCEPTED" if you do not want the service to be optional.
ORA-12661 Protocol authentication to be used

Cause: The SQL*Net authentication service has determined that the SQL*Net transport protocol in use is to be utilized to authenticate a user's identity.

Action: This error is used solely to communicate information between the authentication service and the SQL*Net session layer and should not be visible to the user. If the error is seen, contact Worldwide Customer Support.
ORA-12662 proxy ticket retrieval failed

Cause: The authentication adapter used by SQL*Net failed to retrieve the credentials needed to authenticate a database link.

Action: Enable tracing to determine the exact error.
ORA-12663 Services required by client not available on the server

Cause: Service(s) that was (were) required by the client process were not available on the server process.

Action: Configure the server with the services required by the client (best solution) or delete the requirement from the configuration file of the client (least secure).
ORA-12664 Services required by server not available on the client

Cause: Service(s) that was (were) required by the server process were not available on the client process.

Action: Configure the client with the services required by the server (best solution) or delete the requirement from the configuration file of the server (least secure).
ORA-12665 NLS string open failed

Cause: A native service was unable to make a string available for use by the National Language Support component.

Action: Make sure the National Language Support component has been properly. If it has, enable tracing and report the problem to Customer Support.
ORA-12666 Dedicated server: outbound transport protocol different from inbound

Cause: The protocol specified for an externally-identified outbound connection from a dedicated server (database link) was not the same as that used for the inbound connection. It is not possible fo SQL*Net to authenticate a proxy connection that uses a protocol that is different from that which was used for the connection to the dedicated server.

Action: Specify the same protocol in the SQL*Net connect string or alias for the outbound connection as that used for the inbound connection.
ORA-12667 Shared server: outbound transport protocol different from inbound

Cause: The protocol specified for an externally-identified outbound connection from a shared server (database link) was not the same as as that used for the inbound connection. It is not possible for SQL*Net to authenticate a proxy connection that uses a protocol that is different from that which was used for the connection to the shared server.

Action: Specify the same protocol in the SQL*Net connect string or alias for the outbound connection as that used for the inbound connection
ORA-12668 Dedicated server: outbound protocol does not support proxies

Cause: The protocol specified to perform an externally-identified proxy connection (database link) from a dedicated server does not support proxy connections.

Action: Specify a protocol in the SQL*Net connect string or alias used for the connection that does support externally-authenticated proxy connections.
Note: Because of a limitation in SQL*Net, the protocol used for the proxy connection must the same as that used for the connection from the client to the server.

ORA-12669 Shared server: outbound protocol does not support proxies

Cause: The protocol specified to perform an externally-identified proxy connection (database link) from a shared server does not support proxy connections.

Action: Specify a protocol in the SQL*Net connect string or alias used for the connection that does support externally-authenticated pro connections.
Note: Because of a limitation in SQL*Net, the protocol used for the proxy connection must the same as that used for the connection from the client to the server.

ORA-12670 Incorrect role password

Cause: A password supplied for a role could not be validated by the authentication service.

Action: Supply the correct password.
ORA-12671 Shared server: adapter failed to save context

Cause: The adapter for the authentication service failed when it tried to save the data needed for proxy connections (database links) through the multi-threaded server.

Action: Enable tracing to determine the exact error. Contact Worldwide Customer Support if the reason is not obvious.
ORA-12672 Database logon failure

Cause: The authentication service adapter in use encountered an error it attempted to validate the logon attempt of a user.

Action: Enable tracing to determine the exact error encountered by the adapter.
ORA-12673 Dedicated server: context not saved

Cause: A connection was marked as being a proxy connection (database link) from a dedicated server but no inbound context was present.

Action: Before calling nsnainit(), call the routine that saves the context.
ORA-12674 Shared server: proxy context not saved

Cause: A connection was marked as being a proxy connection (database link) from a shared server but no inbound context was present.

Action: Before calling nsnainit(), call the routine that saves the context.
ORA-12675 External user name not available yet

Cause: The authentication service in use was not able to return the external name of a user of the ORACLE server because it is not available to the service yet.

Action: This is just an information message and should not normally be visible to the user. If the error does appear, contact Worldwide Customer Support.
ORA-12676 Server received internal error from client

Cause: The server process received an error from the client which indicated that an internal SQL*Net native services error had occurred.

Action: Enable tracing on both processes and attempt to recreate the problem. If the problem recurs, contact Worldwide Customer Support.
ORA-12677 Authentication service not supported by database link

Cause: The authentication service used by the proxy process (database link) was unable to find the adapter being used by the client in its list of authentication mechanisms.

Action: Specify an authentication adapter that is shared by the client and the server being used for the database link.
ORA-12678 Authentication disabled but required

Cause: The configuration parameters that control whether SQL*Net authentication is disabled or required were both set to TRUE.

Action: Set one or both of the parameters to FALSE.
ORA-12679 Native services disabled by other process but required

Cause: The remote process has disabled native services but the local process requires them.

Action: Enable native services on the remote process or disable them locally.
ORA-12680 Native services disabled but required

Cause: The process has disabled native services but at least one service is required.

Action: Enable native services or change the configuration file so that none of the available services are required.
ORA-12681 Login failed: the SecurID card does not have a pincode yet

Cause: The SecurID card that is used to logon to Oracle, does not have a pincode assigned to it.

Action: Use one of the programs supplied by Security Dynamics to assign a pincode to the card.
ORA-12682 Login failed: the SecurID card is in next PRN mode

Cause: The SecurID card and the SecurID server are out of sync and the server requires the next cardcode to resynchronize the card.

Action: Use one of the programs supplied by Security Dynamics to resynchronize the SecurID card.
ORA-12683 Encryption/crypto-checksumming: no Diffie-Hellman seed

Cause: The "sqlnet.crypto_seed" parameter is missing from the SQLNET.ORA parameters file for SQL*Net.

Action: Add this line to SQLNET.ORA, perhaps by using Network Manager: sqlnet.crypto_seed = randomly-chosen text
ORA-12684 Encryption/crypto-checksumming: Diffie-Hellman seed too small

Cause: A native service is required by the remote process but native services have been disabled locally.

Action: Enable native services locally or change the configuration parameters on the remote host so that no native services are required.
ORA-12686 Invalid command specified for a service

Cause: An operation which does not exist was specified for a native service.

Action: This is a programing error and should not normally be visible to the user. If the error does appear, contact Worldwide Customer Support.
ORA-12687 Database link failed: credentials expired

Cause: The credentials that are used to authenticate the user for the requested database link have expired.

Action: Renew your credentials. Refer to the documentation specific for your Network Authentication Adapter on how to do this.
ORA-12688 Login failed: the SecurID server rejected the new pincode

Cause: There are a number of reasons why the SecurID server would refuse a pincode: - The user might not have permission to make up his own pincode. - The pincode was either too short or too long. Valid pincodes consist of minimal four, but no more than eight characters. - The pincode contains any non alpha-numeric characters.

Action: Reexecute the operation and make sure to use a pincode that satisfies the above requirements. If the problem persists, turn on tracing at the Oracle Server side of the connection and examine the trace file for the exact error.
ORA-12689 Server Authentication required, but not supported

Cause: Server Authentication is required for this connection, but not supported by both sides of the connection.

Action: Make sure both sides of the connection have the correct version of Secure Network Services, and that the Authentication Adapter supports Server Authentication.
ORA-12690 Server Authentication failed, login cancelled

Cause: Server Authentication is required, but the server's credentials were found invalid by the client.

Action: Make sure that the server has a valid set of credentials. Refer to your authentication adapter specific documentation on how to do this.
ORA-12699 Native service internal error

Cause: An internal error occurred in the native services component.

Action: Enable tracing to determine the exact error. Contact Worldwide Customer Support.

Prev Next

Library

Product

Contents

Index

*Prefix*	*Error Number*	*Component*	*Type of Error*
TNS	1 to 500	NR (routing)	MultiProtocol Interchange
TNS	501 to 1000	NT (transport)	Protocol Adapter
TNS	1001 to 1500	Listener Control Program	Listener Control Program
ORA/TNS	12150 to 12195	SQL*Net	Oracle SQL*Net
ORA/TNS	12196 to 12285	NR (routing)	TNS
ORA/TNS	12500 to 12530	Listener	Listener to client
ORA/TNS	12531 to 12629	NS (session)	TNS
ORA	12630 to 12699	NA	Native Services