October 2005
Intermediate to advanced
454 pages
14h 44m
English
Like most scheduling systems, the Oracle Scheduler executes programs in the background, where no direct feedback to users or administrators can take place. Given this situation, how can you diagnose issues related to jobs after those jobs have stopped running? The Scheduler allows you to do so with the extensive logging information generated by your job operations and window operations. I’ll describe logging for both in the following sections.