Databases Reference
In-Depth Information
Now a Job can belong to this class, automatically being enforced to comply with the
resource allocation policy that governs the Job Class.
BEGIN
sys.dbms_scheduler.set_attribute(
name => '"OSCHEDULER"."TEST_MINUTELY"',
attribute => 'job_class',
value => 'LOW_GROUP_JOB_CLASS');
END;
/
And finally we can see the job belongs to the
LOW_GROUP_JOB_CLASS
:
SQL> select OWNER,
2 JOB_NAME,
3 JOB_CLASS
4 from DBA_SCHEDULER_JOBS
5 where OWNER = 'OSCHEDULER';
OWNER JOB_NAME JOB_CLASS
---------- ---------------------- ----------------------
OSCHEDULER TEST_SCHEDULER DEFAULT_JOB_CLASS
OSCHEDULER TEST_MINUTELY LOW_GROUP_JOB_CLASS
OSCHEDULER MONTHLYTEST DEFAULT_JOB_CLASS
OSCHEDULER OS_LOG_RECORDS_JOB DEFAULT_JOB_CLASS
Managing the Scheduler
While defining a schedule it is not required to launch the schedule immediately
afterwards. A scheduled task can be created in a disabled status so that the user can
schedule it at a later time.
All tasks leave a log that can be used to validate that the task was successful or to
find out if a scheduled task failed and why. The user should know how and when to
purge it so it doesn't grow too big.
Search WWH ::
Custom Search