How To Implement And Test Enhanced Statement Queuing In 12c So Critical Statements Bypass The Parallel Statement Queue.
(Doc ID 1518404.1)
Last updated on AUGUST 09, 2021
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168 and later
Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
In 12.1 Oracle introduces a new resource plan directives called PARALLEL_STMT_CRITICAL which allows critical parallel statements to bypass the parallel statement queue.
There are two options for this directive.
FALSE - The consumer group is non-critical. This is the default value
BYPASS_QUEUE - The consumer group is marked critical, and parallel statements from this consumer group will bypass the parallel statement queue
When set to BYPASS_QUEUE, the parallel statements from the specified consumer group will be executed immediately.
-- More flexibility in controlling critical work.
-- For autodop to work I/O calibration statistics must be gathered.
-- Parallel_degree_policy needs to be set to AUTO or ADAPTIVE to enable statement queuing
Note: With this setting in place it is possible that the number of parallel execution servers may exceed the value of the PARALLEL_SERVERS_TARGET initialization parameter.
The following example shows how to setup and confirm the use of BYPASS_QUEUE for one consumer group and PARALLEL_QUEUE_TIMEOUT for another.
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