Release 8.1.5
A67785-01
 Library |
 Product |
 Contents |
 Index |
| Oracle8i Error Messages Release 8.1.5 A67785-01 |
|
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 the error persists, contact Oracle 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 the 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 resolved.
TNS-00003 INTCTL: error while sending request to the Interchange
Cause: Improper command sent to the Interchange or the Interchange is not responding. This message is 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 the 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 resolved.
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.
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 variable HOST properly and restart the INTCTL program.
TNS-00007 INTCTL: unknown host
Cause: The pointer HOST is set to an unknown host name.
Action: Set the pointer HOST properly and restart INTCTL program.
TNS-00008 INTCTL: could not contact destination Navigator
Cause: Connection could not be properly 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 Oracle Customer Support.
TNS-00009 INTCTL: could not contact destination Connection Manager
Cause: Connection could not be properly established to a Connection Manager. This may be because the Connection Manager (Interchange) specified is not running or the Connection Manager addresses are incorrect.
Action: Make sure 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 Oracle Customer Support.
TNS-00010 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 Oracle 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. Tracing can also be turned on in the Connection Manager and detailed information about the reason for the error determined. Consult the MultiProtocol Interchange Administrator's Guide for how to turn on tracing.
TNS-00012 INTCTL: error while processing Connection Manager request
Cause: An improper command was sent to the Connection Manager or it is not responding. This message is 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 Oracle 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 Oracle Customer Support.
TNS-00014 INTCTL: error while opening terminal input channel
Cause: Could not open standard terminal input. This is an internal error.
Action: Normally not visible to the user. Restart the INTCTL program. If the error persists, contact Oracle Customer Support.
TNS-00015 INTCTL: error while closing terminal input channel
Cause: Could not close terminal input channel. This is an internal error.
Action: Normally not visible to the user. Restart the INTCTL program. If the error persists, contact Oracle Customer Support.
TNS-00016 INTCTL: error while performing NS send command
Cause: This is an internal NS error. Connection may be lost.
Action: If the error persists contact Oracle Customer Support.
TNS-00017 INTCTL: error while performing NS receive command
Cause: Internal NS error. Connection may be lost.
Action: If the error persists contact Oracle 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-00020 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-00021 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: INTCHG.ORA does not contain a CMANAGER_NAME component.
Action: Define the correct name for the CMANAGER_NAME, then restart the INTCTL program.
TNS-00023 INTCTL: missing ADDRESS(es) in config files
Cause: Configuration 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 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 the error persists, contact Oracle 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.
Action: If you do not want it to be used, and want the default directory to be used instead, then unset TNS_ADMIN and re-execute.
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 Oracle 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 Oracle 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 Oracle 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 Oracle 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 Navigator or Connection Manager 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, if possible. If all is correct, contact Oracle 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 the 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 Oracle 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: No action required. 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: No action required. The Connection Manager is already running.
TNS-00043 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 the 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. 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 the TNSNAV.ORA file for that address. Or check that the Navigator is actually listening on that address.
TNS-00046 INTCTL: Could not contact the CMANAGER 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: A command was entered that does not exist, or a request other than STATUS was made 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: A trace level was not specified.
Action: Specify a trace level and retry the command.
TNS-00062 INTCTL: Bad command or syntax error: For help type help/h/?
Cause: An invalid command was entered.
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 execute any command other than status and version, you must run INTCTL on the interchange machine.
TNS-00070 INTCTL usage: [intctl] command process_name [argument]
Cause: Help message displayed by INTCTL.
Action: No action required.
TNS-00071 where command is one of following:
Cause: Help message displayed by INTCTL.
Action: No action required.
TNS-00072 * start - start up process_name
Cause: Help message displayed by INTCTL.
Action: No action required.
TNS-00073 * stop/abort - stop the process_name
Cause: Help message displayed by INTCTL.
Action: No action required.
TNS-00074 * status - get statistics from the process_name
Cause: Help message displayed by INTCTL.
Action: No action required.
TNS-00075 NOTE: the user may get the status info of a remote
Cause: Help message displayed by INTCTL.
Action: No action required.
TNS-00076 component by specifying the component name in
Cause: Help message displayed by INTCTL.
Action: No action required.
TNS-00077 the argument field
Cause: Help message displayed by INTCTL.
Action: No action required.
TNS-00078 * log_on - ask process_name to turn logging on
Cause: Help message displayed by INTCTL.
Action: No action required.
TNS-00079 * log_off - ask process_name to turn logging off
Cause: Help message displayed by INTCTL.
Action: No action required.
TNS-00080 * force_log - ask process_name to dump its state
Cause: Help message displayed by INTCTL.
Action: No action required.
TNS-00081 * trace_on - ask process name to turn tracing on
Cause: Help message displayed by INTCTL.
Action: No action required.
TNS-00082 NOTE: the user MUST specify a trace level
Cause: Help message displayed by INTCTL.
Action: No action required.
TNS-00083 (USER or ADMIN) in the argument field
Cause: Help message displayed by INTCTL.
Action: No action required.
TNS-00084 * trace_off - ask process name to turn tracing off
Cause: Help message displayed by INTCTL.
Action: No action required.
TNS-00085 * reread - ask the process name to reread parameter files
Cause: Help message displayed by INTCTL.
Action: No action required.
TNS-00086 * reload - ask the Navigator to reload TNSNET.ORA
Cause: Help message displayed by INTCTL.
Action: No action required.
TNS-00087 * version - ask the process name to display its version number
Cause: Help message displayed by INTCTL.
Action: No action required.
TNS-00088 * exit - quit the Interchange controller
Cause: Help message displayed by INTCTL.
Action: No action required.
TNS-00089 process_name is one of Interchange, CMANAGER, or Navigator
Cause: Help message displayed by INTCTL.
Action: No action required.
TNS-00090 * Interchange - will ask the Interchange
Cause: Help message displayed by INTCTL.
Action: No action required.
TNS-00091 * Navigator (or navgatr) - will ask the Navigator only
Cause: Help message displayed by INTCTL.
Action: No action required.
TNS-00092 * CMANAGER (or intlsnr) - will ask the Cmanager only
Cause: Help message displayed by INTCTL.
Action: No action required.
TNS-00093 argument is only supplied to either status or trace_on
Cause: Help message displayed by INTCTL.
Action: No action required.
TNS-00094 * to status - argument is considered the remote process_name
Cause: Help message displayed by INTCTL.
Action: No action required.
TNS-00095 * to trace_on - argument is considered the trace level
Cause: Help message displayed by INTCTL.
Action: No action required.
TNS-00100 Unable to allocate memory
Cause: Out of memory on the machine.
Action: Add more memory or run fewer processes.
TNS-00101 File operation error
Cause: Error in accessing reading or writing a particular file.
Action: Check existence of or operating system access to the log and trace file locations.
TNS-00102 Keyword-Value binding operation error
Cause: This message is not normally visible to the user. May indicate a shortage of memory.
Action: If the error persists, contact Oracle 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 the error persists, contact Oracle 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 files and directories.
TNS-00105 Could not initialize tracing
Cause: The INTCHG.ORA file is improperly configured. Verify the trace parameters specified.
Action: If the error persists, contact Oracle 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: This message is not normally visible to the user.
Action: If the error persists, contact Oracle 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 the error persists, contact Oracle Customer Support.
TNS-00110 Could not initialize network from file TNSNET.ORA
Cause: Poorly formed network information in network file.
Action: Fix network configuration data to assure that at least one Interchange is defined in TNSNET.ORA.
TNS-00111 Failed to get configuration data from file
Cause: Poorly formed configuration information in network files TNSNET.ORA or TNSNAV.ORA.
Action: Check TNSNET.ORA and TNSNAV.ORA and 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 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: This is an internal error. Should not normally occur.
Action: Contact Oracle 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 problem persists, contact Oracle Customer Support.
TNS-00117 Internal error- No data passed through pump
Cause: This is an internal error. Data expected has not arrived yet.
Action: If the error persists, contact Oracle 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.
TNS-00120 Missing PUMPS in INTCHG.ORA
Cause: No PUMPS parameter specified.
Action: Add an appropriate number of PUMPS to INTCHG.ORA.
TNS-00121 Missing CMANAGER_NAME in INTCHG.ORA
Cause: No CMANAGER_NAME parameter specified.
Action: Define the CMANAGER_NAME parameter in INTCHG.ORA; it must match the CMANAGER_NAME parameter used in TNSNET.ORA for that Interchange.
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: This is an internal error. Should not normally occur.
Action: If the error persists, contact Oracle 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 the configuration files.
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 configuration files.
TNS-00127 Missing Connection Manager name in TNSNET.ORA
Cause: One or more Connection Manager names are missing.
Action: Ensure that each Connection Manager name is defined in TNSNET.ORA. Regenerate TNSNET.ORA.
TNS-00128 Missing COMMUNITY in TNSNET.ORA
Cause: One or more ADDRESSes does 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: This is an 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 Oracle 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-00134 Missing COMMUNITY component in addresses for the Navigator in TNSNAV.ORA
Cause: The addresses specified for the Navigator have no COMMUNITY name.
Action: Ensure that all addresses in the NAVIGATOR_ADDRESSES field have a COMMUNITY entry in the TNSNAV.ORA file.
TNS-00135 Missing TNS error message file
Cause: No 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-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: An internal error occurred in Interchange.
Action: Check that you are using compatible components of the Interchange product, using the INTCTL VERSION command. If problem persists call Oracle 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 indeed in TNSNET.ORA.
TNS-00141 Failed to get file stream information
Cause: Error in the file stream package.
Action: No action required.
TNS-00142 Community mismatch in TNSNAV.ORA
Cause: The communities in the LOCAL_COMMUNITIES entry in TNSNAV.ORA do not correspond with all the communities in the NAVIGATOR_ADDRESSES entry.
Action: Assure that all communities in the NAVIGATOR_ADDRESSES correspond to those in the LOCAL_COMMUNITIES component.
TNS-00143 Illegal PREFERRED_CMANAGERS entry in TNSNAV.ORA
Cause: PREFERRED_CMANAGERS entry in the TNSNAV.ORA used by the Connection Manager. There should only be a PREFERRED_NAVIGATORS entry in the TNSNAV.ORA on an Interchange.
Action: Remove the PREFERRED_CMANAGERS entry from TNSNAV.ORA and assure that either no PREFERRED_NAVIGATORS entry is present or that it is correct.
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 maximum 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 maximum value for the number of PUMPS.
TNS-00146 Internal-- Retry data request withing pump.
Cause: The data space provided in order to receive data from the pump is to small.
Action: Retry the operation 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 occurred in.
TNS-00200 Unable to do nsanswer on contextresult=string
Cause: Requester of service may have aborted or options negotiation failed.
Action: Try making the connection again. If the problem persists call Oracle 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 Oracle Customer Support if the problem cannot be located.
TNS-00202 Failure in redirecting call : Original to string Redirect to string
Cause: This is an 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 the error persists, call Oracle 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-00204 Started tracing in intlsnr
Cause: Internal message. Successfully started tracing information.
Action: No action required.
TNS-00205 Turning off tracing in intlsnr
Cause: Internal message. Turned off tracing in the Interchange listener.
Action: No action required.
TNS-00206 Status Information for Interchange string:
Cause: Message sent back by Interchange as header for status request.
Action: No action required.
TNS-00207 Uptime : number days number hr. number min. number sec
Cause: Part of status request.
Action: No action required.
TNS-00208 Logging : string
Cause: Part of status request.
Action: No action required.
TNS-00209 Tracing : string
Cause: Part of status request Interchange.
Action: No action required.
TNS-00210 Total Pumps Available : number
Cause: Part of status request for Connection Manager.
Action: No action required.
TNS-00211 Total Active Pumps : number
Cause: Part of status request for Connection Manager.
Action: No action required.
TNS-00212 Total Pumps Started : number
Cause: Part of status request for Connection Manager.
Action: No action required.
TNS-00213 Available Connections : number
Cause: Part of status request for Connection Manager.
Action: No action required.
TNS-00214 Total Connections in Use : number
Cause: Part of status request for Connection Manager.
Action: No action required.
TNS-00215 Total Successful Connections : number
Cause: Part of status request for Connection Manager.
Action: No action required.
TNS-00216 Total Failed Connections : number
Cause: Part of status request for Connection Manager.
Action: No action required.
TNS-00217 Total Bytes of Data : number
Cause: Part of status request for Connection Manager.
Action: No action required.
TNS-00218 Current Bytes/Sec. : number
Cause: Part of status request for Connection Manager.
Action: No action required.
TNS-00219 Pump Strategy : string
Cause: Part of status request.
Action: No action required.
TNS-00220 Pump Breakdown--------------
Cause: Part of status request.
Action: No action required.
TNS-00221 Pump Connections Total Data Bytes/Second
Cause: Part of status request.
Action: No action required.
TNS-00222 -------------------------------------------------------------------
Cause: Part of status request.
Action: No action required.
TNS-00223 numbernumbernumbernumber
Cause: Part of status request.
Action: No action required.
TNS-00224 No more connections available
Cause: More connections were made 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 aare 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 number to send broadcast message string
Cause: Could not call a particular pump.
Action: No action required. However, if the problem persists, call Oracle 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 over used.
Action: This error is not immediately fatal; the orphaned pump may continue to function. Restart the Interchange when convenient. If the problem persists, call Oracle Customer Support.
TNS-00228 Failure in finding pump data
Cause: Internal problem with data passed back from pump.
Action: No action required.
TNS-00229 Error in call: unable to deliver message:string:stringstringstring
Cause: Destination for call is unavailable.
Action: No action required.
TNS-00230 Cannot start new pump process:stringstringProtocol Adapter errors:number
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 Oracle Customer Support.
TNS-00231 Pump is alive
Cause: Pump log message sent to Interchange listener.
Action: No action required.
TNS-00232 Unable to setup 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: No action required.
TNS-00233 Interchange failed to make contact with destination with errors:stringstringstring
Cause: Pump call to destination failed.
Action: Check destination.
TNS-00234 Connect data for failed call:CALL DATA =stringRECEIVE DATA = :string:
Cause: Connect data supplied for error 00233.
Action: No action required.
TNS-00235 Aborting connection:Protocol Apapter errors:string;number,numberstring;number,number
Cause: Pump aborting connection because connection has been up too long, or some other network error on the connection.
Action: No action required.
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: No action required.
TNS-00238 Pump number @: string:
Cause: Prepended message to all pump log messages.
Action: No action required.
TNS-00239 Connection Manager has been stopped
Cause: Message sent back to control program from Interchange.
Action: No action required.
TNS-00240 Connection Manager: Logging is now ON
Cause: Message sent back to control program from Interchange.
Action: No action required.
TNS-00241 Connection Manager: Logging is now OFF
Cause: Message sent back to control program from Interchange.
Action: No action required.
TNS-00242 Connection Manager: Tracing is now ON
Cause: Message sent back to control program from Interchange.
Action: No action required.
TNS-00243 Connection Manager: Tracing is now OFF
Cause: Message sent back to control program from Interchange.
Action: No action required.
TNS-00244 Connection Manager: Request Failed
Cause: Message sent back to control program from Interchange.
Action: No action required.
TNS-00245 Connection Manager: Failed to open log file
Cause: Message sent back to control program from Interchange.
Action: No action required.
TNS-00246 Connection Manager: Failed to start tracing
Cause: Message sent back to control program from Interchange.
Action: No action required.
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:number
Cause: TNSNAV.ORA 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 with 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-00250 Navigator has been started
Cause: Message to log file on Navigator startup.
Action: No action required.
TNS-00251 Failure in nstest:
Cause: NS test operation failed due to an 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 Oracle Customer Support.
TNS-00252 Unable to handle route request:string
Cause: Command requested did not exist.
Action: No action required.
TNS-00253 Error in reading network configuration data from file string with errorstring
Cause: TNSNET.ORA is poorly configured or non-existent.
Action: Check to make sure that TNSNET.ORA is properly configured.
TNS-00254 Navigator has been stopped
Cause: Message sent to Interchange control program by Navigator confirming it has been stopped.
Action: No action required.
TNS-00255 Closing down log, stopping Navigator
Cause: Log message when Navigator is stopped.
Action: No action required.
TNS-00256 Status of Navigator:
Cause: Navigator status message component.
Action: No action required.
TNS-00257 Number of Successful Requests : number
Cause: Navigator status message component.
Action: No action required.
TNS-00258 Number of Failed Requests : number
Cause: Navigator status message component.
Action: No action required.
TNS-00259 Disabled Interchange list:
Cause: Navigator status message component
Action: No action required.
TNS-00260 -------------------------------------------------------------------
Cause: Navigator status message component
Action: No action required.
TNS-00261 Interchange Name Community Link Down Time Remaining (secs)
Cause: Navigator status message component
Action: No action required.
TNS-00262 stringstringnumber
Cause: Navigator status message component
Action: No action required.
TNS-00263 Navigator: Request Failed
Cause: Response from Navigator when a particular request failed.
Action: No action required.
TNS-00264 Navigator: Failed to reload configuration data
Cause: Message sent to the Interchange control program when reload of network configuration failed. TNSNET.ORA Poorly configured or missing.
Action: No action required.
TNS-00265 Navigator: Reloaded network configuration data
Cause: Message sent to Interchange control program when reload of network is successful.
Action: No action required.
TNS-00266 Navigator: Unknown Request
Cause: Request was made to Navigator that it knows nothing about.
Action: No action required.
TNS-00267 Navigator: Internal Error
Cause: Generated when a request was made to the Navigator it knows nothing about.
Action: No action required.
TNS-00268 ON
Cause: On component of message.
Action: No action required.
TNS-00269 OFF
Cause: Off component of message.
Action: No action required.
TNS-00270 string: Terminal Errorstring
Cause: Message put out in error file of executable when it fails to start.
Action: No action required.
TNS-00271 Connection Manager
Cause: Name of the Connection Manager.
Action: No action required.
TNS-00272 Navigator
Cause: Name for the Navigator.
Action: No action required.
TNS-00273 Navigator: Logging is now ON
Cause: Message sent back to control program from Navigator.
Action: No action required.
TNS-00274 Navigator: Logging is now OFF
Cause: Message sent back to control program from Navigator.
Action: No action required.
TNS-00275 Navigator: Tracing is now ON
Cause: Message sent back to control program from Navigator.
Action: No action required.
TNS-00276 Navigator: Tracing is now OFF
Cause: Message sent back to control program from Navigator.
Action: No action required.
TNS-00277 Navigator: Request Failed
Cause: Message sent back to control program from Navigator.
Action: No action required.
TNS-00278 Navigator: Failed to Open Log file
Cause: Message sent back to control program from Navigator.
Action: No action required.
TNS-00279 Navigator: Failed to Start Tracing
Cause: Message sent back to control program from Navigator.
Action: No action required.
TNS-00280 Max Avg Bytes/Sec : number
Cause: Part of status request for Connection Manager.
Action: No action required.
TNS-00281 Connection Manager: Forced Log output
Cause: Message sent back to control program from Connection Manager.
Action: No action required.
TNS-00282 Connection Manager: Failed to force log, logging is off
Cause: Message sent back to control program from Connection Manager.
Action: No action required.
TNS-00283 Listening on the following TNS addresses:
Cause: Message sent back to control program from Connection Manager.
Action: No action required.
TNS-00284 Imm Max Avg Bytes/Sec : number
Cause: Part of status request for Connection Manager.
Action: No action required.
TNS-00285 Avg Connect Time (secs) : number
Cause: Part of status request for Connection Manager.
Action: No action required.
TNS-00286 Max Connect Time (secs) : number
Cause: Part of status request for Connection Manager.
Action: No action required.
TNS-00287 Min Connect Time (secs) : number
Cause: Part of status request for Connection Manager.
Action: No action required.
TNS-00288 Navigator: Failed to Disable Interchange
Cause: Message sent back to control program from Navigator.
Action: No action required.
TNS-00289 Navigator: Disabled Interchange
Cause: Message sent back to control program from Navigator.
Action: No action required.
TNS-00290 Navigator: Failed to Enable Interchange
Cause: Message sent back to control program from Navigator.
Action: No action required.
TNS-00291 Navigator: Enabled Interchange
Cause: Message sent back to control program from Navigator.
Action: No action required.
TNS-00292 Log File Name :string
Cause: Message sent back to control program showing log file name.
Action: No action required.
TNS-00293 Trace File Name :string
Cause: Message sent back to control program showing trace file name.
Action: No action required.
TNS-00294 Connection Manager: Security is enabled, you cannot STOP the Interchange
Cause: Message sent back to control program indicating that the connection manager is secure.
Action: No action required.
TNS-00295 Navigator: Security is enabled, you cannot STOP the Navigator
Cause: Message sent back to control program indicating that the Navigator is secure.
Action: No action required.
TNS-00296 Stoppable : string
Cause: Message sent back to control program indicating whether program can be stopped.
Action: No action required.
TNS-00297 Logging Level : string
Cause: Message sent back to control program indicating whether program can be stopped.
Action: No action required.
TNS-00298 Request to Navigator:string
Cause: Log entry for request to Navigator.
Action: No action required.
TNS-00299 Response from Navigator:string
Cause: Log entry for request to Navigator.
Action: No action required.
TNS-00300 ***Disabling Interchange : string
Cause: Log entry for disabling a particular Interchange.
Action: No action required.
TNS-00301 ***Enabling Interchange : string
Cause: Log entry for disabling a particular Interchange.
Action: No action required.
TNS-00302 Connection Manager: Unknown Request
Cause: Request sent by Interchange control program is unknown.
Action: No action required.
TNS-00303 Connection Manager: Reread parameter data
Cause: Request sent by control manager to control programming indicating that parameter data was read.
Action: No action required.
TNS-00304 Status Information for Connection Manager:
Cause: Message sent back by Interchange as header for status request.
Action: No action required.
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-00307 Navigator: Reread parameter data
Cause: Request sent by the Navigator to control program indicating that parameter data was read.
Action: No action required.
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: No action required.
TNS-00309 Connection Manager: Failed to open log while re-reading 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: No action required.
TNS-00310 Navigator: Failed to start tracing after rereading parameter data
Cause: Message sent back to control program from Navigator.
Action: No action required.
TNS-00311 Connection Manager: Failed to start tracing after rereading parameter data
Cause: Message sent back to control program from Connection Manager.
Action: No action required.
TNS-00312 Connection Manager: Failed to get version information
Cause: Message sent back to control program from Connection Manager.
Action: No action required.
TNS-00313 Navigator: Failed to get version information
Cause: Message sent back to control program from Connection Manager.
Action: No action required.
TNS-00314 Protocol Adapter Errors: number,number
Cause: Protocol Adapter errors which go with message 233.
Action: No action required.
TNS-00315 Failed to allocate larger connect data area for getting pump data: number
Cause: Could not allocate a large enough area to get pump statistics; continue without them.
Action: No action required.
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, 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 shut down and restart the Interchange to make the changes take effect.
TNS-00317 Failed to contact Connection Manager
Cause: Connection Manager is not running.
Action: Start the Connection Manager and retry.
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 re-execute the operation.
TNS-00502 Invalid argument
Cause: An internal function received an invalid parameter. This message is not normally visible to the user.
Action: For further details, turn on tracing and re-execute the operation. If the error persists, contact Oracle 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). This message is not normally visible to the user.
Action: For further details, turn on tracing and re-execute the operation. If the error persists, contact Oracle 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 re-execute 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. This is an informational message.
Action: No action required.
TNS-00507 Connection closed
Cause: Normal "end of file" condition has been reached; partner has disconnected. This is an informational message.
Action: No action required.
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: Re-execute 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 connect 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 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. This message is not normally visible to the user.
Action: For further details, turn on tracing and re-execute the operation. If the error persists, contact Oracle Customer Support.
TNS-00515 Connect failed because target host or object does not exist
Cause: The address specified is not valid, or the program being connected to does not exist.
Action: Ensure the ADDRESS parameters have been entered correctly; the most likely incorrect parameter is the node name. Ensure that the executable for the server exists (perhaps "oracle" is missing).
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. This message is not normally visible to the user.
Action: For further details, turn on tracing and re-execute the operation. If the error persists, contact Oracle 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. This message is not normally visible to the user.
Action: For further details, turn on tracing and re-execute the operation. If the error persists, contact Oracle 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 Oracle Customer Support.
TNS-00524 Current operation is still in progress
Cause: Internal operation is still in progress but will complete.
Action: No action required. Wait for the 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: This is an internal error.
Action: For further details, turn on tracing and re-execute 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 re-execute 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 re-execute 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 re-execute the operation.
TNS-00532 No previous async operation to wait on
Cause: Internal protocol adapter error.
Action: For further details, turn on tracing and re-execute the operation. If the error persists, contact Oracle Customer Support.
TNS-00533 Connection dissolved or not yet made
Cause: Internal protocol adapter error.
Action: For further details, turn on tracing and re-execute the operation. If the error persists, contact Oracle Customer Support.
TNS-00534 Failed to grant connection ownership to child
Cause: Internal protocol adapter error.
Action: For further details, turn on tracing and re-execute the operation. If the error persists, contact Oracle Customer Support.
TNS-00535 Failed to send or receive disconnect message
Cause: Internal protocol adapter error.
Action: For further details, turn on tracing and re-execute the operation. If the error persists, contact Oracle Customer Support.
TNS-00536 Connection entered inappropriate state
Cause: Internal protocol adapter error.
Action: For further details, turn on tracing and re-execute the operation. If the error persists, contact Oracle Customer Support.
TNS-00537 Index into protocol adapter table is out of legal range
Cause: Internal protocol adapter error.
Action: For further details, turn on tracing and re-execute the operation. If the error persists, contact Oracle Customer Support.
TNS-00539 Network or Protocol services are down
Cause: The Network services on or from your node are not running or have stopped running.
Action: Restart your network or protocol services on this platform. If the error persists, contact Oracle Customer Support.
TNS-01000 spawn [listener_name] spawn_alias [(ARGUMENTS='arg0, arg1,...')]
Cause: Control program usage message.
Action: No action required.
TNS-01001 start [listener_name] : start listener
Cause: Control program usage message.
Action: No action required.
TNS-01002 stop [listener_name] : stop listener
Cause: Control program usage message.
Action: No action required.
TNS-01003 status [listener_name] : get the status of listener
Cause: Control program usage message.
Action: No action required.
TNS-01004 reload [listener_name] : reload the parameter files and SIDs
Cause: Control program usage message.
Action: No action required.
TNS-01005 trace OFF | USER | ADMIN [listener_name] : set tracing to the specified level
Cause: Control program usage message.
Action: No action required.
TNS-01006 set password : set the password for subsequent calls
Cause: Control program usage message.
Action: No action required.
TNS-01007 quit | exit : exit LSNRCTL
Cause: Control program usage message.
Action: No action required.
TNS-01008 version [listener_name] : get the version information of the listener
Cause: Control program usage message.
Action: No action required.
TNS-01009 service [listener_name] : get the service information of the listener
Cause: Control program usage message.
Action: No action required.
TNS-01010 dbsnmp_start : start db subagent
Cause: Control program usage message.
Action: No action required.
TNS-01011 dbsnmp_stop : stop db subagent
Cause: Control program usage message.
Action: No action required.
TNS-01012 dbsnmp_status : status db subagent
Cause: Control program usage message.
Action: No action required.
TNS-01013 set|show trc_{ } [value]: set|show trace parameters of current listener
Cause: Control program usage message.
Action: No action required.
TNS-01014 set|show log_{ } [value]: set|show log parameters of current listener
Cause: Control program usage message.
Action: No action required.
TNS-01015 set|show parm_name [value]: sets|shows current listener parm values
Cause: Control program usage message.
Action: No action required.
TNS-01016 change_password [listener_name]: changes the password of the listener
Cause: Control program usage message.
Action: No action required.
TNS-01017 set|show current_listener [listener_name]: sets|shows current listener
Cause: Control program usage message.
Action: No action required.
TNS-01018 save_config [listener_name]: saves configuration changes to parameter file
Cause: Control program usage message.
Action: No action required.
TNS-01019 set rawmode ON | OFF: set output mode for services and status commands
Cause: Control program usage message.
Action: No action required.
TNS-01020 STATUS of the LISTENER
Cause: Control program status message.
Action: No action required.
TNS-01021 ------------------------
Cause: Control program status message.
Action: No action required.
TNS-01022 Alias string
Cause: Control program status message.
Action: No action required.
TNS-01023 Version string
Cause: Control program status message.
Action: No action required.
TNS-01024 Trace Level string
Cause: Control program status message.
Action: No action required.
TNS-01025 Security string
Cause: Control program status message.
Action: No action required.
TNS-01026 Start Date string
Cause: Control program status message.
Action: No action required.
TNS-01027 Listener Trace File string
Cause: Control program status message.
Action: No action required.
TNS-01028 Listener Log File string
Cause: Control program status message.
Action: No action required.
TNS-01029 Services Summary...
Cause: Control program status message.
Action: No action required.
TNS-01030 The listener supports no services
Cause: Control program status message.
Action: No action required.
TNS-01033 Listener Parameter File string
Cause: Control program status message.
Action: No action required.
TNS-01034 Uptime number days number hr. number min. number sec
Cause: Control program status message.
Action: No action required.
TNS-01036 string established:string refused:string
Cause: Control program status message.
Action: No action required.
TNS-01037 string established:string refused:string
Cause: Control program status message.
Action: No action required.
TNS-01038 string established:string refused:string current:string max:string state:string
Cause: Control program status message.
Action: No action required.
TNS-01039 stringhas string service handler(s)
Cause: Control program status message.
Action: No action required.
TNS-01040 SNMP string
Cause: Control program status message.
Action: No action required.
TNS-01041 string parameter "string" set to string
Cause: Control program status message.
Action: No action required.
TNS-01042 Current Listener is string
Cause: Control program status message.
Action: No action required.
TNS-01043 Password changed for string
Cause: Control program status message.
Action: No action required.
TNS-01044 string(Registered) has string service handler(s)