Graziano, July 26, 2010 - 2:50 am UTC
Shin Zeng, June 28, 2017 - 7:44 pm UTC
I did 'alter materialized view mv_nm refresh start with sysdate+0.1/24 next sysdate+1/24', and checked dba_jobs - the job was scheduled to run in 0.1 hour, but after an hour, I checked the NEXT column in dba_jobs, it's still the original one, I checked dba_mview, the last_refresh was still a few days ago - it did not refresh. job_queue_processes parameter in the database is set to 16. At the moment, only one job was running. I manually refreshed it with dbms_refresh.refresh('mv_nm'), and it worked, but the NEXT column in dba_jobs did not change at all
June 29, 2017 - 2:06 am UTC
Perhaps submit a standalone job, ie
variable j number
exec dbms_job.submit(:j, 'dbms_refresh.refresh(''mv_nm')';', sysdate, sysdate+1/24);
or similar.