Wednesday, August 27, 2008

DBA_SCHEDULER_JOB_LOG

Thank you for visiting Spatial DBA - Oracle and ArcSDE.

Please visit Oracle DBA Tips (http://www.oracledbatips.com) for more Oracle DBA Tips.
==================================================================



Oracle 11gR1
DBA_SCHEDULER_JOB_LOG displays log information for all Scheduler jobs in the database. Its columns are the same as those in ALL_SCHEDULER_JOB_LOG.

Related Views
· ALL_SCHEDULER_JOB_LOG displays log information for the Scheduler jobs accessible to the current user.
· USER_SCHEDULER_JOB_LOG displays log information for the Scheduler jobs owned by the current user.
Column
Datatype
NULL
Description
LOG_ID
NUMBER
NOT NULL
Unique identifier that identifies a row
LOG_DATE
TIMESTAMP(6) WITH TIME ZONE
Date of the log entry
OWNER
VARCHAR2(30)
Owner of the Scheduler job
JOB_NAME
VARCHAR2(65)
Name of the Scheduler job
JOB_SUBNAME
VARCHAR2(65)
Subname of the Scheduler job (for a chain step job)
JOB_CLASS
VARCHAR2(30)
Class that the job belonged to at the time of entry
OPERATION
VARCHAR2(30)
Operation corresponding to the log entry
STATUS
VARCHAR2(30)
Status of the operation, if applicable. Possible values for this column are dependent on the value in the OPERATION column. In most cases, STATUS will be NULL. Only for job run operations will it have a value.
STATUS will be NULL when OPERATION is one of the following:
· CREATE - Job was created
· UPDATE - One or more job attributes have been modified
· ENABLE - Job has been enabled
· DISABLE - Job has been disabled
· COMPLETED - For repeating jobs only, job has reached its end date or maximum number of runs
· BROKEN - Job has reached its maximum number of failures
STATUS can be SUCCEEDED (job run completed successfully), FAILED (job run failed), or STOPPED (job run was stopped) when OPERATION is one of the following:
· RUN - Regular job run
· RETRY_RUN - Job is being retried because the previous run resulted in an error and RESTARTABLE is set to TRUE
· RECOVERY_RUN - Job is being rerun because the database went down, or the job slave crashed and RESTARTABLE is set to TRUE
USER_NAME
VARCHAR2(30)
Name of the user who performed the operation, if applicable
CLIENT_ID
VARCHAR2(64)
Client identifier of the user who performed the operation, if applicable
GLOBAL_UID
VARCHAR2(32)
Global user identifier of the user who performed the operation, if applicable
DESTINATION
VARCHAR2(128)
Destination for a remote job operation
ADDITIONAL_INFO
CLOB
Additional information on the entry, if applicable
Note:
1.
select log_id, log_date, owner, job_name, job_class, operation, status
from DBA_SCHEDULER_JOB_LOG
order by log_date desc;
LOG_ID
LOG_DATE
OWNER
JOB_NAME
JOB_CLASS
OPERATION
STATUS
21841
2008-08-27 3:00:01.521593 AM -07:00
SYS
PURGE_LOG
DEFAULT_JOB_CLASS
RUN
SUCCEEDED
21823
2008-08-26 11:32:06.483508 PM -07:00
SYS
GATHER_STATS_JOB
AUTO_TASKS_JOB_CLASS
RUN
SUCCEEDED
21822
2008-08-26 10:31:50.226223 PM -07:00
SYS
AUTO_SPACE_ADVISOR_JOB
AUTO_TASKS_JOB_CLASS
RUN
SUCCEEDED
21781
2008-08-26 3:00:01.520328 AM -07:00
SYS
PURGE_LOG
DEFAULT_JOB_CLASS
RUN
SUCCEEDED
21763
2008-08-25 11:32:35.439152 PM -07:00
SYS
GATHER_STATS_JOB
AUTO_TASKS_JOB_CLASS
RUN
SUCCEEDED
21762
2008-08-25 10:22:00.342972 PM -07:00
SYS
AUTO_SPACE_ADVISOR_JOB
AUTO_TASKS_JOB_CLASS
RUN
SUCCEEDED
21742
2008-08-25 3:00:01.283498 AM -07:00
SYS
PURGE_LOG
DEFAULT_JOB_CLASS
RUN
SUCCEEDED
2. When STATUS shows FAILED, you can drill down further to find out the cause from the view DBA_SCHEDULER_JOB_RUN_DETAILS.

Oracle data dictionary views