Oracle Network Products Troubleshooting Guide
Interchange Error Messages (TNS-00100 to 00499)
TNS-00100 Unable to allocate memory
| 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-00101 File Operation Error
| 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. | |
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 | |
TNS-00229 Error in nscall: unable to deliver message: string: error num
| Cause: | Destination for call is unavailable. | |
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. | |
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. | |
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. | |
TNS-00245 Connection Manager: Failed to open log file
| Cause: | Message sent back to control program from Interchange. | |
TNS-00246 Connection Manager: Failed to start tracing
| Cause: | Message sent back to control program from Interchange. | |
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. | |
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. | |
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. | |
TNS-00310 Navigator: Failed to start tracing after rereading parameter data
| Cause: | Message sent back to control program from Navigator. | |
TNS-00311 Connection Manager: Failed to start tracing after rereading parameter data
| Cause: | Message sent back to control program from Connection Manager. | |
TNS-00312 Connection Manager: Failed to get version information
| Cause: | Message sent back to control program from Connection Manager. | |
TNS-00313 Navigator: Failed to get version information
| Cause: | Message sent back to control program from Navigator. | |
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. | |
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. | |