Release 8.0
A54625_01
 Library |
 Product |
 Contents |
| Oracle8 Error Messages Release 8.0 A54625_01 |
|
Cause: The Oracle Enterprise Manager is not running.
Action: Start Oracle Enterprise Manager.
Cause: The application failed to stop the node from being monitored.
Action: Make sure Oracle Enterprise Manager is running. Because the resource may have been locked at that time, retry the operation.
Cause: The application failed to remove the node's retry operations from the repository.
Action: Make sure the repository is running.
Cause: The application failed to store the node's retry operations in the repository.
Action: Make sure the repository is running.
Cause: The application failed to get the details necessary for it to connect to the repository.
Action: Make sure that Oracle Enterprise Manager is running and that a user has made a connection to the repository.
Cause: The application failed to get the names and contact times of the nodes the Oracle Daemon intends to retry.
Action: Make sure Oracle Enterprise Manager is running.
Cause: The application failed to get the names and contact times of the nodes the Oracle Daemon is monitoring.
Action: Make sure Oracle Enterprise Manager is running.
Cause: The application filed to stop the node from being retried.
Action: Make sure Oracle Enterprise Manager is running.
Cause: The application failed during an OLE Automation call.
Action: Make sure Oracle Enterprise Manager is running.
Cause: The application failed to save the user's state in the repository.
Action: This means the repository connection has been lost. The state cannot be recovered.
Cause: The application failed to create a mutex for thread synchronization.
Action: Shut down some applications.
Cause: The application failed to create an event for thread synchronization.
Action: Shut down some applications.
Cause: The application failed to initialize OLE.
Action: Shut down some applications.
Cause: The application failed to open the specified key in the NT Registry.
Action: Make sure the application has the correct permissions.
Cause: The application failed to initialize the Oracle CORE library.
Action: Make sure Oracle CORE has ben installed properly.
Cause: The application failed to initialize the Oracle Network Library.
Action: Make sure SQL*Net has been installed properly.
Cause: The application failed to initialize the Oracle Remote Operations library.
Action: Make sure SQL*Net has been installed properly.
Cause: The application failed to create a semaphore for thread synchronization.
Action: Shut down some applications.
Cause: The application failed to create a queue.
Action: Shut down some applications.
Cause: The application failed to create a thread.
Action: Shut down some applications.
Cause: The application failed to get the names of the application users for which pending notifications exist.
Action: Make sure Oracle Enterprise Manager is running.
Cause: The application failed to stop the user from getting queued notifications.
Action: Make sure Oracle Enterprise Manager is running.
Cause: The application failed to get the specified value from the NT registry.
Action: Make sure the application has the correct permissions to access the NT registry and that the value exists.
Cause: The application failed to initialize the NT WINSOCK library necessary to use the TCP/IP network protocol.
Action: Make sure the operation system network software is installed properly.
Cause: The application failed to get the name of the local host necessary for it to use the TCP/IP network protocol.
Action: Make sure the operating system network software is installed properly.
Cause: The application failed to get the IUknown OLE interface of its document class.
Action: Make sure OLE is installed properly.
Cause: The application failed to map the specified CLSID to its associated PROGID.
Action: Make sure Oracle Enterprise Manager software is installed properly.
Cause: The application failed to register the active object of its document class.
Action: Make sure OLE is installed properly.
Cause: The application failed to set the specified value in the NT registry.
Action: Make sure the application has the correct permissions to access the NT registry.
Cause: The application failed to open the specified value in the NT registry.
Action: Make sure the application has the correct permissions to access the NT registry and that the key exists.
Cause: The application failed to remove the specified value from the NT registry.
Action: Make sure the application has the correct permissions to access the NT registry and that the key exists.
Cause: The application failed to find the address of the agent on the specified node.
Action: Make sure the Oracle Enterprise Manager is running and that the agent is known to it.
Cause: The application failed to register the user with the agent on the specified node.
Action: Make sure the agent is running.
Cause: The application failed to contact the agent on the specified node.
Action: Make sure the agent is running.
Cause: Oracle Enterprise Manager is not running, so it is only possible to change configuration parameters.
Action: Start Oracle Enterprise Manager.
Cause: The address you entered is not a valid SQL*Net TNS address.
Action: Review the Oracle Network Manager Administrator's Guide.
Cause: A WINSOCK occurred during service auto discovery.
Action: Review the Microsoft Windows NT WINSOCK error codes.
Cause: An attempt to get a session to the repository failed.
Action: Start Oracle Enterprise Manager again.
Cause: An attempt to allocate memory failed.
Action: Start Oracle Enterprise Manager again.
Cause: The table SMP_AD_ADDRESSES has not been created in the repository.
Action: Run the script smpdccre.sql.
Cause: The table SMP_AD_ADDRESSES contains no rows.
Action: Run service auto discovery.
Cause: An attempt to copy a file failed.
Action: Check the existence and permission of files.
Cause: The agent failed to return the file dbsnmp.ver.
Action: Check the existence and permission of files.
Cause: The agent failed to accept a connection on its spawn address.
Action: Retry the operation or restart the agent.
Cause: The agent failed to return the file services.ora.
Action: Check the existence and permission of files.
Cause: There is a syntax error in TNSNAMES.ORA file.
Action: Correct the syntax error and try the operation again.
Cause: The application was unable to get more memory from the system.
Action: Start the application again.
Cause: The application was unable to locate a valid SQL*Net address for the indicated agent.
Action: Add the address into the SQL*Net configuration file tnsnames.ora.
Cause: The daemon process (vod.exe) was unable to perform a network listen. The nttnt.dll was not installed (i.e. the TCP/IP Protocol Adapter was not installed) or the default port of 7770 is already being used.
Action: If the user sees the following lines in sqlnet.ora, a trace file is generated. Assuming that ORACLE_HOME is located in c:\orant, he should see
daemon.trace_level = 16
daemon.trace_directory = c:\orant\network\trace
Look in c:\orant\network\trace and open daemon.trc. Look for nslisten and check for any error indications. Run Daemon Manager to configure the port. The Listening Address parameter should read "Not Found." This is a message indicating that the parameter does not exist in the NT registry. To ensure that the parameter does not exist, double click the Listening Address line and press the Remove button.
