RAC: How to Control Parallel Execution Across Database Instances 11g and Higher
Last updated on FEBRUARY 13, 2017
Applies to:Oracle Database - Enterprise Edition - Version 220.127.116.11 and later
Oracle Database - Standard Edition - Version 18.104.22.168 and later
Information in this document applies to any platform.
How to control parallel execution across instances in versions 11g and higher
In 10g, parallel execution in RAC instances is controlled with two initialization parameters: INSTANCE_GROUPS and PARALLEL_INSTANCE_GROUP. Both must be used together in 10g.
INSTANCE_GROUPS can have multiple values but it is static; PARALLEL_INSTANCE_GROUP can be modified dynamically at the system level and can also be set at the session level.
In 10g, in order for parallel execution to occur in a session where you have PARALLEL_INSTANCE_GROUP set, the value for PARALLEL_INSTANCE_GROUP has to be found in the list of groups specified by INSTANCE_GROUPS for that instance.
MYRAC1.parallel_instance_group='MYRAC1' # executions started on node 1 runs only on node 1
MYRAC2.parallel_instance_group='MYRAC2' # executions started on node 2 runs only on node 2
MYRAC3.parallel_instance_group='MYRAC3' # executions started on node 3 runs only on node 3
See Note 1260674.1 for more on the use of INSTANCE_GROUPS and PARALLEL_INSTANCE_GROUP in 10g.
In 11g, you can still use INSTANCE_GROUPS and PARALLEL_INSTANCE_GROUP in the same way for backward compatability. However, in 11g, it is no longer necessary to do so.
The INSTANCE_GROUPS parameter is deprecated in 11g and retained for backward compatability only.
The purpose of this note is to describe the new ways in which parallel execution across instances can be controlled in 11g.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms