Release 8.0.4
A58312-01
 Library |
 Product |
 Contents |
 Index |
| Oracle8 Error Messages Release 8.0.4 A58312-01 |
|
Cause: Improper standard input connection from the terminal.
Action: Normally not visible to the user. Start the CMCTL program again. If error persists, contact Worldwide Customer Support.
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 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 rectified.
Cause: Improper command sent to the Connection Manager or the Connection Manager is not responding. 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 the executable for the Connection Manager Admin (sfpadmin) exists in the ORACLE home directory. If 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 rectified.
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 hostname.
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 Worldwide Customer Support.
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 Worldwide Customer Support.
Cause: Internal NS error; connection may be lost.
Action: Make sure the connection is properly established. If the error persists, then contact Worldwide Customer Support.
Cause: Internal NS error. Error in closing down connections.
Action: Make sure the networking protocol being used is properly installed on the machine. If the error persists contact Worldwide Customer Support.
Cause: Could not open standard terminal input. Internal error.
Action: Normally not visible to the user. Restart the CMCTL program. If error persists, contact Worldwide Customer Support.
Cause: Could not close terminal input channel. Internal error.
Action: Normally not visible to the user. Restart the CMCTL program. If error persists, contact Worldwide Customer Support.
Cause: Internal NS error. Connection may be lost.
Action: If the error persists contact Worldwide Customer Support.
Cause: Internal NS error. Connection may be lost.
Action: If the error persists contact Worldwide Customer Support.
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 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 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 Worldwide Customer Support.
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 Worldwide Customer Support.
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 Worldwide Customer Support.
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 Worldwide Customer Support.
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, please contact Worldwide Customer Support.
Cause: An error was encountered while spawning a process due to an internal operating system dependent problem. Machine resources may be limited.
Action: Retry command. Check permissions on Connection Manager executables (sfpadmin, sfpgw) and the current setting of the search path. If necessary, terminate other applications to free up machine resources. If the error persists, contact Worldwide Customer Support.
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: None; the Connection Manager is already running.
Cause: There is a Connection Manager Admin already running and listening on the same addresses.
Action: None; 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 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 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: The user entered a command that does not exist, or the user tried to make a request other than STATUS to a remote Connection Manager.
Action: Check the Net8 Administrator's Guide for a list of CMCTL commands or type HELP for a list of valid commands.
Cause: The user did not specify a trace level.
Action: Specify a trace level and retry command.
Cause: The user entered an invalid command.
Action: Check the Net8 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 to execute any command other than status and version, you must run CMCTL on the Connection Manager machine.
