Release 2 (9.2)
Part Number A96525-01
 Home |
 Book List |
 Contents |
 Index |
 Master Index |
 Feedback |
| Oracle9i Database Error Messages Release 2 (9.2) Part Number A96525-01 |
|
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 Support Services.
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.
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.
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.
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.
Cause: The HOST variable was not set.
Action: Set the variable HOST properly and restart the INTCTL program.
Cause: The pointer HOST is set to an unknown host name.
Action: Set the pointer HOST properly and restart INTCTL program.
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 Support Services.
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 Support Services.
Cause: Internal NS error; connection may be lost.
Action: Make sure the connection is properly established. If the error persists, then contact Oracle Support Services.
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.
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 Support Services.
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 Support Services.
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 Support Services.
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 Support Services.
Cause: This is an internal NS error. Connection may be lost.
Action: If the error persists contact Oracle Support Services.
Cause: Internal NS error. Connection may be lost.
Action: If the error persists contact Oracle Support Services.
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.
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.
Cause: TNSNAV.ORA does not contain the NAVIGATOR_DATA component.
Action: Define the ADDRESS(es) for the Navigator, then restart the INTCTL program.
Cause: INTCHG.ORA does not contain an INTERCHANGE_DATA component.
Action: Define the correct data for the Connection Manager, then restart the INTCTL program.
Cause: INTCHG.ORA does not contain a CMANAGER_NAME component.
Action: Define the correct name for the CMANAGER_NAME, then restart the INTCTL program.
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.
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 Support Services.
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.
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.
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.
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.
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 Support Services.
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 Support Services.
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 Support Services.
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 Support Services.
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.
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.
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.
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 Support Services.
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 Support Services.
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.
Cause: There is a Navigator already running and listening on the same addresses.
Action: No action required. The Navigator is already running.
Cause: There is a Connection Manager already running and listening on the same addresses.
Action: No action required. The Connection Manager is already running.
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.
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.
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.
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.
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.
Cause: A trace level was not specified.
Action: Specify a trace level and retry the command.
Cause: An invalid command was entered.
Action: Check the MultiProtocol Interchange Administrator's Guide or type HELP for a list of valid commands.
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.
Cause: INTCTL was unable to find the CMANAGER_NAME parameter in INTCHG.ORA.
Action: Check that the INTCHG.ORA file is properly constructed.
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.
Cause: Help message displayed by INTCTL.
Action: No action required.
Cause: Help message displayed by INTCTL.
Action: No action required.
Cause: Help message displayed by INTCTL.
Action: No action required.
Cause: Help message displayed by INTCTL.
Action: No action required.
Cause: Help message displayed by INTCTL.
Action: No action required.
Cause: Help message displayed by INTCTL.
Action: No action required.
Cause: Help message displayed by INTCTL.
Action: No action required.
Cause: Help message displayed by INTCTL.
Action: No action required.
Cause: Help message displayed by INTCTL.
Action: No action required.
Cause: Help message displayed by INTCTL.
Action: No action required.
Cause: Help message displayed by INTCTL.
Action: No action required.
Cause: Help message displayed by INTCTL.
Action: No action required.
Cause: Help message displayed by INTCTL.
Action: No action required.
Cause: Help message displayed by INTCTL.
Action: No action required.
Cause: Help message displayed by INTCTL.
Action: No action required.
Cause: Help message displayed by INTCTL.
Action: No action required.
Cause: Help message displayed by INTCTL.
Action: No action required.
Cause: Help message displayed by INTCTL.
Action: No action required.
Cause: Help message displayed by INTCTL.
Action: No action required.
Cause: Help message displayed by INTCTL.
Action: No action required.
Cause: Help message displayed by INTCTL.
Action: No action required.
Cause: Help message displayed by INTCTL.
Action: No action required.
Cause: Help message displayed by INTCTL.
Action: No action required.
Cause: Help message displayed by INTCTL.
Action: No action required.
Cause: Help message displayed by INTCTL.
Action: No action required.
Cause: Help message displayed by INTCTL.
Action: No action required.
Cause: Out of memory on the machine.
Action: Add more memory or run fewer processes.
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.
Cause: This message is not normally visible to the user. May indicate a shortage of memory.
Action: If the error persists, contact Oracle Support Services.
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 Support Services.
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.
Cause: The INTCHG.ORA file is improperly configured. Verify the trace parameters specified.
Action: If the error persists, contact Oracle Support Services.
Cause: Unable to access or obtain write permission to create log file.
Action: Check existence of or access to log file directory.
Cause: This message is not normally visible to the user.
Action: If the error persists, contact Oracle Support Services.
Cause: TNS_ADMIN pointer is not set.
Action: Set the TNS_ADMIN pointer before running application.
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 Support Services.
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.
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.
Cause: Name specified for configuration file was incorrect.
Action: Check for presence of the configuration 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.
Cause: This is an internal error. Should not normally occur.
Action: Contact Oracle Support Services.
Cause: Not enough memory to allocate pump buffers.
Action: Decrease the number of PUMP_BUFFERS in INTCHG.ORA.
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 Support Services.
Cause: This is an internal error. Data expected has not arrived yet.
Action: If the error persists, contact Oracle Support Services.
Cause: No PUMP_CONNECTIONS parameter specified in INTCHG.ORA.
Action: Add PUMP_CONNECTIONS parameter to INTCHG.ORA.
Cause: No PUMPS parameter specified.
Action: Add an appropriate number of PUMPS to 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.
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.
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.
Cause: This is an internal error. Should not normally occur.
Action: If the error persists, contact Oracle Support Services.
Cause: Error in the TNSNET.ORA file.
Action: Check the contents of TNSNET.ORA and eliminate errors. Regenerate the configuration files.
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.
Cause: One or more Connection Manager names are missing.
Action: Ensure that each Connection Manager name is defined in TNSNET.ORA. Regenerate 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.
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 Support Services.
Cause: There is an error in one of the addresses listed in TNSNET.ORA.
Action: Check the file for errors in defining Interchanges.
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.
Cause: A community has been defined in TNSNET.ORA with a COST of 0.
Action: Assign an alternate value that is greater than 0.
Cause: Improperly configured TNSNAV.ORA file.
Action: Define the LOCAL_COMMUNITIES fields correctly 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.
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.
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.
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.
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.
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 the problem persists, contact Oracle Support Services.
Cause: Could not find the Interchange specified in a control request.
Action: Check that the Interchange specified is indeed in TNSNET.ORA.
Cause: Error in the file stream package.
Action: No action required.
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.
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.
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.
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.
Cause: The data space provided in order to receive data from the pump is to small.
Action: Retry the operation with a larger buffer.
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.
Cause: Requester of service may have aborted or options negotiation failed.
Action: Try making the connection again. If the problem persists, contact Oracle Support Services.
Cause: Improperly formed connect data sent to the Interchange listener.
Action: If the problem persists, check the application using the Interchange (it may be closing down or crashing). Contact Oracle Support Services if the problem cannot be located.
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, contact Oracle Support Services.
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.
Cause: Internal message. Successfully started tracing information.
Action: No action required.
Cause: Internal message. Turned off tracing in the Interchange listener.
Action: No action required.
Cause: Message sent back by Interchange as header for status request.
Action: No action required.
Cause: Part of status request.
Action: No action required.
Cause: Part of status request.
Action: No action required.
Cause: Part of status request Interchange.
Action: No action required.
Cause: Part of status request for Connection Manager.
Action: No action required.
Cause: Part of status request for Connection Manager.
Action: No action required.
Cause: Part of status request for Connection Manager.
Action: No action required.
Cause: Part of status request for Connection Manager.
Action: No action required.
Cause: Part of status request for Connection Manager.
Action: No action required.
Cause: Part of status request for Connection Manager.
Action: No action required.
Cause: Part of status request for Connection Manager.
Action: No action required.
Cause: Part of status request for Connection Manager.
Action: No action required.
Cause: Part of status request for Connection Manager.
Action: No action required.
Cause: Part of status request.
Action: No action required.
Cause: Part of status request.
Action: No action required.
Cause: Part of status request.
Action: No action required.
Cause: Part of status request.
Action: No action required.
Cause: Part of status request.
Action: No action required.
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.
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.
Cause: Could not call a particular pump.
Action: No action required. However, if the problem persists, contact Oracle Support Services.
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, contact Oracle Support Services.
Cause: Internal problem with data passed back from pump.
Action: No action required.
Cause: Destination for call is unavailable.
Action: No action required.
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 Support Services.
Cause: Pump log message sent to Interchange listener.
Action: No action required.
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.
Cause: Pump call to destination failed.
Action: Check destination.
Cause: Connect data supplied for error 00233.
Action: No action required.
Cause: Pump aborting connection because connection has been up too long, or some other network error on the connection.
Action: No action required.
Cause: Pump failed to initialize tracing.
Action: Check that INTCHG.ORA is properly configured.
Cause: Connection may have aborted before error took place in Pump.
Action: No action required.
Cause: Prepended message to all pump log messages.
Action: No action required.
Cause: Message sent back to control program from Interchange.
Action: No action required.
Cause: Message sent back to control program from Interchange.
Action: No action required.
Cause: Message sent back to control program from Interchange.
Action: No action required.
Cause: Message sent back to control program from Interchange.
Action: No action required.
Cause: Message sent back to control program from Interchange.
Action: No action required.
Cause: Message sent back to control program from Interchange.
Action: No action required.
Cause: Message sent back to control program from Interchange.
Action: No action required.
Cause: Message sent back to control program from Interchange.
Action: No action required.
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.
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.
Cause: Network configuration file TNSNET.ORA is missing or poorly configured.
Action: Check to make sure that TNSNET.ORA is properly configured.
Cause: Message to log file on Navigator startup.
Action: No action required.
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, contact Oracle Support Services.
Cause: Command requested did not exist.
Action: No action required.
Cause: TNSNET.ORA is poorly configured or non-existent.
Action: Check to make sure that TNSNET.ORA is properly configured.
Cause: Message sent to Interchange control program by Navigator confirming it has been stopped.
Action: No action required.
Cause: Log message when Navigator is stopped.
Action: No action required.
Cause: Navigator status message component.
Action: No action required.
Cause: Navigator status message component.
Action: No action required.
Cause: Navigator status message component.
Action: No action required.
Cause: Navigator status message component
Action: No action required.
Cause: Navigator status message component
Action: No action required.
Cause: Navigator status message component
Action: No action required.
Cause: Navigator status message component
Action: No action required.
Cause: Response from Navigator when a particular request failed.
Action: No action required.
Cause: Message sent to the Interchange control program when reload of network configuration failed. TNSNET.ORA Poorly configured or missing.
Action: No action required.
Cause: Message sent to Interchange control program when reload of network is successful.
Action: No action required.
Cause: Request was made to Navigator that it knows nothing about.
Action: No action required.
Cause: Generated when a request was made to the Navigator it knows nothing about.
Action: No action required.
Cause: On component of message.
Action: No action required.
Cause: Off component of message.
Action: No action required.
Cause: Message put out in error file of executable when it fails to start.
Action: No action required.
Cause: Name of the Connection Manager.
Action: No action required.
Cause: Name for the Navigator.
Action: No action required.
Cause: Message sent back to control program from Navigator.
Action: No action required.
Cause: Message sent back to control program from Navigator.
Action: No action required.
Cause: Message sent back to control program from Navigator.
Action: No action required.
Cause: Message sent back to control program from Navigator.
Action: No action required.
Cause: Message sent back to control program from Navigator.
Action: No action required.
Cause: Message sent back to control program from Navigator.
Action: No action required.
Cause: Message sent back to control program from Navigator.
Action: No action required.
Cause: Part of status request for Connection Manager.
Action: No action required.
Cause: Message sent back to control program from Connection Manager.
Action: No action required.
Cause: Message sent back to control program from Connection Manager.
Action: No action required.
Cause: Message sent back to control program from Connection Manager.
Action: No action required.
Cause: Part of status request for Connection Manager.
Action: No action required.
Cause: Part of status request for Connection Manager.
Action: No action required.
Cause: Part of status request for Connection Manager.
Action: No action required.
Cause: Part of status request for Connection Manager.
Action: No action required.
Cause: Message sent back to control program from Navigator.
Action: No action required.
Cause: Message sent back to control program from Navigator.
Action: No action required.
Cause: Message sent back to control program from Navigator.
Action: No action required.
Cause: Message sent back to control program from Navigator.
Action: No action required.
Cause: Message sent back to control program showing log file name.
Action: No action required.
Cause: Message sent back to control program showing trace file name.
Action: No action required.
Cause: Message sent back to control program indicating that the connection manager is secure.
Action: No action required.
Cause: Message sent back to control program indicating that the Navigator is secure.
Action: No action required.
Cause: Message sent back to control program indicating whether program can be stopped.
Action: No action required.
Cause: Message sent back to control program indicating whether program can be stopped.
Action: No action required.
Cause: Log entry for request to Navigator.
Action: No action required.
Cause: Log entry for request to Navigator.
Action: No action required.
Cause: Log entry for disabling a particular Interchange.
Action: No action required.
Cause: Log entry for enabling a particular Interchange.
Action: No action required.
Cause: Request sent by Interchange control program is unknown.
Action: No action required.
Cause: Request sent by control manager to control programming indicating that parameter data was read.
Action: No action required.
Cause: Message sent back by Interchange as header for status request.
Action: No action required.
Cause: Message sent back by the Navigator indicating an invalid trace level.
Action: Reattempt the request with a correct trace level.
Cause: Message sent back by the Connection Manager indicating an invalid trace level.
Action: Reattempt the request with a correct trace level.
Cause: Request sent by the Navigator to control program indicating that parameter data was read.
Action: No action required.
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.
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.
Cause: Message sent back to control program from Navigator.
Action: No action required.
Cause: Message sent back to control program from Connection Manager.
Action: No action required.
Cause: Message sent back to control program from Connection Manager.
Action: No action required.
Cause: Message sent back to control program from Connection Manager.
Action: No action required.
Cause: Protocol Adapter errors which go with message 233.
Action: No action required.
Cause: Could not allocate a large enough area to get pump statistics; continue without them.
Action: No action required.
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.
Cause: Connection Manager is not running.
Action: Start the Connection Manager and retry.
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.
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 Support Services.
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.
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 Support Services.
Cause: The requested operation could not be completed within the timeout period.
Action: For further details, turn on tracing and re-execute the operation.
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.
Cause: Normal "end of file" condition has been reached; partner has disconnected. This is an informational message.
Action: No action required.
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.
Cause: Too much data for buffer.
Action: Re-execute with larger receive buffer or smaller send buffer.
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.
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.
Cause: Specified listener address is already being used.
Action: Start your listener with an unused address.
Cause: Contact cannot be made with remote party.
Action: Make sure the network driver is functioning and the network is up.
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 Support Services.
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).
Cause: User has insufficient privileges to perform the requested operation.
Action: Acquire necessary privileges and try again.
Cause: Partner has unexpectedly gone away.
Action: Investigate partner application for abnormal termination.
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 Support Services.
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.
Cause: The supplied connect descriptor contains illegal syntax.
Action: Check the syntax of the connect descriptor for correct syntax.
Cause: The supplied connect descriptor is missing one or more TNS keywords.
Action: Check the syntax, and ensure all required keywords are present.
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 Support Services.
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 Support Services.
Cause: Internal operation is still in progress but will complete.
Action: No action required. Wait for the operation to complete.
Cause: Operating system failed to complete operation because user lacked sufficient privileges.
Action: Check your platform-specific privileges.
Cause: This is an internal error.
Action: For further details, turn on tracing and re-execute the operation.
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.
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.
Cause: A generic protocol adapter error occurred.
Action: For further details, turn on tracing and re-execute the operation.
Cause: Internal protocol adapter error.
Action: For further details, turn on tracing and re-execute the operation. If the error persists, contact Oracle Support Services.
Cause: Internal protocol adapter error.
Action: For further details, turn on tracing and re-execute the operation. If the error persists, contact Oracle Support Services.
Cause: Internal protocol adapter error.
Action: For further details, turn on tracing and re-execute the operation. If the error persists, contact Oracle Support Services.
Cause: Internal protocol adapter error.
Action: For further details, turn on tracing and re-execute the operation. If the error persists, contact Oracle Support Services.
Cause: Internal protocol adapter error.
Action: For further details, turn on tracing and re-execute the operation. If the error persists, contact Oracle Support Services.
Cause: Internal protocol adapter error.
Action: For further details, turn on tracing and re-execute the operation. If the error persists, contact Oracle Support Services.
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 Support Services.
Cause: The SSL protocol adapter encountered an error.
Action: In most cases, this error should only be paired with a more meaningful ORA- error.
Cause: The SSL protocol adapter was unable to locate an adapter for the protocol that it is going to use as the data transport.
Action: In most cases, the underlying transport is TCP. Make sure that the Oracle Net TCP/IP adapter was installed.
Cause: The SSL protocol adapter was unable to connect to another process.
Action: This error can be caused by a variety of problems including the termination of the peer process. Enable Oracle Net tracing and attempt the connection again. The trace file should give some clues as to what the exact problem is.
Cause: The SSL protocol adapter encountered an unexpected error.
Action: This error is not normally visible to users. Enable Oracle Net tracing and attempt to reproduce the error. If it occurs, contact Oracle Support Services.
Cause: The SSL adapter could not perform a given command.
Action: This error is not normally visible to users. Enable Oracle Net tracing and attempt to reproduce the error. If it occurs, contact Oracle Support Services.
Cause: The SSL protocol adapter was not able to retrieve a configuration parameter.
Action: This error is not normally visible to users. Enable Oracle Net tracing and attempt to reproduce the error. If it occurs, contact Oracle Support Services.
Cause: The SSL protocol adapter was unable to perform a command.
Action: This error is not normally visible to users. Enable Oracle Net tracing and attempt to reproduce the error. If it occurs, contact Oracle Support Services.
Cause: The SSL protocol adapter was unable to retrieve information about the remote user.
Action: Examine the first error in the error stack. It should describe the error in more detail.
Cause: The value specified for the parameter that specifies that SSL client authentication is to be used was not boolean.
Action: Specify a correct value for the parameter.
Cause: The value specified for the SSL version is not valid.
Action: Specify a valid value for the SSL version.
Cause: The SSL protocol adapter encountered an error when the underlying transport disconnected.
Action: This error is not normally visible to users. Enable Oracle Net tracing and attempt to reproduce the error. If it occurs, contact Oracle Support Services.
Cause: The underlying transport adapter used by the SSL adapter failed to connect.
Action: Enable Oracle Net tracing and try the connection again. If the connection fails, examine the trace file to determine the cause.
Cause: SSL cipher specs were specified, but none were valid.
Action: Specify correct cipher suites.
Cause: The SSL adapter failed to read data from its connection.
Action: Examine the contents of sqlnet.log for more information. Enable Oracle Net tracing and try the connection again. If the connection fails, examine the trace file to determine the cause.
Cause: The SSL adapter failed to send data over its connection.
Action: Examine the contents of sqlnet.log for more information. Enable Oracle Net tracing and try the connection again. If the connection fails, examine the trace file to determine the cause.
Cause: It was specified that a file was to be used from which to retrieve a wallet, but no directory was specified for the wallet.
Action: Specify the directory where the wallet is located.
Cause: A wallet resource locator was specified, but no method was given for the retrieval of the wallet.
Action: Specify the method by which the method is to be retrieved.
Cause: The method specified for wallet retrieval is not supported. Currently, only files are supported for wallet retrieval.
Action: Specify "FILE" as the wallet retrieval method.
Cause: Entrust failed to authenticate the username, password, and/or profile name that was presented.
Action: Specify correct values for the username, password or profile name. If no data was prompted for, contact Oracle Support Services.
Cause: An error occurred while attempting to validate the provided Entrust certificate.
Action: This error is not normally visible to users. Enable Oracle Net tracing and attempt to reproduce the error. If it occurs, contact Oracle Support Services.
Cause: An error occurred while attempting to extract a name from an Entrust certificate.
Action: This error is not normally visible to users. Enable Oracle Net tracing and attempt to reproduce the error. If it occurs, contact Oracle Support Services.
Cause: Control program usage message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program general message.
Action: No action required.
Cause: Control program general message.
Action: No action required.
Cause: Control program general message.
Action: No action required.
Cause: Control program general message.
Action: No action required.
Cause: Control program general message.
Action: No action required.
Cause: Control program general message.
Action: No action required.
Cause: Control program general message.
Action: No action required.
Cause: Control program general message.
Action: No action required.
Cause: Control program general message.
Action: No action required.
Cause: Control program general message.
Action: No action required.
Cause: Control program general message.
Action: No action required.
Cause: Control program general message.
Action: No action required.
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.
Cause: Control program general message.
Action: No action required.
Cause: Listener starting message.
Action: No action required.
Cause: Control program general message.
Action: No action required.
Cause: Listener starting message.
Action: No action required.
Cause: Listener starting message.
Action: No action required.
Cause: Listener starting message.
Action: No action required.
Cause: Listener starting message.
Action: No action required.
Cause: Listener starting message.
Action: No action required.
Cause: Listener starting message.
Action: No action required.
Cause: Listener starting message.
Action: No action required.
Cause: Listener starting message.
Action: No action required.
Cause: Listener starting message.
Action: No action required.
Cause: Listener starting message.
Action: No action required.
Cause: Listener starting message.
Action: No action required.
Cause: Listener starting message.
Action: No action required.
Cause: Listener logging message.
Action: No action required.
Cause: Listener logging message.
Action: No action required.
Cause: Listener logging message.
Action: No action required.
Cause: Listener logging message.
Action: No action required.
Cause: Listener logging message.
Action: No action required.
Cause: Listener logging message.
Action: No action required.
Cause: Listener logging message.
Action: No action required.
Cause: Listener logging message.
Action: No action required.
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 Net8 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 path name of the TNSLSNR executable as displayed by LSNRCTL is correct.
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.
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.
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.
Cause: Another listener is already listening on one of the ADDRESSes specified.
Action: Shut down the previous listener specified by the listener name before starting this one.
Cause: Failed to specify a valid trace level for the LSNRCTL trace command.
Action: Specify one of OFF, USER, ADMIN, or SUPPORT. Type "LSNRCTL help trace" for more information.
Cause: Password not entered via TTY.
Action: Enter the listener password on a TTY device.
Cause: Possibly garbled password entered.
Action: Re-enter the listener password, using valid ASCII characters. If problem persists, contact Oracle Support Services.
Cause: New password and re-entered new password are different.
Action: Re-enter the listener password, make sure that New password and re-entered new password are the same.
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.
Cause: Failed to specify a valid value for the LSNRCTL use_plugandplay command.
Action: Specify one of ON or OFF. Type "LSNRCTL help set use_plugandplay" for more information.
Cause: Failed to specify a valid value for the LSNRCTL save_config_on_stop command.
Action: Specify one of ON or OFF. Type "LSNRCTL help set save_config_on_stop" for more information.
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 is TNSNAMES.ORA.
Cause: The listener could not find the listener name specified.
Action: Make sure valid addresses on which to listen are specified for the listener name in LISTENER.ORA.
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.
Cause: One of the SIDs was specified in an obsolete format.
Action: Check LISTENER.ORA for a line of the form:
sid = (SID=(ORACLE_HOME=oracle_home))
or
sid = (SID_DESC=(ORACLE_HOME=oracle_home))
The above format is no longer supported and SID_LIST_listener_name format described in the Oracle9i Net Services Administrator's Guide should be used. For example:
SID_LIST_LISTENER = (SID_LIST=(SID_DESC=(SID_NAME=sid)(ORACLE_ HOME=oracle_home)))
Cause: SID_LIST_listener_name in LISTENER.ORA has an error in it.
Action: Be sure this parameter is specified as described in the Oracle9i Net Services Administrator's Guide. For example:
SID_LIST_LISTENER = (SID_LIST=(SID_DESC=(SID_NAME=sid)(ORACLE_ HOME=oracle_home)))
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_DESC=(SID_NAME=sid)(PRESPAWN_ MAX=5)(ORACLE_HOME=oracle_home)(PRESPAWN_DESC=(PROTOCOL=tcp)(POOL_ SIZE=10)(TIMEOUT=30))))
Add or correct these parameters in the LISTENER.ORA file.
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.
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 re-execute the operation. If the error persists, contact Oracle Support Services.
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 re-execute the operation. If the error persists, contact Oracle Support Services.
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.
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.
Cause: The security feature of the listener is preventing the intended operation.
Action: Some commands like stopping the listener are only intended to be done by database administrators. 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 database administrator is attempting the command then use the "set password" command at the LSNRCTL prompt with 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.
Cause: The 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 message is not normally visible to the user. For further details, turn on tracing and re-execute the operation. If the error persists, contact Oracle Support Services.
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 message is not normally visible to the user. For further details, turn on tracing and re-execute the operation. If the error persists, contact Oracle Support Services.
Cause: The event detection mechanism broke and caused all listen addresses to be removed.
Action: Error 1170 has occurred 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 message is not normally visible to the user. For further details, turn on tracing and re-execute the operation. If the error persists, contact Oracle Support Services.
Cause: PRESPAWN_MAX in each SID_DESC does not have required fields.
Action: Be sure the parameters required for SID_DESC are specified in each SID_DESC. For example:
SID_LIST_LISTENER = (SID_LIST=(SID_DESC=(SID_NAME=sid)(PRESPAWN_ MAX=15)(ORACLE_HOME=oracle_home)(PRESPAWN_DESC=(PROTOCOL=tcp)(POOL_ SIZE=10)(TIMEOUT=30))))
Add or correct these parameters in the LISTENER.ORA file.
Cause: The minimum value for PRESPAWN_MAX should be the sum of the POOL_SIZEs.
Action: Be sure the parameters required for PRESPAWN_DESC are specified in each SID_DESC. For example:
SID_LIST_LISTENER = (SID_LIST=(SID_DESC=(SID_NAME=sid)(PRESPAWN_ MAX=15)(ORACLE_HOME=oracle_home)(PRESPAWN_DESC=(PROTOCOL=tcp)(POOL_ SIZE=10)(TIMEOUT=30))(PRESPAWN_DESC=(PROTOCOL=ipc)(POOL_ SIZE=5)(TIMEOUT=15))))
Add or correct these parameters in the LISTENER.ORA file.
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.
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.
Cause: Log status needs to be set ON for changing the log file.
Action: Use the command set log_status ON to set the log status of the listener ON.
Cause: Trace Level needs to be set for changing the trace file/directory.
Action: Use the command set trc_level ON to set the trace level.
Cause: Instance tried to register as a class unknown to listener.
Action: Check LISTENER.ORA and/or instance configuration, and reference platform documentation to find the instance classes available for the listener on this platform.
Cause: The listener could not find the listener object specified.
Action: Make sure the listener object is present in the Directory Server.
Cause: The ownership privileges of the TNSLSNR executable are incorrect.
Action: Contact your database administrator 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.
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.
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.
Cause: The unprivileged operating system 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.
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 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.
Cause: Listener logging message.
Action: No action required.
Cause: Listener logging message.
Action: No action required.
Cause: Listener logging message.
Action: No action required.
Cause: Listener logging message.
Action: No action required.
Cause: Listener logging message.
Action: No action required.
Cause: Listener logging message.
Action: No action required.
Cause: Listener logging message.
Action: No action required.
Cause: Listener logging message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Invalid value for the LSNRCTL DIRECT_HANDOFF parameter.
Action: Specify either ON or OFF.
Cause: GBNAME or domain name too long.
Action: Check the GBNAME parameter in LISTENER.ORA, shorten it.
Cause: CLBGNAMES parameter in TNSNAMES.ORA is bad.
Action: Check the CLBGNAMES parameter format and correct it. Make sure that the TNSNAMES.ORA file is there.
Cause: An alias was expected in TNSNAMES.ORA but was not found or was not correctly formed.
Action: Check the TNSNAMES.ORA for the alias and make sure it is correctly formed.
Cause: The listener found no suitable handler to redirect to.
Action: Make sure that there is at least one handler for this node.
Cause: A GMS call made by the listener failed.
Action: Check if the GMS is up and running. See GMS-client trace files for more information.
Cause: When a process attempted to retrieve a role from the authentication service, no more were available.
Action: No action required. This error is used internally and occurs in the normal course of events.
Cause: The 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 Oracle Support Services, as this error should never happen. Otherwise, add an initialization function for the service being used.
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 Oracle Support Services.
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 Oracle Support Services.
Cause: The function NAU_INI() was passed a null pointer as the pointer to the context that it is supposed to use.
Action: Call NAU_INI() with a pointer to a context structure.
Cause: An authentication context structure does not contain a string that describes the authentication service being used.
Action: If it is possible, enable tracing and attempt to reproduce the problem. In any event, contact Oracle Support Services.
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. 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 Support Services.
Cause: The server's response in negotiation was in error. 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 Support Services.
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 Oracle Support Services.
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 Oracle Support Services.
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 Oracle Support Services.
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 Oracle Support Services.
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 Oracle Support Services.
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 Oracle Support Services.
Cause: An encryption or crypto-checksumming algorithm "control" function was called, but did not recognize the "type" argument it was given. 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 Support Services.
Cause: A native service attempted 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 Oracle Support Services.
Cause: The key returned by negotiation was smaller than the size requested by some service (either encryption or crypto-checksumming).
Action: The error is not normally visible. If the error persists, enable tracing to reproduce the problem and contact Oracle Support Services.
Cause: An error occurred while the two sides of the connection were negotiating an encryption or crypto-checksumming key.
Action: The error is not normally visible. If the error persists, enable tracing to reproduce the problem and contact Oracle Support Services.
Cause: No appropriate 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 Oracle Support Services.
Cause: The sqlnet.crypto_seed parameter is missing from the SQLNET.ORA parameters file for SQL*Net.
Action: Add this line to SQLNET.ORA:
sqlnet.crypto_seed = "randomly-chosen text"
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.
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 Oracle Support Services.
Cause: The ANO encryption/crypto-checksumming service detected an error while running tests on the active encryption or checksumming algorithm.
Action: Contact Oracle Support Services.
Cause: The authentication type selected by the server does not match that picked by the client.
Action: Contact Oracle Support Services.
Cause: The operation succeeded.
Action: No action necessary.
Cause: Some required command-line arguments are missing.
Action: Re-enter the command using the correct arguments.
Cause: The network library could not be initialized. This is an internal error which should not normally be visible.
Action: Ensure that memory is available to run the application and that there are no other operating system problems, and then attempt the command again.
Cause: The service name you are attempting to ping is too long.
Action: Re-enter the command using the correct service 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.
Cause: The TNSPING utility found the requested address or service name, but received an internal error when trying to use it. This is an internal error which should not normally be visible.
Action: Ensure that memory is available to run the application and that there are no other operating system problems, and then attempt the command again.
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.
Cause: The TNSPING utility received an internal error when generating an address. This is an internal error which should not normally be visible.
Action: Ensure that memory is available to run the application and that there are no other operating system problems, and then attempt the command again.
Cause: The operation succeeded, in this amount of time.
Action: No action necessary.
Cause: An I/O operation failed, perhaps due to a resource failure or premature window termination. This is an internal error which should not normally be visible.
Action: Do not close the TNSPING window before all I/O operations have completed.
Cause: Prints out the path of the parameter files(sqlnet.ora,tnsnames.ora) used in the process of resolving the NAME.
Cause: Prints out the name of the adapter which resolved the TNS alias.
Cause: The route could either not connect, or encountered an unsupported version of SQL*Net.
Action: Check if SQL*Net along all nodes is version 2.3 or greater.
Cause: Some required command-line arguments are missing.
Action: Re-enter the command using the correct arguments.
Cause: Any version of SQL*Net before 2.3 does not support TRCROUTE.
Action: Find the node that is not responding to TRCROUTE.
Cause: Improper standard input connection from the terminal.
Action: Normally not visible to the user. Start the CMCTL program again. If the error persists, contact Oracle Support Services.
Cause: The Connection Manager could not be started.
Action: Check the Connection Manager configuration file for errors and confirm that no other programs are using the ADDRESS(es) specified. If the error continues, turn on tracing in the Connection Manager and examine the trace files to determine the cause of the problem. Be sure to turn tracing off when the problem has been resolved.
Cause: Improper command sent to the Connection Manager or the Connection Manager is not responding. This message is not normally visible to the user.
Action: Verify that the command sent to the Connection Manager is valid. Also check that the Connection Manager is running by using the CMCTL STATUS command. If necessary, start the Connection Manager using the CMCTL START command.
Cause: The Connection Manager Admin could not be started.
Action: Check to make sure that executable for the Connection Manager Admin (CMADMIN) exist in the Oracle home directory. If the error continues, turn on tracing in the Connection Manager Admin and examine the trace file to determine the cause of the problem. Be sure to turn tracing off when the problem has been resolved.
Cause: The Connection Manager Admin is not responding or is not running.
Action: Check that the Connection Manager Admin is running by using the CMCTL STATUS command. If necessary, start the Connection Manager Admin using the CMCTL START command.
Cause: The HOST variable was not set.
Action: Set the variable HOST properly and restart the CMCTL program.
Cause: The pointer HOST is set to an unknown host name.
Action: Set the pointer HOST properly and restart CMCTL program.
Cause: Connection could not be properly established to a Connection Manager. This may be because the Connection Manager specified is not running.
Action: Check that the Connection Manager is running by using the STATUS command. If necessary, start the Connection Manager using the START command. If it is running and the error persists, contact Oracle Support Services.
Cause: Connection could not be properly established to a Connection Manager Admin. This may be because the Connection Manager Admin specified is not running.
Action: Make sure the Connection Manager Admin is running by using the STATUS command. If necessary, start the Connection Manager Admin using the START command. If it is running and the error persists, contact Oracle Support Services.
Cause: Internal NS error; connection may be lost.
Action: Make sure the connection is properly established. If the error persists, then contact Oracle Support Services.
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 Support Services.
Cause: Could not open standard terminal input. This is an internal error, not normally visible to the user.
Action: Restart the CMCTL program. If the error persists, contact Oracle Support Services.
Cause: Could not close terminal input channel. This is an internal error, not normally visible to the user.
Action: Restart the CMCTL program. If the error persists, contact Oracle Support Services.
Cause: This is an internal NS error. Connection may be lost.
Action: If the error persists, contact Oracle Support Services.
Cause: This is an internal NS error. Connection may be lost.
Action: If the error persists, contact Oracle Support Services.
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.
Cause: CMAN.ORA does not contain Connection Manager data.
Action: Define the correct data for the Connection Manager, then restart the CMCTL program.
Cause: CMAN.ORA does not contain a CMANAGER_NAME component.
Action: Define the correct name for the CMANAGER_NAME, then restart the CMCTL program.
Cause: Configuration files do not contain an ADDRESS/ADDRESS_LIST component.
Action: Define the Connection Manager ADDRESS(es) in the CMAN.ORA file and then restart the CMCTL program.
Cause: The Connection Manager Admin is not running.
Action: Verify that the Connection Manager Admin is running by doing a status request on the Connection Manager Admin. If necessary, start the Connection Manager Admin using the START command.
Cause: The Oracle environment is set up incorrectly.
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 CMCTL. Make sure the Oracle environment includes the correct directories.
Cause: The Connection Manager's name to address definition is missing.
Action: Check TNSNAMES.ORA file and make sure to include a definition for the name specified.
Cause: The Connection Manager Admin's name to address definition is missing.
Action: Check TNSNAMES.ORA file and make sure to include a definition for the name specified.
Cause: Problem interfacing to the protocol adapters installed.
Action: Normally not visible to the user. Try starting CMCTL again. If the error persists, check the product installation. If it is correct, contact Oracle Support Services.
Cause: Problem interfacing with TNS.
Action: Normally not visible to the user. Try starting CMCTL again. If the error persists, check the product installation. If it is correct, contact Oracle Support Services.
Cause: Problem with internal TNS module NL.
Action: Normally not visible to the user. Try starting CMCTL again. If the error persists, check the product installation. If it is correct, contact Oracle Support Services.
Cause: Problem with internal Connection Manager.
Action: Normally not visible to the user. Try starting CMCTL again. If the error persists, check the product installation. If it is correct, contact Oracle Support Services.
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 CMAN.ORA and the error files for the Connection Manager and Connection Manager Admin.
Action: Check that all environment variables are defined correctly and that all configuration files exist in their correct places.
Cause: Problem while reading from Connection Manager or Connection Manager Admin error files generated by the Connection Manager or Connection Manager Admin when they have failed to start.
Action: Check that a standard Network Error directory exists and that all privileges on the directory are appropriate.
Cause: Failed to open Connection Manager or Connection Manager Admin 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.
Cause: An unacceptable string was encountered while attempting to send a message to either the Connection Manager or Connection Manager Admin. The addresses provided for either the Connection Manager or Connection Manager Admin may be incorrectly constructed.
Action: Check all address strings in configuration file (TNSNAMES.ORA) and assure that they are properly formed. If all is correct, contact Oracle Support Services.
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 Connection Manager executables (CMADMIN, CMGW) and the current setting of the search path. If necessary, terminate other applications to free up machine resources. If the error persists, contact Oracle Support Services.
Cause: Problem while opening specified trace file because of errors in CMAN.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.
Cause: There is a Connection Manager already running and listening on the same addresses.
Action: No action required. The Connection Manager is already running.
Cause: There is a Connection Manager Admin already running and listening on the same addresses.
Action: No action required. The Connection Manager Admin is already running.
Cause: The Connection Manager that is being stopped has active connections going through. This is the confirmation message.
Action: Respond by typing "y" or "n". Answering "y" will cause the active database connection to be dropped; this is not generally recommended.
Cause: There was an attempt to contact a default Connection Manager where there was no CMAN.ORA present in the correct directory.
Action: Create an CMAN.ORA file. Make sure it is placed in the correct directory and includes the correct name for the Connection Manager you wish to contact.
Cause: There was an attempt to contact a Connection Manager on a specific address which is not responding.
Action: Check that the Connection Manager is actually listening on that address.
Cause: There was an attempt to contact a Connection Manager Admin on a specific address which is not responding.
Action: Check that the Connection Manager Admin is actually listening on that address.
Cause: There was an attempt to contact a Connection Manager Admin using the IPC address which is not responding.
Action: Check that the Connection Manager Admin is actually running.
Cause: A command was entered that does not exist, or request other than STATUS was made to a remote Connection Manager.
Action: Check the Oracle9i Net Services Administrator's Guide for a list of CMCTL commands or type HELP for a list of valid commands.
Cause: A trace level was not specified.
Action: Specify a trace level and retry the command.
Cause: An invalid command was entered.
Action: Check the Oracle9i Net Services Administrator's Guide or type HELP for a list of valid commands.
Cause: CMCTL 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.
Cause: CMCTL was unable to find the CMANAGER_NAME parameter in CMAN.ORA.
Action: Check that the CMAN.ORA file is properly constructed.
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 CMCTL on the Connection Manager machine.
Cause: Help message displayed by CMCTL.
Action: No action required.
Cause: Help message displayed by CMCTL.
Action: No action required.
Cause: Help message displayed by CMCTL.
Action: No action required.
Cause: Help message displayed by CMCTL.
Action: No action required.
Cause: Help message displayed by CMCTL.
Action: No action required.
Cause: Help message displayed by CMCTL.
Action: No action required.
Cause: Help message displayed by CMCTL.
Action: No action required.
Cause: Help message displayed by CMCTL.
Action: No action required.
Cause: Help message displayed by CMCTL.
Action: No action required.
Cause: Help message displayed by CMCTL.
Action: No action required.
Cause: Help message displayed by CMCTL.
Action: No action required.
Cause: Help message displayed by CMCTL.
Action: No action required.
Cause: Help message displayed by CMCTL.
Action: No action required.
Cause: Help message displayed by CMCTL.
Action: No action required.
Cause: Help message displayed by CMCTL.
Action: No action required.
Cause: Help message displayed by CMCTL.
Action: No action required.
Cause: Help message displayed by CMCTL.
Action: No action required.
Cause: Help message displayed by CMCTL.
Action: No action required.
Cause: Help message displayed by CMCTL.
Action: No action required.
Cause: Help message displayed by CMCTL.
Action: No action required.
Cause: Control program general message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Control program usage message.
Action: No action required.
Cause: Possibly garbled password entered.
Action: Re-enter the CMAN password, using valid ASCII characters. If the problem persists, contact Oracle Support Services.
Cause: Control program status message.
Action: No action required.
Cause: Control program general message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Control program status message.
Action: No action required.
Cause: Trace file name argument is missing.
Action: Put the trace file name as the last command line argument for this tool.
Cause: The file_name and/or the options arguments are missing.
Action: Put the right number of command line arguments.
Cause: The options provided are not valid.
Action: Check the valid options for this tool.
Cause: The trace file name given does not exist or it is not accessible for this user.
Action: Check the spelling, and permissions of the trace file.
Cause: Possible memory problem.
Action: Verify the amount of available memory on the system.
Cause: The packet type read by trcAsst is not valid.
Action: Verify that your trace file is not corrupted. If trace file looks normal, with no unexpected characters in it, contact Oracle Support Services and have the trace file ready.
Cause: The packet being decode is corrupted.
Action: Verify that your trace file is not corrupted. If trace file looks normal, with no unexpected characters in it, contact Oracle Support Services and have the trace file ready.
Cause: Fatal internal error.
Action: Contact Oracle Support Services.
Cause: Internal type error.
Action: Contact Oracle Support Services.
Cause: Reached the end of file too soon. The trace file appears to be truncated. This trace file cannot be decoded.
Action: Generate another trace file.
Cause: Internal System Error.
Action: Contact Oracle Support Services.
Cause: Not able to decode Network Authentication information.
Action: Contact Oracle Support Services.
Cause: This trace file may not be a Network trace file. The default format (Oracle Trace) will be assumed.
Action: No action required.
Cause: Trace Assistant will not retrieve all the rows' data.
Action: No action required.
Cause: An attempt was made to read beyond packet length. The trace file may be corrupted.
Action: No action required.
Cause: Trace assistant does not have enough information to decode TTC data. This maybe an old trace file or from a platform that trace assistant does not understand.
Action: No action required.
Cause: Trace Assistant has reached a point in which the TTC protocol cannot be understood.
Action: No action required.
Cause: Unable to send data. Connection probably disconnected.
Action: Re-establish connection. If the error is persistent, turn on tracing and re-execute the operation.
Cause: This is an internal error, not normally visible to the user.
Action: For further details, turn on tracing and re-execute the operation. If the error persists, contact Oracle Support Services.
Cause: Unable to send break message. Connection probably disconnected.
Action: Re-establish connection. If the error is persistent, turn on tracing and re-execute the operation.
Cause: Not currently connected to a remote host.
Action: Re-establish connection.
Cause: The service name specified is not defined correctly in the TNSNAMES.ORA file.
Action: Make the following checks and correct the error:
Cause: An internal error occurred during break handling, 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 Support Services.
Cause: An internal error occurred during break handling. 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 Support Services.
Cause: An internal error occurred during network communication. 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 Support Services.
Cause: Unable to locate parameter file.
Action: Verify that a valid parameter file exists, and is readable.
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 database administrator to get the proper permissions or use TRACE_DIRECTORY_CLIENT in SQLNET.ORA to specify a directory the user can write to.
Cause: Corrupt error reporting subsystem. 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 Support Services.
Cause: The connection may be terminated.
Action: Reconnect and try again. For further details, turn on tracing and re-execute the operation. If the error persists, contact Oracle Support Services.
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 a TNSNAMES.ORA file makes it unusable. See the Oracle9i Net Services Administrator's Guide.
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 Oracle Support Services.
Cause: The SQLNET.FDF file does not 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.
Cause: Oracle Trace does not 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.
Cause: NVstring contained DESCRIPTION/HO.
Action: Call HO agent from integrating server.
Cause: Configured to use LDAP based Directory Server.
Action: Bring the Directory Server up or change configuration to LOCAL.
Cause: The net_service_name you are attempting to resolve is too long.
Action: The maximum length of the net_service_name is 255 bytes and this limit has been exceeded. Use a smaller alias. If this is not possible, then contact Oracle Support Services.
Cause: The server shut down because connection establishment with a client failed to complete within the allotted time interval. This may be a result of network/system delays; or this may indicate that a malicious client is trying to cause a Denial of Service attack on the server.
Action: If the error occurred because of a slow network/system, then reconfigure the "sqlnet.connect_timeout" parameter in sqlnet.ora to a larger value. If a malicious client is suspected, then use the address in sqlnet.log to identify the source and restrict access. Note that logged addresses may not be reliable as they can be forged (that is, in TCP/IP).
Cause: The navigation layer received an error from TNS.
Action: See the error log file for the specific TNS 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.
Cause: Could not navigate a path through Interchanges to the destination. This error occurs if an invalid community is in the address string, or the address includes a protocol that is not available or the TNSNAV.ORA file does not have a correct CMANAGER address specified or the Interchange is down.
Action: Assure that Interchanges necessary to get to the desired destination are up and have available capacity for an additional connection. Also check that the correct community and protocol have been specified in the CMANAGER address used.
Cause: Out of memory on machine.
Action: Reconfigure machine to have more storage or run fewer applications while the Interchange is running.
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, then contact Oracle Support Services.
Cause: Internal navigation error. This message is not normally visible to the user.
Action: For further details, contact Oracle Support Services.
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.
Cause: The application using the Interchange or Connection Manager refused the connection at the listener.
Action: Make sure that the application listener at the destination is functioning correctly. If it is and the problem persists, contact Oracle Support Services.
Cause: Internal navigation error. This message is not normally visible to the user.
Action: For further details, contact Oracle Support Services.
Cause: Internal navigation error because of an unexpected TNS error.
Action: Look at the log file to find the TNS error. If necessary, turn on tracing and repeat the operation.
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.
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.
Cause: Application calling navigation routine has not properly configured the global variables. There are no TNSNAV.ORA files available, or they are defective. 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 Support Services.
Cause: Application calling navigation routine has not properly configured the TNSNAV.ORA file.
Action: Check the syntax of the TNSNAV.ORA file.
Cause: TNSNAV.ORA does not have a PREFERRED_CMANAGERS defined.
Action: Add a PREFERRED_CMANAGERS entry to the TNSNAV.ORA file.
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.
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.
Cause: There is no LOCAL_COMMUNITIES entry in TNSNAV.ORA.
Action: Define the LOCAL_COMMUNITIES for this node in the TNSNAV.ORA file.
Cause: Address binding for PREFERRED_NAVIGATORS entry is improperly entered. entry.
Action: Check your PREFERRED_NAVIGATORS entry and fix it 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.
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.
Cause: Poorly formed network configuration data. For example, a PREFERRED_CMANAGERS entry may have an incorrect CMANAGER_NAME in the client's TNSNAV.ORA file. Or an Interchange downtime parameter (TIMEOUT_INTERVAL) on the Navigator may be set to zero in INTCHG.ORA.
Action: Check the entries in TNSNAV.ORA and the Interchange configuration files and correct them. If necessary, talk with your network administrator to determine if the specified Interchanges (Connection Managers) are available and properly configured. Use the Oracle Network Manager to generate the configuration files if necessary.
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.
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.
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).
Cause: Too many TNS connections open simultaneously.
Action: Wait for connections to close and retry.
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.
Cause: Contact cannot be made with remote party.
Action: Make sure the network driver is functioning and the network is up.
Cause: The current user has exceeded the allotted resource assigned in the operating system.
Action: Acquire more operating system resources, or perform a different function.
Cause: The supplied connect descriptor contains illegal syntax.
Action: Check the syntax of the connect descriptor in TNSNAMES.ORA.
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 re-execute the operation. The trace file will include the name of the shared library (or DLL) that could not be loaded.
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.
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.
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.
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.
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 the interchange problem can be isolated.
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: No action required.
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.
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 re-execute the operation. The trace file will have the name of the shared library (or DLL) that has not been loaded.
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 re-execute 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. The Oracle Protocol Adapter that is being called may not be installed on the local hard drive. Check that the correct Protocol Adapter are successfully linked. If the error persists, contact Oracle Support Services.
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.
Cause: The SID was missing from CONNECT_DATA.
Action: Check that the connect descriptor corresponding to the service name in TNSNAMES.ORA has an SID component in CONNECT_DATA.
Cause: The SID in 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 currently registered with the listener can be obtained by typing "LSNRCTL SERVICES listener_name". These SIDs correspond to SID_NAMEs in TNSNAMES.ORA, or DB_NAMES in the INIT.ORA file.
Cause: The dispatcher terminated unexpectedly.
Action: Attempt to connect again and if the same error occurs, contact the database administrator 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.
Cause: The dispatchers appear to be busy handling other requests.
Action: Attempt the connection again. If the error persists, ask the database administrator to increase the number of dispatchers and/or dispatchers' limit on the number of connections/sessions that they can accept.
Cause: The dispatchers notified the listener that they temporarily do not accept new connections.
Action: Attempt the connection again. If the error persists, contact the database administrator to check the state of the dispatchers and/or increase the number of dispatchers.
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 database administrator to increase the number of dispatchers.
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 database administrator to register a dispatcher on your protocol.
Cause: The SERVICE_NAME in the CONNECT_DATA was not found in the listener's tables.
Action: Check to make sure that the SERVICE_NAME specified is correct.
Cause: None of the listener's known service handlers are registered as supporting the presentation protocol required by the connecting client.
Action: Check that the destination service is configured to accept the presentation protocol.
Cause: None of the known and available service handlers for the given SERVICE_NAME support the client's protocol stack: transport, session, and presentation protocols.
Action: Check to make sure that the service handlers (for example, dispatchers) for the given SERVICE_NAME are registered with the listener, are accepting connections, and that they are properly configured to support the desired protocols.
Cause: None of the known service handlers are registered as supporting direct handoff as required for this client connection.
Action: Check that the instance(s) are configured properly for direct handoff, and are versions of Oracle that support direct handoff.
Cause: The process of handing off a client connection to another process failed.
Action: Turn on listener tracing and re-execute the operation. Verify that the listener and database instance are properly configured for direct handoff. If the problem persists, contact Oracle Support Services.
Cause: The listener could not find any available service handlers that are appropriate for the client connection.
Action: Run "lsnrctl services" to ensure that the instance(s) have registered with the listener, and are accepting connections.
Cause: None of the known and available service handlers for requested type of server (dedicated or shared) are appropriate for the client connection.
Action: Run "lsnrctl services" to ensure that the instance(s) have registered with the listener and that the appropriate handlers are accepting connections.
Cause: The INSTANCE_NAME in the CONNECT_DATA was not found in the listener's tables for the specified SERVICE_NAME.
Action: Check to make sure that the specified INSTANCE_NAME is correct.
Cause: There are not any available and appropriate database instances registered with the listener, that are part of the service identified by SERVICE_NAME given in the connect descriptor and that have the specified INSTANCE_ROLE (and INSTANCE_NAME, if specified).
Action: Check to make sure that the specified INSTANCE_ROLE is correct. Run "lsnrctl services" to ensure that the instance(s) have registered with the listener and that they are ready to accept connections.
Cause: The listener could not find any available (database) instances, that are appropriate for the client connection.
Action: Run "lsnrctl services" to ensure that the instance(s) are registered with the listener, and have READY status.
Cause: The HANDLER_NAME in the CONNECT_DATA was not found in the listener's tables for the specified SERVICE_NAME and INSTANCE_NAME.
Action: Check to make sure that the specified HANDLER_NAME is correct.
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.
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 Support Services.
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.
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 Support Services.
Cause: The requested connection 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.
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.
Cause: "End of file" condition has been reached; partner has disconnected. This is an informational message.
Action: No action required.
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 the typographical 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).
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 re-execute the operation; contact Oracle Support Services.
Cause: Too many TNS connections open simultaneously.
Action: Wait for connections to close and retry.
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.
Cause: Specified listener address is already being used.
Action: Start your listener with a unique address.
Cause: Contact cannot be made with remote party.
Action: Make sure the network driver is functioning and the network is up.
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 Support Services.
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). If the protocol is TCP/IP, edit the TNSNAMES.ORA file to change the host name to a numeric IP address and try again.
Cause: User has insufficient privileges to perform the requested operation.
Action: Acquire necessary privileges and try again.
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.
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 Support Services.
Cause: The current user has exceeded the allotted resource assigned in the operating system.
Action: Acquire more operating system resources, or perform a different function.
Cause: The supplied connect descriptor contains illegal syntax.
Action: Check the syntax of the connect descriptor in TNSNAMES.ORA.
Cause: The supplied connect descriptor is missing one or more TNS keywords.
Action: Check the syntax, and ensure all required keywords are present.
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 Support Services.
Cause: An internal operation is still in progress. 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 Support Services.
Cause: User has insufficient privileges to perform the requested operation.
Action: Acquire necessary privileges and try again.
Cause: TNS detected an incoming connect request but there was no caller. 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 Support Services.
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 re-execute the operation. The trace file will include the name of the shared library (or DLL) that could not be 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 re-execute the operation. The trace file will have the name of the shared library (or DLL) that has not been loaded.
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 re-execute the operation. Turn off tracing when the operation is complete.
Cause: A generic protocol error occurred.
Action: For further details, turn on tracing and re-execute the operation.
Cause: Bad 'gbh' argument passed to TNS from caller. System may have been linked with old libraries. This is an internal error. This message is not normally visible to the user.
Action: Contact Oracle Support Services.
Cause: The connect request was denied by the remote user (or TNS software). This message is not normally visible to the user.
Action: For further details, turn on tracing and re-execute the operation.
Cause: An unexpected TNS protocol error has occurred.
Action: For further details, turn on tracing and re-execute the operation. If the error persists, contact Oracle Support Services.
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 re-execute the operation.
Cause: An error occurred during a data receive. 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 Support Services.
Cause: An error occurred during a data send. This message is not normally visible to the user.
In addition, this message could occur when any of the following SQL*Plus commands have been issued:
Action: For further details, turn on tracing and re-execute the operation. If the error persists, contact Oracle Support Services.
Cause: The connect request failed because it would have required redirection and the caller has requested no redirections. 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 Support Services.
Cause: An internal function received an invalid request. 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 Support Services.
Cause: A send operation has been requested but partner has already disconnected. 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 Support Services.
Cause: A receive operation has completed with insufficient data to satisfy the user's request. 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 Support Services.
Cause: An attempt to hand-off a connection from one process to another has failed because the protocol provider does not support it. 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 Support Services.
Cause: An attempt to perform an I/O operation failed because no buffer was available. 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 Support Services.
Cause: The TNS software is unable to signal an event occurrence.
Action: For further details, turn on tracing and re-execute the operation. If the error persists, contact Oracle Support Services.
Cause: An ill-formed packet has been detected by the TNS software.
Action: For further details, turn on tracing and re-execute the operation. If the error persists, contact Oracle Support Services.
Cause: An attempt to solicit network event activity has failed because no connections are registered for event notification. 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 Support Services.
Cause: TNS is unable to get requested confirmation acknowledgment from remote partner. 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 Support Services.
Cause: TNS has detected an internal inconsistency. This message is not normally visible to the user.
Action: For further details, turn on tracing and re-execute the operation and contact Oracle Support Services.
Cause: Illegal use of connect descriptor. This is an internal error. 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 Support Services.
Cause: The registration of a product banner with the Oracle server failed.
Action: Enable tracing and attempt to repeat the error. If it occurs again, contact Oracle Support Services.
Cause: The data received is not the same as the data sent.
Action: Attempt the transaction again. If the error persists, check (and correct) the integrity of your physical connection.
Cause: The creation of a string in Oracle NLS format failed. This is an internal error.
Action: Enable tracing and attempt to repeat the error. If it occurs again, contact Oracle Support Services.
Cause: The TNS information flags set by the process prior to connection negotiation were not present after the negotiation was finished. This is an internal error.
Action: Enable tracing and attempt to repeat the error. If it occurs again, contact Oracle Support Services.
Cause: The operation failed because maximum active current connections has been reached. It may not be a real error when the Connection Pooling feature is enabled. It is possible that the application later re-issues the operation and successfully grabs the connection pool slot and proceeds.
Action: This is an internal error. Enable tracing and attempt to repeat the error. If it occurs again, then contact Oracle Support Services.
Cause: The operation was aborted because it did not complete within the specified allotted time interval.
Action: This is an error which does not normally appear at the high level. The action to take is application specific, and is detailed in the higher level error description.
Cause: Attempted operation is not portable. 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 Support Services.
Cause: Attempted operation failed because it conflicts with an on-going action or status of the connection. 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 Support Services.
Cause: A request to service an event failed because no event notification has yet been posted. 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 Support Services.
Cause: The TNS software is unable to enable event signals. 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 Support Services.
Cause: The operation failed because the type of data specified is unknown. 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 Support Services.
Cause: The two machines are running incompatible versions of TNS.
Action: Check the version numbers, and upgrade the machine with the smaller one.
Cause: The connect request failed because requested service could not be provided by the local TNS software.
Action: If appropriate, re-execute with reduced service requirements.
Cause: The connect request failed because a requested transport characteristic could not be supported by the remote TNS software.
Action: If appropriate, re-execute with reduced requirements.
Cause: An attempt to register a connection for event notification failed because the event notification type conflicts with existing registrations. This message is not normally visible to the user.
Action: For further details, turn on tracing and re-execute the operation and contact Oracle Support Services.
Cause: Connection is half-duplex and a full-duplex operation was attempted. 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 Support Services.
Cause: An attempt to register a connection for event notification failed because the connection is already registered. This message is not normally visible to the user.
Action: For further details, turn on tracing and re-execute the operation and contact Oracle Support Services.
Cause: An operation failed because an argument was missing. This message is not normally visible to the user.
Action: For further details, turn on tracing and re-execute the operation and contact Oracle Support Services.
Cause: An attempt to register a connection for event notification failed because the event type is unknown. This message is not normally visible to the user.
Action: For further details, turn on tracing and re-execute the operation and contact Oracle Support Services.
Cause: An attempt to register a connection for event notification failed because asynchronous callbacks are not available. This message is not normally visible to the user.
Action: For further details, turn on tracing and re-execute the operation and contact Oracle Support Services.
Cause: An attempt to register a connection for event notification failed because the ability to test for events is not available. This message is not normally visible to the user.
Action: For further details, turn on tracing and re-execute the operation and contact Oracle Support Services.
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.
Cause: The authentication service failed to retrieve the name of a user.
Action: Enable tracing to determine which routine is failing.
Cause: The authentication service failed to retrieve one of the user's roles.
Action: Enable tracing to determine which routine is failing.
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.
Cause: Process was unable to allocate memory.
Action: Terminate other processes in order to reclaim needed memory.
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.
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 Oracle Support Services.
Cause: A process was unable to receive a packet from another process. Possible causes include:
Action: If the cause is not obvious, contact Oracle Support Services.
Cause: The authentication service failed to retrieve the credentials of a user.
Action: Enable tracing to determine the exact error.
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 include:
Cause: The function specified in the authentication table entry for the service failed.
Action: Enable tracing to determine the exact error.
Cause: The authentication service failed during initialization.
Action: Enable tracing to determine the exact error.
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.
Cause: The client process received an error from the server that indicated that an internal SQL*Net native services error had occurred.
Action: Enable tracing on both processes and attempt to re-create the problem. If successful in recreating the problem, contact Oracle Support Services.
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.
Cause: A SQLNET.ORA parameter from which a value was needed does not exist.
Action: Set the parameter in the parameter file.
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.
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.
Cause: A SQL*Net list-of-algorithms parameter was empty; for example, "()".
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.
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.
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.
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 Oracle Support Services.
Cause: Not enough memory was allocated for a string so it had to be truncated
Action: If it is not a problem 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.
Cause: The control function utilized by the authentication service driver failed.
Action: Enable tracing to determine the exact error.
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.
Cause: The authentication service being used was unable to verify the provided password.
Action: Enable tracing to determine the exact error.
Cause: The cryptographic checksum received with a packet of incoming data did not 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.
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.
Cause: A client process that is running an earlier version of TNS attempted to connect but the connection failed because the server process required that an ANO service (authentication, encryption, and so on) be used.
Action: Relink the calling executable and retry the connection or eliminate the requirement that the service be used on the server side.
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.
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 the 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.
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 Oracle Support Services.
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.
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).
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).
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 Oracle Support Services.
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 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 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.
Cause: The protocol specified for an externally-identified outbound connection from a shared server (database link) was not the same 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.
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.
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 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.
Cause: A password supplied for a role could not be validated by the authentication service.
Action: Supply the correct password.
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 Oracle Support Services if the reason is not obvious.
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.
Cause: A connection was marked as being a proxy connection (database link) from a dedicated server but no inbound context was present.
Action: This error should not normally be visible to the user. Contact Oracle Support Services.
Cause: A connection was marked as being a proxy connection (database link) from a shared server but no inbound context was present.
Action: This error should not normally be visible to the user. Contact Oracle Support Services.
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 informational message and should not normally be visible to the user. If the error does appear, contact Oracle Support Services.
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 re-create the problem. If the problem recurs, contact Oracle Support Services.
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.
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.
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.
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.
Cause: The SecurID card that is used to logon to Oracle, does not have a pin code assigned to it.
Action: Use one of the programs supplied by Security Dynamics to assign a pin code to the card.
Cause: The SecurID card and the SecurID server are out of sync and the server requires the next card code to resynchronize the card.
Action: Use one of the programs supplied by Security Dynamics to resynchronize the SecurID card.
Cause: The sqlnet.crypto_seed parameter is missing from the SQLNET.ORA parameters file for SQL*Net.
Action: Add this line to SQLNET.ORA:
sqlnet.crypto_seed = "randomly-chosen text"
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.
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.
Cause: An operation which does not exist was specified for a native service. This is a programming error and should not normally be visible to the user.
Action: Contact Oracle Support Services.
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.
Cause: There are a number of reasons why the SecurID server would refuse a pin code:
Action: Re-execute the operation and make sure to use a pin code 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.
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 Advanced Networking Option, and that the Authentication Adapter supports Server Authentication.
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.
Cause: A Secure Protocol Adapter was used that has Encryption turned ON as well as ASO Encryption.
Action: Turn OFF either ASO Encryption or the Protocol Adapter Encryption if possible. Refer to the Oracle Advanced Security Administrator's Guide for information about how to do this.
Cause: An internal error occurred in the native services component.
Action: Enable tracing to determine the exact error. Contact Oracle Support Services.
|
 Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|
