Checker Run

I’ve noticed after I refresh some of my development databases from production, I am getting a “Checker Run” alert for the newly refreshed database. There is not much information out there, so I figured I would write up how to determine what exactly the cause is.

In Grid Control, I see alerts similar to the following:

So what are these “persistent data failures”? Unfortunately, the alert does not give any further details. It is up to you to figure it out.

Oracle’s new Health Monitor performs a database check and has determined that there are failures. It is HM that is finding these failures and reporting them to Grid Control. You can see the HM runs by querying V$HM_RUN. In my case, I need to know the ID of the run that gave this error.

I know the run ID is 45881. I can now use the supplied DBMS_HM package to get a report on this run which gives me more details. The “run name” is of the form “HM_RUN_xxxxx” where “xxxxx” is the Run ID we determined above.

SQL> SET LONG 999999999
SQL> SELECT dbms_hm.get_run_report('HM_RUN_45881') FROM dual;

DBMS_HM.GET_RUN_REPORT('HM_RUN_45881')
--------------------------------------------------------------------------------
Basic Run Information
Run Name                     : HM_RUN_45881
Run Id                       : 45881
Check Name                   : DB Structure Integrity Check
Mode                         : REACTIVE
Status                       : COMPLETED
Start Time                   : 2011-08-08 12:51:42.822626 -05:00
End Time                     : 2011-08-08 12:52:25.169770 -05:00
Error Encountered            : 0
Source Incident Id           : 0
Number of Incidents Created  : 0

DBMS_HM.GET_RUN_REPORT('HM_RUN_45881')
--------------------------------------------------------------------------------

Low sex drive or lack cute-n-tiny.com prescription free levitra of sexual desire (decreased libido) and problems with ejaculation and orgasm (ejaculatory dysfunction). This Sildenafil citrate is marketed by the US based company Pfizer. discount viagra uk Reason behind http://cute-n-tiny.com/tag/slow-loris/ viagra ordination male erectile dysfunctionMED is caused because the flow of blood to the penis has been restricted. Although this are mild and manageable but there are rare cases where an erection may last too long, but more often than not, dysfunction is focused on tadalafil online india , viagra, but there are still a large number of potent and pure natural herbs such as Kavach Beej, Mulethi, Shatavari, Kudachchal, Haritaki, Chitrak, Soanth, Ashwagandha, Sudh Shilajit, Jeera, Arjun, Bhringaraj,Chitrak, Jaiphal, Amla, Mackoy, Swarnapatra, Jhau, Kesar, Kasturidana, Shankhpuspi,. Input Paramters for the Run
Run Findings And Recommendations
Finding
Finding Name  : Control File needs recovery
Finding ID    : 45882
Type          : FAILURE
Status        : CLOSED
Priority      : CRITICAL
Message       : Control file needs media recovery
Message       : Database cannot be opened

DBMS_HM.GET_RUN_REPORT('HM_RUN_45881')
--------------------------------------------------------------------------------
Finding
Finding Name  : System datafile is old
Finding ID    : 45885
Type          : FAILURE
Status        : CLOSED
Priority      : CRITICAL
Message       : System datafile 1:
'/u01/app/oracle/oradata/fgodba/data02/system01.dbf' needs
media recovery
Message       : Database cannot be opened
Finding

There were many more lines all indicating that the file needs media recovery, one message for each datafile in the database.

The answer is now clear. I refreshed this database from a hot backup of my production database. The checker ran before I had completed recovery and opened the database. I now have a definitive idea of what problem the checker found.

The alert will not clear itself so you will have to go back and manually clear the alert in Grid Control.