Release 8.0
A54625_01
 Library |
 Product |
 Contents |
| Oracle8 Error Messages Release 8.0 A54625_01 |
|
Cause: The specified service could not contact the SNMP master agent. The master agent supported by Oracle for this platform is not installed, or has not been started. Messages specific to this platform follow. This is a warning and does not prevent the agent from communicating with the console.
Action: Consult Oracle documentation for your platform; then, make sure that the correct SNMP master agent is installed and started.
Cause: The specified service was unable to allocate enough memory to hold all the snmp.ora parameters. This may indicate that the parameters are too big, but more likely it may indicate a system error.
Action: Check system configuration, and if possible, reduce the number of the processes running. If this does not fix the problem, report this problem to Worldwide Customer Support.
Cause: The snmp.ora file could not be opened and read by the specified service. The location of this file varies by platform, but normally it must be in the same directory as other SQL*Net parameter files. If the problem could be traced to a specific parameter, detailed error messages may follow this one.
Action: Consult the documentation for your platform, then create the file in the proper location, and restart the program.
Cause: The snmp.ora file does not contain a configured snmp.visibleservices parameter, or the snmp.ora file is empty.
Action: Edit or create the snmp.ora file and try again.
Cause: The snmp.ora file did not contain the indicated parameter. This parameter was required. Normally this would happen because one of the services mentioned in snmp.visibleservices required one or more detail parameters to be supplied, such as the one indicated.
Action: Edit or create the snmp.ora file and try again.
Cause: The specified service was unable to allocate memory.
Action: Check system configuration and if possible, reduce the number of processes running. If this does not fix the problem, report the problem to Worldwide Customer Support.
Cause: The specified environment variable is not found.
Action: Make this environment variable available to the agent.
These messages do not indicate an error.
Cause: The subagent successfully connected to the master agent.
Cause: The subagent successfully logged off from the master agent. This would normally be a part of the shutdown process.
Cause: The snmp.ora file did not contain the indicated parameter, which was optional. The service instead used its default value for that parameter.
Action: If a value other than the default is desired, edit or create the snmp.ora file and try again.
Cause: The database subagent was unable to connect to the database. The detailed error message follows.
Action: Consult Oracle7 Server Messages for the detailed error message.
Cause: The database subagent was unable to connect to the database, and received the specified error number and text message. The detailed error message follows.
Action: Consult Oracle7 Server Messages for the detailed error message.
Cause: The database subagent was unable to listen on the specified TNS address, possibly because another instance of the database agent has already claimed the address. If more information is available, it will appear under this error.
Action: If another instance of the database agent is already running, either allow it to continue running or bring it down and try again.
Cause: The database subagent was unable to listen on the specified TNS address, possibly because another instance of the database agent has already claimed the address. If more information is available, it will appear under this error.
Action: If another instance of the database agent is already running, either allow it to continue running or bring it down and try again.
Cause: The character set information is not available.
Action: Check if nls_database_parameters table exists.
These messages provide information only, they do not indicate an error.
Cause: The database subagent started successfully.
Cause: The database subagent has received the shutdown command and is processing it.
Cause: The shutdown process has completed. This should be the last message output.
Cause: The subagent successfully logged on to the specified database. This message may also appear if the database goes down and comes back up.
Cause: The subagent successfully logged off from the specified database. This would normally be a part of the shutdown process.
Cause: The specified database became inaccessible, and the subagent then sent an SNMP trap. This may not indicate a problem, since the database may have been shut down deliberately (the subagent is unable to distinguish the cause of the inaccessibility). The destination(s) of the trap are normally set as part of master agent configuration.
Action: If the shutdown was not deliberate, consult Oracle7 Server Messages. If traps are not being received at your management station(s), consult the platform SNMP documentation and ensure that the management station's address is configured properly for the master agent.
Cause: The agent was unable to initialize the file which holds data about users. Following messages may provide more details.
Action: If a solution cannot be found, call Worldwide Customer Support with the circumstances and complete set of messages leading to the error.
Cause: The agent was unable to initialize the file which holds data about event registrations. Following messages may provide more details.
Action: If a solution cannot be found, call Worldwide Customer Support with the circumstances and complete set of messages leading to the error.
Cause: The agent was unable to initialize the file which holds data about jobs. Following messages may provide more details.
Action: If a solution cannot be found, call Worldwide Customer Support with the circumstances and complete set of messages leading to the error.
Cause: The agent was unable to initialize the file which holds data about event occurrences. Following messages may provide more details.
Action: If a solution cannot be found, call Worldwide Customer Support with the circumstances and complete set of messages leading to the error.
Cause: The agent was unable to initialize the file which holds data about job statuses. Following messages may provide more details.
Action: If a solution cannot be found, call Worldwide Customer Support with the circumstances and complete set of messages leading to the error.
Cause: The Remote Procedure Call layer could not be initialized. Following messages may provide more details.
Action: If a solution cannot be found, call Worldwide Customer Support with the circumstances and complete set of messages leading to the error.
Cause: The agent's connection cache could not be initialized. This message usually appears when another agent is running. Only one copy can be running at a time.
Action: If another agent is running, bring it down before running the desired agent.
Cause: The agent's address for internal RPC's could not be initialized. This may be because another copy of the agent is already running.
Action: If another copy of the agent is already running, kill both agents and try again.
Cause: The agent's address for file transfer RPC's could not be initialized. This may be because another copy of the agent is already running.
Action: If another copy of the agent is already running, kill both agents and try again.
Cause: The language ID of the agent could not be initialized.
Action: Make sure the language ID environment variable is correct for the agent.
Cause: The agent was unable to open the specified file.
Action: Make sure that the directory exists, and that the agent has the required permissions to write to it.
Cause: The agent was unable to access the specified directory, or the directory does not exist.
Action: Make sure that the directory exists, and that the agent has the required permissions to write to it.
Cause: The dbsnmp.spawnaddress parameter is required from 7.3.2.1 and later releases. This must be a different address from the dbsnmp.address and is used for file transfer and Oracle Software Manager.
Cause: Add the dbsnmp.spawnaddress parameter to snmp.ora.
Cause: The tcl package index could not be created.
Action: Make sure all the shared libraries in the $ORACLE_HOME/network/agent/library directory are correct.
Cause: The tcl7.5 init.tcl file could not be initialized.
Action: Make sure you have a correct version of init.tcl in $ORACLE_HOME/network/agent/tcl.
Cause: If a key was given at startup, it does not match the key that was last used. If no key was given at startup, then the file was encrypted with a non-default key, and that key must be supplied. There is no way for Oracle to recover the key because it is not hidden anywhere.
Action: If the user cannot remember it, then the files should be saved in case the key is remembered later.
Cause: This message appears on startup if a "password_file=" argument was typed on the command line, but the indicated file was not found, could not be read, or did not contain a line of text. (For security reasons, the name of the password file is not echoed.)
Action: Enter the correct file name and ensure that it has at least one text line of at least 6 characters.
Cause: The user has typed in a key that is too short. See message 00352.
Action: Enter between 6 and 8 characters.
Cause: oemevent was called with too few arguments.
Action: oemevent should be invoked as follows:
oemevent eventname object severity message [result...]
where:
eventname is a legal Oracle Enterprise Manager event name;
object is the name of the service or resource to which the event applies;
severity is one of the following-----alert, warning, or clear;
message is the text of the error message to be conveyed to the Oracle Enterprise Manager console;
result is zero or more strings to be returned as the results of the event.
Cause: The first argument passed to oemevent is not a valid Oracle Enterprise Manager event name.
Action: Invoke oemevent with a legal Oracle Enterprise Manager event name.
Cause: The third argument passed to oemevent is not a valid Oracle Enterprise Manager event severity level (either alert, warning, or clear).
Action: Invoke oemevent with a legal Oracle Enterprise Manager severity level.
Cause: oemevent was unable to establish a connection with the agent Comm process.
Action: Make sure that the agent Comm process is running, that it is accepting connections, and that the agent address in the snmp.ora file is correct.
Cause: oemevent was unable to send the ReportEvent RPC to the agent Comm process.
Action: Make sure that the agent is up. Try running oemevent again.
These messages can be sent back to the console when users run jobs or register events.
Cause: A predefined event or job was invoked with fewer arguments than required, or with the wrong types of arguments.
Action: Check the documentation and try again. If the problem continues, ensure that the installed versions of the agent and the console match.
These messages appear only in the agent log file and do not necessarily indicate an error.
Cause: The agent has registered the specified event for the user of the service; the internal ID number of the event, user and service is shown in the message.
Cause: The Registration was rejected because it was identical to an existing registration.
Cause: The agent is about to cancel an event registration.
Cause: The agent delivered a report of an event occurring, which was registered by the specified user.
Cause: The schedule of the specified job number has expired.
Cause: The specified job number is being executed by the agent.
Cause: The specified job is being cancelled at the request of the console.
Cause: The specified fixup job is being run, since its event occurred.
Cause: A dbsnmp_stop command was received from lsnrctl.
Cause: The Worker process has detected no response from the Comm process for the timeout period, and has restarted it. This may or may indicate an error. If it happens repeatedly, it may indicate communication problems with the console.
Action: Inspect trace file for the Comm process, if tracing is on. If not, and this appears repeatedly, stop the agent, turn on tracing, and restart it.
Cause: A request to schedule the specified job was received from the console and the job was scheduled; the internal ID number is shown in the message.
Cause: The specified job number was cancelled by the console.
Cause: The status of a completed job was delivered to the console.
Cause: The user was registered with the specified parameters. The internal ID of the user is also shown in the message.
Cause: The specified job number has been run and reported success.
Cause: The specified job ID failed with the error code given. Complete output is returned to the console.
Cause: The specified file was fetched from the specified address.
These error messages can appear on the console; they may or may not indicate a software problem. In certain cases, user actions can clear the problem.
Cause: The specified event could not be registered because the .tcl file that implements it does not exist on the agent.
Action: Check the installation of the agent, and if necessary reinstall the correct version.
Cause: On an event registration, a database or service name was specified which the agent does not monitor.
Action: Check configuration files on the console, and the snmp.ora file on the agent.
Cause: For an event, a user was specified who has not been registered with the agent. Possibly the user registration file has been inadvertently deleted.
Action: Logging off from the console and logging back in may fix the problem.
Cause: For an event registration, the language string which was registered for the user was invalid. The language comes from the NLS_LANG environment variable on the console machine.
Action: Check the setting of the NLS_LANG environment variable. If necessary, correct it, log off from the console, and log back on.
Cause: The Tcl script for the specified event failed to evaluate. The specific error found by Tcl is returned to the console. It may be that incorrect arguments were provided to the event, or the catsnmp.sql script that allows the agent permission to execute the predefined events has not been run.
Action: Check the results returned to the console. Correct the Tcl script if necessary.
Cause: The specified job could not be registered because the .tcl file that implements it does not exist on the agent.
Action: Check the installation of the agent, and if necessary install the correct version.
Cause: The specified segment could not be found in the database.
Action: Make sure the SQL statement is correct, especially the job or event parameters.
Cause: The specified parameter could not be found in the V$SYSSTAT table.
Action: Make sure the SQL statement is correct, especially the job or event parameters.
Cause: The specified user-defined program could not be executed on the agent.
Action: Make sure the user defined program exists and that the agent can execute it.
Cause: Make sure the user-defined program exists and that the agent can execute it.
Action: Make sure that the agent can invoke either svrmgr1 or sqldba.
Cause: The date format is not in mm/dd/yy format.
Action: Correct the date format.
Cause: The database is in NOARCHIVELOG mode.
Action: Alter the database archive log mode to on.
Cause: The sqlplus executable does not exist.
Action: Make sure either svrmgrl or sqldba can be invoked by the agent.
Action: Report to Worldwide Customer Support.
Cause: On an event registration, the agent was unable to create the Tcl interpreter to process the event.
Action: Report to Worldwide Customer Support.
Cause: Call to a SQL statement failed.
Cause: An offline backup is in progress.
Cause: Call to a SQL statement failed.
Cause: Call to a SQL statement failed.
Cause: Offline backup about to take place.
Cause: Call to a SQL statement failed.
Cause: Database is running and needs to be shutdown.
Cause: Database is not running and needs to be started.
