Job Scheduler secondary are not mapped to proper Consumer Group
(Doc ID 785541.1)
Last updated on APRIL 06, 2022
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.1 to 10.2.0.4 [Release 10.2]
Information in this document applies to any platform.
This problem can occur on any platform.
Problem prevents users from controlling the degree of parallelism of their batch jobs.
When they create a scheduler job to run their process code, they specify that the job run under specific Job Class.
That Job Class is associated with a Resource Consumer Group that is part of the active resource plan.
The Consumer Group Plan Directives which specify the degree of parallelism limits.
– one for parallel server limits which controls the degree of parallelism of parallel query/dml in the code
- and one for active session limit, which controls the number of threads spawned during process code is run
What occurs is the Job Class and Consumer Group mapping is INTERMITTENTLY ignored.
This causes scheduler job to run in the OTHER_GROUPS Consumer Group instead of the
consumer Group they specifically created.
To summarize, the Job Scheduler secondary are not getting mapped correctly to the corresponding resource Consumer Group.
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