DATABASE JOB NOTES:

Log User - USER who was logged in when the job was submitted.

Schema - Default schema used to parse the job. For example, if the SCHEMA_USER is SCOTT and you submit the procedure HIRE_EMP as a job, Oracle looks for SCOTT.HIRE_EMP.

Job# - Identifier of job. Neither import/export nor repeated executions change it.

Interval - A date function, evaluated at the start of execution, becomes next NEXT_DATE.

Next Execution - Date/time that this job will next be executed.

Broken - If Y, no attempt is made to run this job. See DBMS_JOBQ.BROKEN (JOB).

What - Body of the anonymous PL/SQL block that this job executes.

The DBMS_JOB package is actually an API into an Oracle subsystem known as the job queue. The Oracle job queue allows for the scheduling and execution of PL/SQL routines (jobs) at predefined times and/or repeated job execution at regular intervals. The DBMS_JOB package provides programs for submitting and executing jobs, changing job execution parameters, and removing or temporarily suspending job execution. This package is the only interface with the Oracle job queue.

DBMS_JOB is used to schedule many different types of tasks that can be performed in PL/SQL and that require regular execution. The job queue is used extensively by Oracle replication facilities, and was originally developed for the purpose of refreshing Oracle snapshots. DBMS_JOB is often used by DBAs to schedule regular maintenance activities on databases, typically during periods of low usage by end users. It can similarly be used by applications to schedule large batch operations during off hours. The job queue can also be used to start up service programs that listen on database pipes and respond to service requests by user sessions.