5 Replies Latest reply: Sep 27, 2012 8:03 AM by BrianPa RSS

    EM12cR2 - "Job Purge" repository scheduler job falsely(?) reported down

    BrianPa
      EM12cR2 on Linux x86-64 with an 11.2.0.3 repository database. This popped up after my upgrade from 12.1.0.1+BP1 yesterday.

      On the Repository page (Setup -> Manage Cloud Control -> Repository), in the Repository Scheduler Jobs Status section, the "Job Purge" job is shown as down with a red arrow and blanks for both Next Scheduled Run and Last Scheduled Run. All the other jobs look good and are running successfully.

      This also appears as an incident stating "DBMS Job UpDown for Job Purge exceeded the critical threshold (DOWN). Current value: DOWN".

      The framework metric reference manual for this metric (http://docs.oracle.com/cd/E24628_01/em.121/e25162/oracle_emrep.htm#autoId20) indicates that this metric equates to the DBMS_JOB 'broken' status and suggests retrieving the job_id and re-submitting it, but the provided instructions don't find anything useful.
      SQL> sho user                            
      USER is "SYSMAN"
      SQL> select dbms_jobname from mgmt_performance_names where display_name = 'Job Purge';
      
      DBMS_JOBNAME
      --------------------------------------------------------------------------------
      MGMT_JOB_ENGINE.apply_purge_policies()
      
      SQL> select job from all_jobs where what='MGMT_JOB_ENGINE.apply_purge_policies()';
      
      no rows selected
      
      SQL> select count(*) from all_jobs;
      
        COUNT(*)
      ----------
               0
      No ORA-12012 messages found in the alert/trace logs.

      Repvfy also reports this as a missing scheduler job:
      2. Missing DBMS_SCHEDULER jobs
      ------------------------------
      
      DISPLAY_NAME                             DBMS_JOBNAME
      ---------------------------------------- -----------------------------------------------------
      Job Purge                                MGMT_JOB_ENGINE.apply_purge_policies()
      The MGMT_JOB_ENGINE package no longer contains apply_purge_policies. It seems to have moved to EM_JOB_PURGE.

      According to dba_scheduler_jobs, EM_JOB_PURGE.APPLY_PURGE_POLICIES is running just fine:
      SQL> select job_action, enabled, state, failure_count, last_start_date, last_run_duration
        2  from dba_scheduler_jobs where job_name = 'EM_JOB_PURGE_POLICIES';
      
      JOB_ACTION                               ENABL STATE      FAILURE_COUNT
      ---------------------------------------- ----- ---------- -------------
      LAST_START_DATE
      ----------------------------------------
      LAST_RUN_DURATION
      ----------------------------------------
      EM_JOB_PURGE.APPLY_PURGE_POLICIES();     TRUE  SCHEDULED              0
      14-SEP-12 05.00.00.010318 AM US/EASTERN
      +000000000 00:00:09.464552
      It seems to me this is some kind of metadata inconsistency between mgmt_performance_names and the DBMS scheduler, and probably isn't something to be concerned with. Any thoughts?

      Edited by: BrianP on Sep 14, 2012 10:38 AM (subject line typo, missed the word 'job')