Oracle MFT Broken Jobs due to MATERIALIZED VIEW INVALID

(Doc ID 2314977.1)

Last updated on OCTOBER 06, 2017

Applies to:

Oracle Managed File Transfer - Version 12.2.1.0.0 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.1.0.0 version, Core MFT Application Console

ACTUAL BEHAVIOR
---------------
Oracle MFT Broken DB Jobs refreshing Materialized views

Checking on Database jobs, it was found that some JOBS spawn from MFT schema to materialized views where failing

Upon checking on the DB Job tables it was found that some of them are failing
SQL> SELECT JOB, LAST_DATE, NEXT_DATE, NEXT_SEC, FAILURES, BROKEN FROM DBA_JOBS ;

  JOB LAST_DATE NEXT_DATE NEXT_SEC FAILURES B
---------- --------- --------- -------------------------------- ---------- -
  4001 13-SEP-17 13-SEP-17 17:00:28 0 N
  4002 13-SEP-17 13-SEP-17 15:09:40 0 N
  15 13-SEP-17 13-SEP-17 15:03:20 0 N
  16 13-SEP-17 13-SEP-17 15:03:20 0 N
  17 13-SEP-17 13-SEP-17 15:02:50 0 N
  18 13-SEP-17 13-SEP-17 15:02:50 0 N
  19 13-SEP-17 13-SEP-17 15:03:20 0 N
  20 13-SEP-17 13-SEP-17 15:03:20 0 N
  21 26-FEB-17 01-JAN-00 00:00:00 16 Y
  22 13-SEP-17 13-SEP-17 15:03:20 0 N
  23 13-SEP-17 13-SEP-17 15:02:55 0 N
  24 13-SEP-17 13-SEP-17 15:03:20 0 N
  25 13-SEP-17 13-SEP-17 15:02:55 0 N
  26 26-FEB-17 01-JAN-00 00:00:00 16 Y

Here you see job 21 and 26 with Failures

Checking on this jobs where fond to be spawn from MFT schema

SQL> select job, schema_user, last_date, next_date, interval, what from dba_jobs where job in (21,26);

JOB SCHEMA_USERLAST_DATE NEXT_DATE INTERVAL WHAT
---- ---------- --------- --------- ----------------- -------------------------------------------------------------
 21 PHTSVO_MFT 26-FEB-17 01-JAN-00 SYSDATE + 1/1440 dbms_refresh.refresh('"XXXX_MFT"."MV_MFT_SOURCE_MESSAGE"');
 26 PHTSVO_MFT 26-FEB-17 01-JAN-00 SYSDATE + 1/1440 dbms_refresh.refresh('"XXXX_MFT"."MV_MFT_SOURCE_INFO"');

checking on the status of the Materialized views they show
SQL> select object_type,owner,object_type,status from dba_Objects where object_name in ('MV_MFT_SOURCE_MESSAGE','MV_MFT_SOURCE_INFO');

OBJECT_TYPE OWNER OBJECT_TYPE STATUS
------------------- ------------------------------ ------------------- -------
TABLE XXXX_SOAINFRA TABLE VALID
MATERIALIZED VIEW XXXX_SOAINFRA MATERIALIZED VIEW VALID
TABLE XXXX_SOAINFRA TABLE VALID
MATERIALIZED VIEW XXXX_SOAINFRA MATERIALIZED VIEW VALID
TABLE XXXX_MFT TABLE VALID
MATERIALIZED VIEW XXXX_MFT MATERIALIZED VIEW INVALID
TABLE XXXX_MFT TABLE VALID
MATERIALIZED VIEW XXXX_MFT MATERIALIZED VIEW INVALID

Analysis showed that previous simialr issues with materialized vies where fixed upon refreshing the actual vies, as reference:
Bug 26076341 : Schema Consolidation MFT install is not showing dashboard metrics
Bug 21530442 : near 100% CPU utilization by refresh materialized View process on the server


Due to the fact that his is a production environment, the job comes from MFT and the actual views are from MFT, customer needs to validate if this issue will be solved by running a full refresh of the table as per
execute dbms_mview.refresh('MV_MFT_SOURCE_MESSAGE','f');
execute dbms_mview.refresh('MV_MFT_SOURCE_INFO','f');


EXPECTED BEHAVIOR
-----------------------
to return the materialized vies to a valid state so the jobs can run

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms