Oracle PL/SQL for DBAs

Job Logs

There are two data dictionary views that show information about job logs : DBA_SCHEDULER_JOB_LOG and DBA_SCHEDULER_JOB_RUN_DETAILS.

DBA_SCHEDULER_JOB_LOG

When jobs are created, altered, dropped, and run, the results are loaded into a summary table that is visible through the DBA_SCHEDULER_JOB_LOG view . Its columns are listed in the following table.

Column name	Description
LOG_ID	Unique identifier for each record.
LOG_DATE	Timestamp of the log entry.
OWNER	Owner of the job.
JOB_NAME	Name of the job.
JOB_CLASS	Job class, if any.
OPERATION	What happened during the job entry (e.g., CREATE, RUN, BROKEN).
STATUS	What happened after the operation was performed by the job (e.g., SUCCEEDED, FAILED).
USER_NAME	Name of the user who invoked the job.
CLIENT_ID	Client identifier, if set using DBMS_SESSION.SET_IDENTIFIER.
GLOBAL_UID	If the user is a global user, the global UID is shown here.
ADDITIONAL_INFO	Any additional information about the job execution is stored as a CLOB in this column. For example, if the job was dropped automatically after it was successfully executed (provided that the auto_drop parameter was set to TRUE), then the OPERATION column shows DROP. However, you will not know from that column whether the job was dropped automatically or explicitly by a user. This column shows the specific reason for the drop. In this case, the column shows: REASON="Auto drop job dropped". Similarly, any other relevant information about the job execution is ...