How To Incorporate Pre-Defined jobs into your Resource Manager Plan
(Doc ID 971991.1)
Last updated on NOVEMBER 27, 2019
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.1 and later
Information in this document applies to any platform.
A standard Oracle Database is delivered with several pre-defined jobs that are scheduled to run on a specific schedule. The names and actions may be different from release to release but the concept is basically the same. Some example of these jobs are AUTO_GATHER_JOB, AUTO_SPACE_ADVISOR_JOB, etc
Oracle 10g, does not have pre-defined settings regarding resource manager and therefor the jobs will be run under the consumer group credentials of the user SYS or even worse in the OTHER_GROUPS consumer group.
As of Oracle 11g, the default maintenance window linked to the jobs will automatically switch the database into the DEFAULT_MAINTENANCE_PLAN plan and switych back to the original plan once the window has been closed.
While the credentials specified in the DEFAULT_MAINTENANCE_PLAN plan is suited for most database, some high demand environment such as 24*7 activity have the need to plan maintenance resources in a more intelligent manor. This article will illustrate how this can be achieved
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