EM 13c EM_ECM_VCPU_JOB DBMS Scheduler Job stuck in running state forever (Doc ID 2786745.1)

Last updated on SEPTEMBER 23, 2022

Applies to:

Symptoms

Long running DBMS scheduler job on the repository database

JOB_NAME                            JOB_SUBNAME          NEXT_RUN_DATE                                                     STATE                     FAILURE_COUNT

-----------------------              --------------             --------------------------------------------------------     --------------------    -------------

EM_ECM_VCPU_JOB                                               14-NOV-20 11.00.00.714633 PM EUROPE/BERLIN      RUNNING                  2

  
DECLARE job BINARY_INTEGER := :job; next_date TIMESTAMP WITH TIME ZONE := :mydate; broken BOOLEAN := FALSE; job_name VARCHAR2(128) := :job_name; job_subname VARCHAR2(128) := :job_subname; job_owner VARCHAR2(128) := :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(128) := :credown; credential_name VARCHAR2(128) := :crednam; destination_owner VARCHAR2(128) := :destown; destination_name VARCHAR2(128) := :destnam; job_dest_id varchar2(14) := :jdestid; log_id number := :log_id; BEGIN EM_ECM_VCPU_COLLECTION.vcpu_computation_job(); :mydate := next_date; IF broken THEN :b := 1; ELSE :b := 0; END IF; END;


Module : DBMS_SCHEDULER
Action : EM_ECM_VCPU_JOB
Parsing Schema : SYSMAN
PL/SQL Source (Line Number) : SYSMAN.EM_ECM_VCPU_COLLECTION (1671)

Changes

Cause

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