You use the set_attribute procedure to set the job_priority which defaults to 3
out of 1 to 5 with 1 being highest.
DBMS_SCHEDULER
(oracle.com)<https://docs.oracle.com/en/database/oracle/oracle-database/19/arpls/DBMS_SCHEDULER.html#GUID-D7A11F8A-8746-4815-91C4-BC8DDBA4C74A>
PL/SQL Packages and Types
Reference<https://docs.oracle.com/en/database/oracle/oracle-database/19/arpls/DBMS_SCHEDULER.html#GUID-D7A11F8A-8746-4815-91C4-BC8DDBA4C74A>
The DBMS_SCHEDULER package provides a collection of scheduling functions and
procedures that can be called from any PL/SQL program.
docs.oracle.com
Mark Powell
Database Administration
(313) 592-5148
________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx <oracle-l-bounce@xxxxxxxxxxxxx> on behalf
of Fairlie Rego <fairlie.rego@xxxxxxxxx>
Sent: Thursday, May 25, 2023 5:23 AM
To: ORACLE-L <oracle-l@xxxxxxxxxxxxx>
Subject: job_priority for Oracle scheduler jobs
Hi all,
I am currently working on a system which is a heavy user of Oracle scheduler
jobs. During certain hours we have almost 20,000 jobs running in an hour
and some critical ones do not seem to get kicked off at the exact time they
need to run.
Is anyone using the job_priority feature and if so in what version and have
they faced any issues with it.?
"When several jobs within the same job class are scheduled to start at the same
time, the job coordinator uses the job priority to decide which job to execute
first."
[image.png]
Cheers
Fairlie