Oracle Enterprise Manager Messages Manual Release 9.2.0 Part Number A96671-01 |
|
Cause: The operation completed with a success status.
Action: No action.
Cause: There was a syntax error in the command line.
Action: Correct the command line error.
Cause: The repository specified cannot be connected to.
Action: Check to make sure that the repository exists and that the Oracle Management Server is running.
Cause: Was not able to log into the Oracle Management Server.
Action: Check that the Oracle Management Server is running, the repository name is correct, and the username/password is correct.
Cause: A general processing error occurred.
Action: Contact Oracle Support Services.
Cause: A capture command was given with a baseline name that does not exist in the repository.
Action: Specify an existing baseline.
Cause: A compare command was given with a comparison name that does not exist in the repository.
Action: Specify an existing comparison.
Cause: A change plan command (generate or execute) was given with a plan name that does not exist in the repository.
Action: Specify an existing plan.
Cause: A script is already being executed for this plan version.
Action: Review the execution history log in the Oracle Change Manager graphical user interface.
Cause: Script execution failed.
Action: Review the execution log and execution history in the Oracle Change Manager graphical user interface.
Cause: The script generation completed with some warnings.
Action: Check the impact report in the Oracle Change Manager graphical user interface.
Cause: The script generation completed with some errors.
Action: Check the impact report in the Oracle Change Manager graphical user interace and correct the problems identified.
Cause: The script generation failed to complete.
Action: Contact Oracle Support Services.
Cause: A problem was encountered involving the specified database.
Action: Check the reason for the error and correct the problem.
Cause: Preferred credentials were not found for the database specified.
Action: Using the console, check to see if the specified database is discovered and has credentials defined.
Cause: Was not able to log into the Oracle Management Server.
Action: Check that the Oracle Management Server is running, the repository name is correct, and the username/password is correct.
Cause: An error occurred during script execution.
Action: Review the execution history log in the Oracle Change Manager graphical user interface.
Cause: An error occurred while executing the cleanup script.
Action: Review the execution history log in the Oracle Change Manager graphical user interface.
Cause: An error occurred while executing the undo script.
Action: Review the execution history log in the Oracle Change Manager graphical user interface.
Cause: Execution of the cleanup script was successful.
Action: No action required.
Cause: Execution of the undo script was successful.
Action: No action required.
Cause: Execution of the script was successful.
Action: No action required.
Cause: Executing the cleanup script as a result of a successful script execution.
Action: No action required.
Cause: Executing the undo script as a result of an error in script execution.
Action: No action required.
Cause: Exception thrown, internal error.
Action: Contact Oracle Support Services.
Cause: Error status report.
Action: No action required.
Cause: Reports execution process exit status.
Action: No action required.
Cause: Script execution succeeded.
Action: No action required.
Cause: The script generation completed with no errors.
Action: No action required.
Cause: Successful completion of operation.
Action: None.
Cause: This command requires that you use the -id argument to specify a valid identity.
Action: Make sure that you typed your identity string correctly. See the command line interface appendix in the Getting Started with Oracle Change Management Pack manual if you need more information about specifying a valid identity using the -id argument.
|
Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|