{"id":1954,"date":"2018-09-18T21:12:44","date_gmt":"2018-09-18T19:12:44","guid":{"rendered":"http:\/\/clemente.pamplona.name\/dba\/?p=1954"},"modified":"2018-09-19T11:15:25","modified_gmt":"2018-09-19T09:15:25","slug":"comprobando-del-oem-13-alertas-data-failure-detected","status":"publish","type":"post","link":"http:\/\/clemente.pamplona.name\/dba\/comprobando-del-oem-13-alertas-data-failure-detected\/","title":{"rendered":"Comprobando  del OEM 13:  alertas    Data Failure Detected"},"content":{"rendered":"<p>Hoy vamos a ver otra entrada sobre las comprobaciones del OEM .<\/p>\n<p>Una de los incidentes que hay que limpiar a mano en el enterprise manager es el de la comprobacion de la integridad dela base de datos.<br \/>\nEl check de la metrica <i>Data Failure Detected<\/i> se basa en las comprobaciones de los Health monitor de Oracle.<\/p>\n<h1> Como saber a que problema se refiere<\/h1>\n<p>Mediante la libreria <b> DBMS_HM<\/b> podemos acceder a los checks llevados a cabo por Oracle.<br \/>\nSi ejecutamos la consulta<\/p>\n<pre>\r\nSET LONG 100000;\r\nSET LONGCHUNKSIZE 1000\r\nSET PAGESIZE 1000\r\nSET LINESIZE 512\r\ncolumn name format a20;\r\ncolumn STATUS format a10;\r\ncolumn START_TIME format a20;\r\ncolumn END_TIME format a20;\r\ncolumn name format a20;\r\ncolumn STATUS format a10;\r\ncolumn START_TIME format a30;\r\ncolumn END_TIME format a30;\r\ncolumn CHECK_NAME format a40;\r\n\r\n select run_id,name,check_name,start_time,end_time,status \r\n   from v$hm_run order by START_TIME asc;\r\n<\/pre>\n<p>Obtendremos el listado de los checks ejecutados <\/p>\n<pre>\r\n    RUN_ID NAME                 CHECK_NAME                   START_TIME\r\n---------- ---------------- -------------------- ------------------------------\r\n   1 HM_RUN_1       DB Structure Integrity Check   25-JUL-18 05.18.01.337628 PM\r\n  21 HM_RUN_21      DB Structure Integrity Check   25-JUL-18 05.19.35.157614 PM\r\n  41 HM_RUN_41      DB Structure Integrity Check   25-JUL-18 05.20.51.496617 PM\r\n  61 HM_RUN_61      DB Structure Integrity Check   25-JUL-18 05.52.24.630598 PM\r\n9621 HM_RUN_9621    DB Structure Integrity Check   15-SEP-18 05.51.52.339032 PM\r\n9641 HM_RUN_9641    DB Structure Integrity Check   15-SEP-18 05.53.25.135027 PM\r\n 6 rows selected.\r\n<\/pre>\n<p>En el caso del ejemplo, preguntaremos por la ultima ejecucion, que es la <b>HM_RUN_9641<\/b><\/p>\n<pre>\r\nDBMS_HM.GET_RUN_REPORT('HM_RUN_9641')\r\n-----------------------------------------------------------------------------------------\r\nBasic Run Information\r\n Run Name                     : HM_RUN_9641\r\n Run Id                       : 9641\r\n Check Name                   : DB Structure Integrity Check\r\n Mode                         : REACTIVE\r\n Status                       : COMPLETED\r\n Start Time                   : 2018-09-15 17:53:25.135027 +02:00\r\n End Time                     : 2018-09-15 17:53:28.473273 +02:00\r\n Error Encountered            : 0\r\n Source Incident Id           : 0\r\n Number of Incidents Created  : 0\r\n\r\nInput Paramters for the Run\r\nRun Findings And Recommendations\r\n Finding\r\n Finding Name  : Inaccessible CF\r\n Finding ID    : 9642\r\n Type          : FAILURE\r\n Status        : CLOSED\r\n Priority      : CRITICAL\r\n Message       : Control file\r\n               +DATA\/test\/controlfile\/current.599.982430265\r\n               cannot be accessed because of an ASM Failure\r\n Message       : Database cannot be mounted\r\n<\/pre>\n<p>Aqui podemos ver como el error es referente a un controlfile inaccesbile , lo que parece ser un error antiguo.<\/p>\n<h1> \u00bfComo asegurarnos de que todo esta correcto?<\/h1>\n<p>La respuesta mas obia es, lanzar nosotros mismos este check de manera manual para ver el resultado.<br \/>\nPara ello usaremos el procedure <b>DBMS_HM.RUN_CHECK<\/b><\/p>\n<pre>\r\nSQL> SELECT DBMS_HM.GET_RUN_REPORT('Clear_OEM') FROM DUAL;\r\n\r\nDBMS_HM.GET_RUN_REPORT('CLEAR_OEM')\r\n-----------------------------------------------------------------------------------\r\nBasic Run Information\r\n Run Name                     : Clear_OEM\r\n Run Id                       : 10581\r\n Check Name                   : DB Structure Integrity Check\r\n Mode                         : MANUAL\r\n Status                       : COMPLETED\r\n Start Time                   : 2018-09-18 20:58:12.283769 +02:00\r\n End Time                     : 2018-09-18 20:58:12.476010 +02:00\r\n Error Encountered            : 0\r\n Source Incident Id           : 0\r\n Number of Incidents Created  : 0\r\n\r\nInput Paramters for the Run\r\nRun Findings And Recommendations\r\n<\/pre>\n<p>Donde podemos ver como ya no tenemos errores <\/p>\n<p>Como siempre, mas informacion en:<\/p>\n<ul>\n<li> metalink en la entrada <i>\tChecker Run Found xx New Persistent Data Failures. (Doc ID 1391202.1)<i>\n<li> Manual de Oracle <a href=\"https:\/\/docs.oracle.com\/cd\/B28359_01\/server.111\/b28310\/diag007.htm#ADMIN11273\"> Running Health Checks Manually<\/a><br \/>\n","protected":false},"excerpt":{"rendered":"<p>Hoy vamos a ver otra entrada sobre las comprobaciones del OEM . Una de los incidentes que hay que limpiar a mano en el enterprise manager es el de la comprobacion de la integridad dela base de datos. El check &hellip; <a href=\"http:\/\/clemente.pamplona.name\/dba\/comprobando-del-oem-13-alertas-data-failure-detected\/\">Sigue leyendo <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[935,929,931,933],"class_list":["post-1954","post","type-post","status-publish","format-standard","hentry","category-em","tag-db-structure-integrity-check","tag-data-failure-detected","tag-dbms_hm","tag-dbms_hm-get_run_report"],"_links":{"self":[{"href":"http:\/\/clemente.pamplona.name\/dba\/wp-json\/wp\/v2\/posts\/1954","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/clemente.pamplona.name\/dba\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/clemente.pamplona.name\/dba\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/clemente.pamplona.name\/dba\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/clemente.pamplona.name\/dba\/wp-json\/wp\/v2\/comments?post=1954"}],"version-history":[{"count":8,"href":"http:\/\/clemente.pamplona.name\/dba\/wp-json\/wp\/v2\/posts\/1954\/revisions"}],"predecessor-version":[{"id":1962,"href":"http:\/\/clemente.pamplona.name\/dba\/wp-json\/wp\/v2\/posts\/1954\/revisions\/1962"}],"wp:attachment":[{"href":"http:\/\/clemente.pamplona.name\/dba\/wp-json\/wp\/v2\/media?parent=1954"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/clemente.pamplona.name\/dba\/wp-json\/wp\/v2\/categories?post=1954"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/clemente.pamplona.name\/dba\/wp-json\/wp\/v2\/tags?post=1954"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}