This content has been marked as final. Show 3 replies
Hi Rod,1 person found this helpful
Yes, I believe so. Here's a test case that I just ran successfully from SQL Workshop in my database trial service:
Is the next_run_date in the past for your job? If it is, try disabling/enabling the job to "reinitialize" the job's schedule.
create table myjob_test (aa timestamp with time zone); begin cloud_scheduler.create_job ( job_name => 'MYJOB', job_type => 'PLSQL_BLOCK', job_action => 'begin insert into myjob_test values (systimestamp); commit; end;', repeat_interval => 'freq=minutely; interval=3' ); end; / begin cloud_scheduler.enable ( name => 'MYJOB' ); end; / select job_name, state, run_count, failure_count, last_start_date, next_run_date, systimestamp from sys.user_scheduler_jobs; select * from myjob_test order by aa;
Tested this again and the enable job now works. Not sure why it didn't before or why you get the error when you run_job with use_current_session=>false.
Thanks for your help.
The error with use_current_session=>false is expected due to resource limitations imposed by the cloud_scheduler package. The documentation is not clear about this, and I asked for it to be clarified.