My Oracle Support Banner

PURGE_LOG Job will purge all entries and ignore the setting of LOG_HISTORY (Doc ID 1270854.1)

Last updated on JANUARY 27, 2023

Applies to:

Oracle Database - Enterprise Edition - Version 11.1.0.7 to 12.1.0.2 [Release 11.1 to 12.1]
Information in this document applies to any platform.

Symptoms


In a database version 11.1.0.7  or later versions,
there can be the situation where the automatic purge job (PURGE_LOG)
purge more entries from the scheduler log tables than expected. In that case the setting of log_history
will be ignored by the purge job .

Some generics:
The attribute log_history controls the number of days that log entries for both the job log and
the window log are retained. It helps prevent logs from growing indiscriminately.
Log_history can be set explicit as a global attribute or can be set explicit for a job class.
When not explicit set, then there is a default value of 30 days.


Example how to set the log history for the default_job_class to 5:



The purge job is a default Oracle job which will be executed per default schedule at 3 am, every day.


Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.