Release 8.0.4
A58312-01
 Library |
 Product |
 Contents |
 Index |
| Oracle8 Error Messages Release 8.0.4 A58312-01 |
|
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: Not normally visible to the user. May indicate a shortage of memory.
Action: If error persists contact Worldwide Customer Support.
Cause: Parameter file process failed.
Action: Check to make sure that all parameter files necessary for the Interchange are present (TNSNAV.ORA, TNSNET.ORA and INTCHG.ORA). If these files are present and properly configured, turn on tracing and repeat the operation. Turn off tracing when the trace is complete. Look in the trace file for errors in the parameter loading process. If error persists contact Worldwide Customer Support.
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 error persists contact Worldwide Customer Support.
Cause: Unable to access or obtain write permission to create log file.
Action: Check existence of or access to log file directory.
Cause: Not normally visible to the user.
Action: If error persists contact Worldwide Customer Support.
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 user.
Action: Increase the resources on your machine. If error persists contact Worldwide Customer Support.
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 start-up 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: Internal error. Should not normally occur.
Action: Contact Worldwide Customer Support.
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 Worldwide Customer Support.
Cause: Internal error. Data expected has not arrived yet.
Action: If error persists, contact Worldwide Customer Support.
Cause: No PUMP_CONNECTIONS parameter specified in INTCHG.ORA.
Action: Add PUMP_CONNECTIONS parameter to INTCHG.ORA. If the file is generated by the Oracle Network Manager, this error should not occur.
Cause: No PUMPS parameter specified.
Action: Add an appropriate number of PUMPS to INTCHG.ORA. Use the Oracle Network Manager to generate the configuration files.
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. This will happen automatically if the Oracle Network Manager is used.
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: - Internal error. Should not normally occur.
Action: If problem persists contact Worldwide Customer Support.
Cause: Error in the TNSNET.ORA file.
Action: Check the contents of TNSNET.ORA and eliminate errors. Regenerate the configuration files using the Oracle Network Manager.
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 using the Oracle Network Manager.
Cause: One or more Connection Manager names are missing.
Action: Ensure that each Connection Manager name is defined in TNSNET.ORA. Regenerate TNSNET.ORA using the Oracle Network Manager.
Cause: One or more ADDRESSes does not have a COMMUNITY assigned.
Action: Ensure that all addresses have a COMMUNITY defined in TNSNET.ORA.
Cause: Internal Error. Should not normally occur. There may be a resource limitation problem on the machine.
Action: Stop and restart Interchange. If possible, make more memory available on the machine. If problem persists, contact Worldwide Customer Support.
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: Internal error in Interchange.
Action: Check that you are using compatible components of the Interchange product, using the INTCTL VERSION command. If problem persists call Worldwide Customer Support.
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: None.
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: Operation must be retried with a larger buffer.
Cause: The Connection Manager was unable to start a pump during start-up.
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 call Worldwide Customer Support.
Cause: Improperly formed connect data sent to the Interchange listener.
Action: If problem persists, check the application using the Interchange (it may be closing down or crashing). Call Worldwide Customer Support if the problem cannot be located.
Cause: Internal - error could not redirect call to a pump or other Interchange listener. The cause may be insufficient network or machine resources.
Action: Add resources or close some running applications in order to free up resources. If error persists, call Worldwide Customer Support.
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: 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: None, but if the problem persists call Worldwide Customer Support.
Cause: A pump became an orphaned process. A protocol adapter is not working properly or machine network resources are being over used.
Action: This error is not immediately fatal; the orphaned pump may continue to function. Restart the Interchange when convenient. If the problem persists, call Worldwide Customer Support.
Cause: Internal problem with data passed back from pump.
Action: None.
Cause: Destination for call is unavailable.
Action: None.
Cause: Unable to create a new process; possibly there are too many processes on the machine.
Action: Free machine resources by exiting other applications on the Interchange machine. If the problem continues you may need more memory on the machine. If you believe there are sufficient resources on the machine but the problem persists, contact Worldwide Customer Support.
Cause: Pump log message sent to Interchange listener.
Action: None.
Cause: Error log message sent from pump to indicate failure in initiating connection because of errors in the call string: network problem or resource limitations.
Action: None.
Cause: Pump call to destination failed.
Action: Check destination.
Cause: Connect data supplied for error 00233.
Action: None
Cause: Pump aborting connection because connection has been up too long, or some other network error on the connection.
Action: None.
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: None.
Cause: Message sent back to control program from Interchange.
Action: None.
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: NS test operation failed due to internal error.
Action: If the problem persists there may be a network problem or resource limitations on the machine. If these do not seem to be causing the problem, call Worldwide Customer Support.
Cause: Command requested did not exist.
Action: None.
Cause: TNSNET.ORA is poorly configured or nonexistent.
Action: Check to make sure that TNSNET.ORA is properly configured.
Cause: Response from Navigator when a particular request failed.
Action: None.
Cause: Message sent to the Interchange control program when reload of network configuration failed. TNSNET.ORA Poorly configured or missing.
Action: None.
Cause: Message sent to Interchange control program when reload of network is successful.
Action: None.
Cause: Request was made to Navigator that it knows nothing about.
Action: None.
Cause: Generated when a request was made to the Navigator it knows nothing about.
Action: None.
Cause: Message sent back to control program from Navigator.
Action: None.
Cause: Message sent back to control program from Navigator.
Action: None.
Cause: Message sent back to control program from Navigator.
Action: None.
Cause: Message sent back to control program from Connection Manager.
Action: None.
Cause: Message sent back to control program indicating that the connection manager is secure.
Action: None.
Cause: Request sent by Interchange control program is unknown.
Action: None.
Cause: Message sent back by the Navigator indicating an invalid trace level.
Action: Re-attempt the request with a correct trace level.
Cause: Message sent back by the Connection Manager indicating an invalid trace level.
Action: Re-attempt the request with a correct trace level.
Cause: Request sent by the Navigator to control program indicating that it could not reopen log file after rereading parameter data.
Action: None.
Cause: Request sent by the Connection Manager to control program indicating that it could not reopen log file after rereading parameter data.
Action: None.
Cause: Message sent back to control program from Navigator.
Action: None.
Cause: Message sent back to control program from Connection Manager.
Action: None.
Cause: Message sent back to control program from Connection Manager.
Action: None.
Cause: Message sent back to control program from Connection Manager.
Action: None.
Cause: Protocol Adapter errors which go with message 233
Action: None.
Cause: Could not allocate a large enough area to get pump statistics; continue without them.
Action: None.
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 shutdown and restart the Interchange to make the changes take effect.
Cause: Connection Manager is not running.
Action: Start the Connection Manager and retry
