0 Replies Latest reply on Nov 18, 2013 9:25 PM by BillW

    Errors in emoms.log file




      I have been poking around a bit trying to better understand some problems and how the OEM works. In the Middleware/gc_inst/em/EMGC_OMS1/sysman/log/emoms.log file I see numerous occurrences of the following error -


      2013-11-18 07:09:56,740 [Thread-136302] WARN  em.dataguard clearMetrics.1545 - StandbyTargetService:clearMetrics(): SQLException: java.sql.SQLException: ORA-20615: -20615Received severity when target is in blackout (target_guid = AF3D78FD11633D484E44A12D074DC59B) (policy_guid=3E6F70DB22758B7B9756EF342180E7BB) (key_value= ERES_HUGE) (violation_level =CLEAR) (collection_ts= 2013-11-18 07:09:56)

      ORA-06512: at "SYSMAN.EM_VIOLATION_CHECKS", line 212

      ORA-06512: at "SYSMAN.EM_VIOLATION_CHECKS", line 316

      ORA-04088: error during execution of trigger 'SYSMAN.EM_VIOLATION_CHECKS'

      ORA-06512: at "SYSMAN.EMD_SCHEMA", line 177

      ORA-06512: at "SYSMAN.EMD_SCHEMA", line 126

      ORA-06512: at line 1


      Searching for target using the target_guid I find that this target is a logical standby database which is under blackout.


      Question, are these errors in the emoms.log file to be expected when a logical standby is under blackout (or under other circumstances) or is there a problem with the SYSMAN.EM_VIOLATION_CHECKS procedure? I find other references to errors in the SYSMAN.EM_VIOLATION_CHECKS procedure but nothing which specifically fits my situation.



      Bill Wagman