Oracle Enterprise Manager Messages Manual Release 1.5.0 A57693-01 |
|
Cause: The specified parameter file could not be found.
Action: Provide a valid pathname for the parameter file.
Cause: The database startup failed because of an unknown exception.
Action: This error occurs rarely. If the error occurs, please shut down the application and restart. Reboot your system, if necessary.
Cause: The database shutdown failed because of an unknown exception.
Action: This error occurs rarely. If the error occurs, please shut down the application and restart. Reboot your system, if necessary.
Cause: The database mount failed because of an unknown exception.
Action: This error occurs rarely. If the error occurs, please shut down the application and restart. Reboot your system, if necessary.
Cause: The database open failed because of an unknown exception.
Action: This error occurs rarely. If the error occurs, please shut down the application and restart. Reboot your system, if necessary.
Cause: The database startup failed because of an unknown exception.
Action: This error occurs rarely. If the error occurs, please shut down the application and restart. Reboot your system, if necessary.
Cause: The database startup failed because an invalid configuration was chosen.
Action: Choose a valid configuration for startup.
Cause: Initialization parameters could not be obtained from the database because of an unknown exception.
Action: This error occurs rarely. If the error occurs, please shut down the application and restart. Reboot your system, if necessary.
Cause: Saving the parameter to a file was unsuccessful.
Action: Make sure you specified a valid filename.
Cause: User is not allowed to edit this initialization parameter.
Action: This parameter cannot be edited.
Cause: Failed to open the Initialization parameter file for reading parameters.
Action: Make sure that you have specified a valid filename.
Cause: Failed to locate list or derived parameter entries in the repository for this version of the database.
Action: Make sure the repository creation table has been run correctly.
Cause: You are not connected to the repository.
Action: Make sure that you have a connection to the repository.
Cause: Failed to obtain Init Params because of an Unknown Exception.
Action: This error occurs rarely. If the error occurs, please shut down the application and restart. Reboot your system, if necessary.
Cause: Failed to get the IUnknown pointer for the server document. An OLE error occurred.
Action: Since Oracle Enterprise Manager relies on OLE, Oracle Enterprise Manager cannot run in this case. The user should quit all Oracle Enterprise Manager applications (possibly checking task viewer for VOD or others). The PC may require a reboot to reset the OLE information.
Cause: The CLSIDFromProgID() call failed.
Action: Contact Oracle Worldwide Customer Support.
Cause: The RegisterActiveObject(), or IRunningObjectTable::Register() call failed for the job-notif object
Action: Since Oracle Enterprise Manager relies on OLE, Oracle Enterprise Manager cannot run in this case. The user should quit all Oracle Enterprise Manager applications (possibly checking task viewer for VOD or others). The PC may require a reboot to reset the OLE information.
Cause: The RevokeActiveObject(), or IRunningObjectTable::Revoke() call failed for the job-notif object
Action: Since Oracle Enterprise Manager relies on OLE, Oracle Enterprise Manager cannot run in this case. The user should quit all Oracle Enterprise Manager applications (possibly checking task viewer for VOD or others). The PC may require a reboot to reset the OLE information.
Cause: The GetActiveObject() call failed. An OLE error occurred.
Action: Since Oracle Enterprise Manager relies on OLE, Oracle Enterprise Manager cannot run in this case. The user should quit all Oracle Enterprise Manager applications (possibly checking task viewer for VOD or others). The PC may require a reboot to reset the OLE information.
Cause: A QueryInterface() call to obtain an IDispatch* failed.
Action: Contact Oracle Worldwide Customer Support.
Cause: To generate error msg for any ole-automation call failure append <error id>\n<error description> ("%0ld\n%s")
Action: Since Oracle Enterprise Manager relies on OLE, Oracle Enterprise Manager cannot run in this case. The user should quit all Oracle Enterprise Manager applications (possibly checking task viewer for VOD or others). The PC may require a reboot to reset the OLE information.
Cause: Failed to obtain the preferred credentials (GetPreferredCredentials()).
Action: Contact Oracle Worldwide Customer Support.
Cause: Failed to obtain the logon information (GetRepLogonInfo()).
Action: Contact Oracle Worldwide Customer Support.
Cause: Failure in initializing a job object. (Initialize()).
Action: Contact Oracle Worldwide Customer Support.
Cause: Failed to create a temporary file for the tcl-script.
Action: Contact Oracle Worldwide Customer Support.
Cause: Failed to write to the tcl-script file.
Action: Contact Oracle Worldwide Customer Support.
Cause: Failed to delete the temporary tcl-script file.
Action: Contact Oracle Worldwide Customer Support.
Cause: Failed to set the script to the job object (SetScript()).
Action: Contact Oracle Worldwide Customer Support.
Cause: Failed to set a name to the job object (SetJobName()).
Action: Contact Oracle Worldwide Customer Support.
Cause: Failed to set destinations to the job object (SetDestinations()).
Action: Contact Oracle Worldwide Customer Support.
Cause: Failed to set schedule to the job object (SetSchedule()).
Action: Contact Oracle Worldwide Customer Support.
Cause: Failed to set the credentials to the job object (SetCredentials())
Action: Contact Oracle Worldwide Customer Support.
Cause: Failed to set a notification object to the job (SetNotificationObjectProgID())
Action: Since Oracle Enterprise Manager relies on OLE, Oracle Enterprise Manager cannot run in this case. The user should quit all Oracle Enterprise Manager applications (possibly checking task viewer for VOD or others). The PC may require a reboot to reset the OLE information.
Cause: Failed to commit the job object (Commit()).
Action: Contact Oracle Worldwide Customer Support.
Cause: Failed to extract notification information for a job (JobNotificationVriantToParameters())
Action: Contact Oracle Worldwide Customer Support.
Cause: Failed to flush the job notifications queue (FlushNotificationQueue())
Action: Contact Oracle Worldwide Customer Support.
Cause: The process of starting the parallel server failed.
Action: Contact Oracle Worldwide Customer Support.
Cause: The process of shuting down the parallel server failed.
Action: Contact Oracle Worldwide Customer Support.
Cause: Generic message to cover errors related to parallel server startup
Action: Contact Oracle Worldwide Customer Support.
Cause: Generic message to cover errors related to parallel server shutdown
Action: Contact Oracle Worldwide Customer Support.
Cause: Generic error text (and dlg-caption) when operation type (start/shut) is not known
Action: Contact Oracle Worldwide Customer Support.
Cause: Failed to get the prefered credentials (GetPreferredCredentials())
Action: Contact Oracle Worldwide Customer Support.
Cause: Failed to get the node name for service (GetServiceNode ())
Action: Contact Oracle Worldwide Customer Support.
Cause: Failed to find the startup .tcl file
Action: Contact Oracle Worldwide Customer Support.
Cause: Failed to find the shutdown .tcl file
Action: Contact Oracle Worldwide Customer Support.
Cause: A CreateDispatch() ole call failed
Action: Since Oracle Enterprise Manager relies on OLE, Oracle Enterprise Manager cannot run in this case. The user should quit all Oracle Enterprise Manager applications (possibly checking task viewer for VOD or others). The PC may require a reboot to reset the OLE information.
Cause: Displayed when attempting to select one too many ops-instance in the startup/shutdown ops dlgs
Action: Contact Oracle Worldwide Customer Support.
Cause: Displayed if too many ops instances selected in the startup/shutdown ops dlgs
Action: Contact Oracle Worldwide Customer Support.
Cause: Failed to extract the information from the variant returned by discovery cache's GetObjectList()
Action: Contact Oracle Worldwide Customer Support.
Cause: Failed to get the ops-instances from the discovery-cache for the parallel server
Action: Contact Oracle Worldwide Customer Support.
Cause: Operation attempted requires at least one ops-instance to be selected, and currently none has been selected
Action: Contact Oracle Worldwide Customer Support.
Cause: Failed to open the file
Action: Contact Oracle Worldwide Customer Support.
Cause: Failed to write to the file
Action: Contact Oracle Worldwide Customer Support.
Cause: The parallel server startup operation failed (dlg caption)
Action: Contact Oracle Worldwide Customer Support.
Cause: The parallel server shutdown operation failed (dlg caption)
Action: Contact Oracle Worldwide Customer Support.
Cause: The parallel server was successfully started (detailed msg)
Action: Contact Oracle Worldwide Customer Support.
Cause: The parallel server was successfully shut down (detailed msg)
Action: Contact Oracle Worldwide Customer Support.
Cause: The CreateItemMoniker() call failed for the job notif object.
Action: Contact Oracle Worldwide Customer Support.
Cause: You did not specify a filename for saving the Initialization Parameter file.
Action: Please specify a valid filename for the Parameter file.
Cause: You specified the name of an existing file.
Action: You must decide whether or not to overwrite the file.
Cause: Unable to locate the console in order to obtain repository details.
Action: You must supply the repository credentials.