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
IN PLS_INTEGER DEFAULT 0,
The parameters and usages associated with this
procedure are listed below:
- This determines the age of the logs that
should be kept. Valid values range between
zero and 999 with the default being zero.
- This indicates which log or logs should be
purged. The possible parameters are
with the latter being the default value.
- 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:
log_history => 5,
log_history => 15,
log_history => 0,
To purge all entries for both the job and window
logs, simply call the procedure with no
auto_purge procedure uses
values defined at the scheduler, job class and
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
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
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