Oracle Consulting Oracle Training Development

Remote DBA

Remote DBA Plans  

Remote DBA Service

Remote DBA RAC

Remote DBA Oracle Home
Remote DBA Oracle Training
Remote DBA SQL Tuning Consulting
Remote DBA Oracle Tuning Consulting
Remote DBA Data Warehouse Consulting
Remote DBA Oracle Project Management
Remote DBA Oracle Security Assessment
Remote DBA Unix Consulting
Burleson Books
Burleson Articles
Burleson Web Courses
Burleson Qualifications
Oracle Links
Remote DBA Oracle Monitoring
Remote DBA Support Benefits
Remote DBA Plans & Prices
Our Automation Strategy
What We Monitor
Oracle Apps Support
Print Our Brochure
Contact Us (e-mail)
Oracle Job Opportunities
Oracle Consulting Prices





Remote DBA services

Remote DBA Support

Remote DBA RAC

Remote DBA Reasons

Remote Oracle Tuning

Remote DBA Links

Oracle DBA Support

Oracle DBA Forum

Oracle Disaster

Oracle Training

Oracle Tuning

Oracle Training

 Remote DBA SQL Server

Remote MSSQL Consulting

Oracle DBA Hosting

Oracle License Negotiation







 Oracle Scheduler Purging Window Logs
Oracle Tips by Burleson Consulting

Advanced Oracle Utilities: The Definitive Reference by Rampant TechPress is written by the top Oracle database experts (Bert Scalzo, Donald Burleson, and Steve Callan).  The following is an excerpt from the book.

Purging Logs

On occasion, it may be necessary to manually purge the scheduler logs prior to any regularly scheduled automatic purge.  This can be accomplished using the purge_log procedure.


PROCEDURE purge_log(


  log_history        IN PLS_INTEGER DEFAULT 0,

  which_log          IN VARCHAR2    DEFAULT 'JOB_AND_WINDOW_LOG',

  job_name           IN VARCHAR2    DEFAULT NULL)


The parameters and usages associated with this procedure are listed below:

  • log_history - This determines the age of the logs that should be kept. Valid values range between zero and 999 with the default being zero.

  • which_log - This indicates which log or logs should be purged. The possible parameters are job_log, window_log and job_and_window_log, with the latter being the default value.

  • job_name - This limits the purge operation of a specific job, job class or comma separated list. By default, this parameter is set to NULL, which indicates logs for all jobs should be purged.

The following example shows how the procedure can be used:



  DBMS_SCHEDULER.purge_log (

    log_history => 5,

    which_log   => 'JOB_AND_WINDOW_LOG',

    job_name    => 'my_text_job');


  DBMS_SCHEDULER.purge_log (

    log_history => 15,

    which_log   => 'JOB_LOG',

    job_name    => 'my_text_job_class');


  DBMS_SCHEDULER.purge_log (

    log_history => 0,

    which_log   => 'WINDOW_LOG',

    job_name    => 'my_text_job');




To purge all entries for both the job and window logs, simply call the procedure with no parameters.




The auto_purge procedure uses the log_history values defined at the scheduler, job class and job log_history level to determine which logs should be purged. This procedure runs as part of the scheduled purge process, but it can also be run manually.




Depending on the circumstances, it is possible to manage the purging of logs manually as well as automatically.  Moving on to the management of resources, it was mentioned previously that windows are involved in the link between the scheduler and the resource manager.  In the following section, the link between these two functional areas will be examined.

r more details on Oracle utilities, see the book "Advanced Oracle Utilities" by Bert Scalzo, Donald K. Burleson, and Steve Callan.

You can buy it direct from the publisher for 30% off directly from Rampant TechPress.


Remote DBA Service

Oracle Tuning Book


Advance SQL Tuning Book 

BC Oracle support

Oracle books by Rampant

Oracle monitoring software










BC Remote Oracle Support

Remote DBA

Remote DBA Services

Copyright © 1996 -  2013 by Burleson. All rights reserved.

Oracle® is the registered trademark of Oracle Corporation.