FPSAPP.CFG_JOBS

LOAD_JOB

VARCHAR2(10)

Name of load job

CALLING_PROCEDURE

VARCHAR2(30)

For load jobs ending in IF, CALLING_PROCEDURE is the ADM_LOAD procedure which is scheduled either as part of ADM_LOAD_EVENT_HIST_VIA_APD or in CFG_SCHED. This procedure calls the ADM_LOAD_START_SHIFT_OR_WEEK procedure which has logic common to all ADMA+IF jobs. It calls the objects in the ADMA job in a loop. If inserts are made to the table listed in CALL_IF_INSERTS_IN_TABLE then this procedure makes an external call to the IF job.

CALL_IF_INSERTS_IN_TABLE

VARCHAR2(30)

This is the name of a table which must be part of the corresponding ADMA job in CFG_SCHED. If inserts are made in this table during the ADMA job then the ADM_LOAD_START_SHIFT_OR_WEEK procedure makes an external call to the IF job.

IS_EXTERNAL

CHAR(1)

Y means the job is called from an external scheduler like cron or Activity Manager otherwise it will be called by an Oracle job

NUM_OTHER_SLOW_JOBS_TO_ABORT

NUMBER(1)

To prevent overloading the data warehouse with too many jobs running at once, we want to prevent multiple slow jobs from running at the same time. The way we do this is to decline to start a slow job that is scheduled reasonably frequently like 10mi or 30mi when too many other slow jobs are running. These jobs will run again reasonably soon so it is not a big deal to have them not run once or twice. We cannot decline to start the EaSh or StWk jobs since they are not scheduled frequently but we want to count them as running when considering whether to start 10mi and 30mi. Technically we do this with this column. A value greater than 0 means that we will not start the job if at least that many other slow jobs are running. Any value including 0 means that when running that it will be counted by other jobs consider whether to start. EaSh and StWk will always have a value of 0 which means they count as slow jobs but are always started on schedule. A common configuration would be to set both 10mi and 30mi to 2 when means that each job will not start when at least 2 of EaSh, StWk, and the other x0mi job are already running. At some sites, 10mi is essential so we could set to 0 meaning that it will always start on schedule and only 30mi will be submit to postponement. At sites when EaSh is reasonably fast then we might want to set 10mi and/or 30mi to 1 which that they do not start at all while EaSh is running. Please note that technically it is possible for too many jobs to be running simultaneously. One way would be if both 10mi and 30mi are running when EaSh starts then all three would be running even though 10mi and 30mi are set to 2. However since EaSh is by far the slowest of the three then we assume that either 10mi and 30mi will finish soon so we will get out of this state relatively quickly.