Oracle Enterprise Manager Messages Manual Release 1.5.0 A57693-01 |
|
Cause: File is not saved.
Action: None.
Cause: File is not saved.
Action: None.
Cause: File is not saved.
Action: None.
Cause: Third-party user tried to supply a name for an interactive job.
Action: None.
Cause: Third-party user tried to supply a schedule for an interactive job.
Action: None.
Cause: The file has incorrect syntax. Only certain parameters are allowed.
Action: Recreate the script using the Backup wizard.
Cause: Cannot create a unique filename.
Action: Do not open file.
Cause: There is nothing to execute.
Action: Specify a filename or text.
Cause: There is nothing to execute.
Action: Specify message text in field.
Cause: Task Validate State.
Action: None.
Cause: Task Validate State.
Action: None.
Cause: Task Validate State.
Action: None.
Cause: Task Invalidate State.
Action: Reload task.
Cause: Task Validate State.
Action: None.
THE FOLLOWING 2 MESSAGES ARE SEEN BY THE USER AS A SINGLE MESSAGE.
Cause: A limit exists for length of job parameters VARCHAR2[1024].
Action: You need to reduce the number of tasks and associated parameters for this job before scheduling the job.
Cause: A limit exists for length of job parameters VARCHAR2[1024]. You have exceeded the 1024 byte buffer limit.
Action: You need to reduce the number of tasks in this job before you schedule this job.
Cause: Script was modified.
Action: Save script in to the file.
THE FOLLOWING 2 MESSAGES ARE SEEN BY THE USER AS A SINGLE MESSAGE
Cause: A limit exists for number of input files in Agent code (5).
Action: Before you schedule the job, you must reduce the number of tasks and associated input files.
Cause: A limit exists for the number of input files in Agent code (5).
Action: Before you schedule the job, you must reduce the number of tasks.
Cause: Tried to modify, suspend or release a job while it is still in processing mode.
Action: Try to do the same job operation after the job status is changed from processing to others.
Cause: Nothing was changed.
Action: Do not modify Job.
Cause: Interactive Jobs ID is not 0.
Action: Interactive jobs are not available with this release of Enterprise Manager.
Cause: Job Name is Empty.
Action: From the General tab of the Create Job window, fill in the Name blank.
Cause: The Destinations parameter is a SAFEARRAY. It does not have 2 columns of BSTR.
Action: This could be a repository error. A possible workaround would be to remove the node and rediscover it.
Cause: Job name already exists.
Action: You can either wait for the existing job (in the Active Jobs page) to complete or give this job a different name.
Cause: The selected destinations field has not be populated or the available destinations field is empty due to comfiguration problems
Action: To correct the error perform the following steps:
lsnrctl dbsnmp_stat
If the agent is not running, enter the following command:
lsnrctl dbsnmp_start
mydb.world=(ORACLE_DATABASE,host1,listener_host1.world) listener_host1.world=(ORACLE_LISTENER,host1) agent_host1.world=(ORACLE_AGENT,host1)
agent_host1.world= (DESCRIPTION = (ADDRESS = (PROTOCOL=TCP) (HOST=host1) (PORT=1748) ) )
Cause: List of selected tasks is empty.
Action: From the Tasks tab of the Create Job window, select a task. Then, fill in parameters for the task on the Parameters tab.
Cause: Failed to Open SQL file.
Action: An operating system error may have occurred.
Cause: Cannot create a unique filename for Startup DB script.
Action: An operating system error may have occurred.
Cause: Failed to write Startup DB script file.
Action: A write error has occurred in the SYSMAN directory. Make sure the directory is not full or write-protected.
Cause: Failed to read TCL script file.
Action: An operating system error may have occurred.
Cause: Cannot create a unique filename for Master TCL Script.
Action: An operating system error may have occurred.
Cause: Failed to Open Master TCL Script.
Action: An operating system error may have occurred.
Cause: Failed to Write Master TCL Script.
Action: An operating system error may have occurred.
THE FOLLOWING 3 MESSAGES ARE SEEN BY THE USER AS A SINGLE MESSAGE
Cause: Just Warning.
Action: Do or do not change job type.
Cause: Just Warning
Action: Do or do not change job type
Cause: Just Warning
Action: Do or do not change job type.
Cause: Failed to Open file.
Action: Exit.
Cause: Failed to Read file.
Action: Exit.
Cause: Failed to write file.
Action: Exit.
Cause: Cannot find the predefined task file.
Action: Install the predefined task file from the staging area.
Cause: System fails to return current time.
Action: Restart the machine.
Cause: Failed to retrieve a list of job destinations.
Action: Retry the same operation later. The message could indicate lost repository connection.
Cause: User ordered a remove job on a job instance which is already pending deletion.
Action: Check the remote agent or ping agent from Daemon manager if desired. The message could indicate a lost connection to the agent.
Cause: Remove job operation failed on the remote agent.
Action: Retry the remove job operation. The error should disappear after the message. No action required.
Cause: Tried to submit a job with an invalid task.
Action: Do not submit the job.
Cause: Tried to save a job with an invalid task.
Action: Query if the user really wishes to save the job.
Cause: Job Name is duplicate.
Action: Do not save a duplicate job.
Cause: The job contains a task with a CLSID that was not registered on this machine
Action: Either delete the saved job or open the job on a machine with the task registered.
Cause: Job Name is invalid.
Action: Do not save or submit a job with an invalid job name.
Cause: A day of the week was not specified.
Action: Enter a day of the week on the Schedule tab of the Create Job window.
Cause: A day of the month was not specified.
Action: Enter a valid day of the month on the Schedule tab of the Create Job window.
Cause: The end time is before the start time.
Action: Enter a valid end time on the Schedule tab of the Create Job window.
Cause: The interval is not valid.
Action: Enter a valid time interval on the Schedule tab of the Create Job window.
Cause: Bad execution mode.
Action: Enter a valid execution mode on the Schedule tab of the Create Job window.
Cause: The frequency clause is invalid.
Action: Enter a valid frequency clause on the Schedule tab of the Create Job window.
Cause: Bad start date.
Action: Enter a valid start date on the Schedule tab of the Create Job window.
Cause: Next execution time past.
Action: Enter a valid start/end date on the Schedule tab of the Create Job window.
Cause: Unknown schedule error.
Action: Do not save or submit a job with an invalid schedule.
Cause: The schedule was invalid.
Action: Enter a valid start/end date on the Schedule tab of the Create Job window.
Cause: A day of the week was not specified.
Action: Enter a valid day of the week on the Schedule tab of the Create Job window.
Cause: A day of the week was not specified.
Action: Enter a day of the week on the Schedule tab of the Create Job window.