Search notes:

Oracle: Scheduler related base tables

select
   lower(table_name) t
from
   dba_tables
where
   table_name like 'SCHEDULER$%' and
   owner = 'SYS'
order by
   table_name;
--
-- scheduler$_chain
-- scheduler$_class
-- scheduler$_constraints
-- scheduler$_constraints_stats
-- scheduler$_credential
-- scheduler$_dbmsjob_map
-- scheduler$_destinations
-- scheduler$_event_log
-- scheduler$_event_qtab
-- scheduler$_evtq_sub
-- scheduler$_filewatcher_history
-- scheduler$_filewatcher_resend
-- scheduler$_file_watcher
-- scheduler$_global_attribute
-- scheduler$_job
-- scheduler$_job_argument
-- scheduler$_job_destinations
-- scheduler$_job_output
-- scheduler$_job_out_args
-- scheduler$_job_run_details
-- scheduler$_lightweight_job
-- scheduler$_listeneraddresses
-- scheduler$_lwjob_obj
-- scheduler$_notification
-- scheduler$_program
-- scheduler$_program_argument
-- scheduler$_remdb_jobqtab
-- scheduler$_remote_dbs
-- scheduler$_remote_job_state
-- scheduler$_resources
-- scheduler$_rjob_src_db_info
-- scheduler$_saved_oids
-- scheduler$_schedule
-- scheduler$_srcq_info
-- scheduler$_srcq_map
-- scheduler$_step
-- scheduler$_step_state
-- scheduler$_window
-- scheduler$_window_details
-- scheduler$_window_group
-- scheduler$_wingrp_member

LOG_ID

The tables scheduler$_job_run_details and scheduler$_event_log can be joined on log_id.
scheduler$_job_output can be left joined on log_id.
log_id is unique (primary key) in scheduler$_job_run_details.
In scheduler$_event_log, the primary key is log_id, dbid (because standby event logs contain events from more than one server: primary and standby).

See also

dbms_scheduler

Index