Skip to main content

Oracle Parallel Server Option in Explain Plan

Oracle parallel option:
Parallel option parameter in int.ora:

parallel_degree_level                        integer     100
parallel_degree_limit                        string      CPU
parallel_degree_policy                      string      AUTO
parallel_execution_message_size     integer     15343
parallel_max_servers                        integer     743
parallel_min_servers                         integer     76
parallel_min_time_threshold            string      AUTO
parallel_server                                   boolean     TRUE
parallel_server_instances                  integer     4
parallel_servers_target                      integer     374
parallel_threads_per_cpu                  integer     2

In an explain plan PX stands for Parallel processing.
PX Send are producer
PX Receiver receiver
PX Coordinator
PX COORDINATOR FORCED SERIAL operation means that, although the plan looks like a parallel execution, Oracle effectively will run this serially at execution time.
IN-OUT column is either P->P or P->S (line 2)
P->P means that data is being sent from one parallel operation to another.
P->S means that data is being sent from a parallel operation to serial operation
P->S QC, which is a single process
PCWC Parallel Combine with Child
PCWP Parallel Combine with Parent
HASH: Hash redistribution is very common in parallel execution in order to achieve an equal distribution among the parallel server processes.
A hash function is applied to the join column and the result dictates which consumer parallel server process should receive the row.
BROADCAST: Broadcast redistribution happens when one of the two result sets in a join operation is much smaller than the other result set. Instead of redistributing rows from both result sets the database sends the smaller result set to all of the consumer parallel server processes in order to guarantee the individual servers are able to complete their join operation.
RANGE: Range redistribution is generally used for parallel sort operations. Individual parallel server processes work on data ranges so that the QC does not have to do any additional sorting but only present the individual parallel server processes results in the correct order.
KEY: Key redistribution ensures result sets for individual key values are clumped together. This is an optimization that is primarily used for partial partition-wise joins to ensure only one side in the join has to be redistributed.
ROUND ROBIN: Round-robin data redistribution can be the final redistribution operation before sending data to the requesting process.
It can also be used in an early stage of a query when no redistribution constraints are required.
Ref:
http://www.oracle.com/technetwork/database/bi-datawarehousing/twp-explain-the-explain-plan-052011-393674.pdf
http://www.oracle.com/technetwork/articles/database-performance/geist-parallel-execution-1-1872400.html
http://www.oracle.com/technetwork/database/manageability/con9579-sql-tune-cookbook-2031472.pdf
 

Comments

Popular posts from this blog

MySQL InnoDB cluster troubleshooting | commands

Cluster Validation: select * from performance_schema.replication_group_members; All members should be online. select instance_name, mysql_server_uuid, addresses from  mysql_innodb_cluster_metadata.instances; All instances should return same value for mysql_server_uuid SELECT @@GTID_EXECUTED; All nodes should return same value Frequently use commands: mysql> SET SQL_LOG_BIN = 0;  mysql> stop group_replication; mysql> set global super_read_only=0; mysql> drop database mysql_innodb_cluster_metadata; mysql> RESET MASTER; mysql> RESET SLAVE ALL; JS > var cluster = dba.getCluster() JS > var cluster = dba.getCluster("<Cluster_name>") JS > var cluster = dba.createCluster('name') JS > cluster.removeInstance('root@<IP_Address>:<Port_No>',{force: true}) JS > cluster.addInstance('root@<IP add>,:<port>') JS > cluster.addInstance('root@ <IP add>,:<port> ') JS > dba.getC...

InnoDB cluster Remove Instance Force | Add InnoDB instance

InnoDB cluster environment UUID is different on node: To fix it stop group replication, remove instance (use force if require), add instance back Identify the node which is not in sync: Execute following SQL statement on each node and identify the node has different UUID on all nodes. mysql> select * from mysql_innodb_cluster_metadata.instances; Stop group replication: Stop group replication on the node which does not have same UUID on all nodes. mysql > stop GROUP_REPLICATION; Remove instances from cluster: Remove all secondary node from the cluster and add them back if require. $mysqlsh JS >\c root@<IP_Address>:<Port_No> JS > dba.getCluster().status() JS > dba.getCluster () <Cluster:cluster_name> JS > var cluster = dba.getCluster("cluster_name"); JS >  cluster.removeInstance('root@<IP_Address>:<Port_No>'); If you get "Cluster.removeInstance: Timeout reached waiting......" JS > cluster.removeInstance(...

Oracle E-Business Suite Online Patch Phases executing adop

Following description about Oracle E-Business Suite is high level and from documentation https://docs.oracle.com/cd/E26401_01/doc.122/e22954/T202991T531062.htm#5281339 for in depth and detail description refer it. The online patching cycle phases: Prepare Apply Finalize Cutover Cleanup Prepare phase: Start a new online patching cycle, Prepares the environment for patching. $ adop phase=prepare Apply phase: Applies the specified patches to the environment. Apply one or more patches to the patch edition. $ adop phase=apply patches=123456,789101 workers=8 Finalize phase: Performs any final steps required to make the system ready for cutover. Perform the final patching operations that can be executed while the application is still online. $ adop phase=finalize Cutover phase: Shuts down application tier services, makes the patch edition the new run edition, and then restarts application tier services. This is the only phase that involves a brief ...