My Oracle Support Banner

EM 13c: The Group Membership Sync up Job is Valid, but has an Invalid Schedule in Enterprise Manager 13.1 Cloud Control (Doc ID 2171948.1)

Last updated on JUNE 12, 2017

Applies to:

Enterprise Manager Base Platform - Version 13.1.0.0.0 to 13.1.0.0.0 [Release 13.1]
Information in this document applies to any platform.

Symptoms

Enterprise Manager (EM) 13.1.0.0.0 Cloud Control system, upgraded from 12.1

EM 13.1 Cloud Control shows that the Group Membership Sync Up DBMS job has an invalid schedule.
The job status appears to be valid, but its schedule is not, as shown below:

 

 

EMDIAG reports that this job is not running on schedule:

verifyCORE
======================================================================
1. DBMS_SCHEDULER jobs not running on schedule
=--------- ---------- ---------- ---------- ---------- ---------- ---------=
= Action:
= - Verify the DBMS_SCHEDULER operations in the database, and make sure
= the database scheduler is enabled, and has enough worker threads to
= do all the work
= - If the database scheduler is working properly, a check the
= performance of the repository database.
= To get performance details, run this report:
= $ repvfy dump advisors
= To get EM specific performance details, run this report:
= $ repvfy dump performance
=--------- ---------- ---------- ---------- ---------- ---------- ---------=

JOB_NAME JOB_SUBNAME NEXT_RUN_DATE STATE FAILURE_COUNT
---------------------------------------- -------------------------------------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------- --------------- -------------
EM_GROUP_MEMBER_SYNCUP 22-JUN-16 09.52.39.824794 AM MST7MDT RUNNING 0

1 row selected.

 

 

According to the AWR report, the query running behind this job is consuming significant resources:

Elapsed Time (s) Executions Elapsed Time per Exec (s) %Total %CPU %IO SQL Id SQL Module PDB Name SQL Text
604,730.80 0 39.35 89.78 7.84 79fgmjxku9z5v DBMS_SCHEDULER OEMPRD DECLARE job BINARY_INTEGER := ...

CPU Time (s) Executions CPU per Exec (s) %Total Elapsed Time (s) %CPU %IO SQL Id SQL Module PDB Name SQL Text
542,919.08 0 78.44 604,730.80 89.78 7.84 79fgmjxku9z5v DBMS_SCHEDULER OEMPRD DECLARE job BINARY_INTEGER := ...

User I/O Time (s) Executions UIO per Exec (s) %Total Elapsed Time (s) %CPU %IO SQL Id SQL Module PDB Name SQL Text
47,425.92 0 34.39 604,730.80 89.78 7.84 79fgmjxku9z5v DBMS_SCHEDULER OEMPRD DECLARE job BINARY_INTEGER := ...

Query consuming resources:
DECLARE job BINARY_INTEGER := :job; next_date TIMESTAMP WITH TIME ZONE := :mydate; broken BOOLEAN := FALSE; job_name VARCHAR2(30) := :job_name; job_subname VARCHAR2(30) := :job_subname; job_owner VARCHAR2(30) := :job_owner; job_start TIMESTAMP WITH TIME ZONE := :job_start; job_scheduled_start TIMESTAMP WITH TIME ZONE := :job_scheduled_start; window_start TIMESTAMP WITH TIME ZONE := :window_start; window_end TIMESTAMP WITH TIME ZONE := :window_end; chain_id VARCHAR2(14) := :chainid; credential_owner varchar2(30) := :credown; credential_name varchar2(30) := :crednam; destination_owner varchar2(30) := :destown; destination_name varchar2(30) := :destnam; job_dest_id varchar2(14) := :jdestid; log_id number := :log_id; BEGIN EM_GROUP.SYNC_UP_GROUP_MEMBERSHIP(); :mydate := next_date; IF broken THEN :b := 1; ELSE :b := 0; END IF; END;

 

 

 

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.