eG Help

The Oracle Recovery Manager (RMAN) provides a comprehensive foundation for efficiently backing up and recovering the Oracle database. It is designed to work intimately with the server, providing block-level corruption detection during backup and restore. It provides a common interface, via command line and Enterprise Manager, for backup tasks across different host operating systems and offers features not available through user-managed methods, such as parallelization of backup/restore data streams, backup files retention policy, and detailed history of all backups. Since errors in backup/recovery jobs can result in loss of critical data, it is essential to keep a close watch on the activities of the RMAN. Using the OraRmanJobTest, you can monitor the status of backup/recovery jobs executed by the RMAN so that, you can be forewarned of issues in these critical processes.

Measurement	Description	Measurement Unit	Interpretation
Completed_jobs	The number of jobs completed during the last measurement period	Number	Use the detailed diagnosis of this measure to view the details of the completed jobs.
Failed_jobs	The count of failed jobs in the last measurement period	Number	Ideally, the value of this measure should be 0. If a non-zero value is reported, use the detailed diagnosis of this measure to determine which jobs failed at what time.
Running_jobs	The number of jobs that were running during the last measurement period	Number	Use the detailed diagnosis of this measure to view the details of the jobs that were running.
Running_with_error_jobs	The number of jobs that were running during the last measurement period, but with errors	Number	Ideally, this value should be low. If the value is high, you may want to check the detailed diagnosis of this measure to know which jobs are running with errors.
Running_with_warning_job	The number of jobs that were running during the last measurement period, but with warnings	Number	Ideally, this value should be low. If the value is high, you may want to check the detailed diagnosis of this measure to know which jobs are running with warnings.
Completed_with_error_job	The number of jobs that were completed during the last measurement period, but with warnings	Number	Ideally, this value should be low. If the value is high, you may want to check the detailed diagnosis of this measure to know which completed jobs have errors.
Completed_withwarningjob	The number of jobs that were completed during the last measurement period, but with errors	Number	Ideally, this value should be low. If the value is high, you may want to check the detailed diagnosis of this measure to know which completed jobs are with warnings.
Exceeded_time_limit_jobs	The number of jobs that are taking an abnormal amount of time to complete	Number	If this measure reports a non-zero value, then, it indicates that one/more jobs are taking too long to complete. Since such jobs could drain the server of resources, it is imperative that you determine why the jobs are taking so much time to execute, and fix the problem. A possible reason could be that these jobs are waiting for objects that have been locked by other sessions; if these sessions are less-critical, you may want to terminate them in order to enable the jobs to use the locked resources and resume execution. To know the jobs that are taking too long a time, use the detailed diagnosis of this measure.