hi there,
I have materialized views being refreshed via dbms_scheduler that runs fine in promotional environments but did not work for its first test in a new environment. other mv refresh jobs did run successfully in the test environment.
the dba_scheduler_job_log view provides that the associated job OPERATION: RUN is STOPPED with REASON:REASON="Stop job called".
what might cause a dbms_scheduler job to be stopped in such a fashion?
database is Release 12.1.0.2.0.