|
ADDRESS |
RAW(4) |
The address of the handle to the parent for this cursor |
|
HASH_VALUE |
NUMBER |
The hash value of the parent statement in the library cache. The two columns (ADDRESS, HASH_VALUE) can be used to join with V$SQLAREA to add the cursor-specific information. |
|
CHILD_NUMBER |
NUMBER |
Child cursor number using this execution plan. The columns (ADDRESS, HASH_VALUE, CHILD_NUMBER) can be used to join with V$SQL to add the child cursor-specific information. |
|
OPERATION |
VARCHAR2(30) |
The name of the internal operation performed in this step (for example, TABLE ACCESS) |
|
OPTIONS |
VARCHAR2(30) |
A variation on the operation described in the OPERATION column (for example, FULL) |
|
OBJECT_NODE |
VARCHAR2(10) |
The name of the database link used to reference the object (a table name or view name). For local queries using parallel execution, this column describes the order in which output from operations is consumed. |
|
OBJECT# |
NUMBER |
The object number of the table or the index |
|
OBJECT_OWNER |
VARCHAR2(30) |
The name of the user who owns the schema containing the table or index |
|
OBJECT_NAME |
VARCHAR2(64) |
The name of the table or index |
|
OPTIMIZER |
VARCHAR2(20) |
The current mode of the optimizer for the first row in the plan (statement line), for example, CHOOSE. When the operation is a database access (for example, TABLE ACCESS), this column indicates whether or not the object is analyzed. |
|
ID |
NUMBER |
A number assigned to each step in the execution plan |
|
PARENT_ID |
NUMBER |
The ID of the next execution step that operates on the output of the current step |
|
DEPTH |
NUMBER |
The depth (or level) of the operation in the tree. (It's not necessary to perform a "CONNECT BY" to get the level information, generally used to indent the rows from the PLAN_TABLE). The root operation (statement) is level 0. |
|
POSITION |
NUMBER |
The order of processing for all operations that have the same PARENT_ID |
|
COST |
NUMBER |
The cost of the operation as estimated by the optimizer's cost-based approach. For statements that use the rule-based approach, this column is null. |
|
CARDINALITY |
NUMBER |
The estimate, by the cost-based optimizer, of the number of rows produced by the operation |
|
BYTES |
NUMBER |
The estimate, by the cost-based optimizer, of the number of bytes produced by the operation |
|
OTHER_TAG |
VARCHAR2(35) |
Describes the contents of the OTHER column. See EXPLAIN PLAN for values. |
|
PARTITION_START |
VARCHAR2(5) |
The start partition of a range of accessed partitions |
|
PARTITION_STOP |
VARCHAR2(5) |
The stop partition of a range of accessed partitions |
|
PARTITION_ID |
NUMBER |
The step that computes the pair of values of the PARTITION_START and PARTITION_STOP columns |
|
OTHER |
VARCHAR2(4000) |
Other information specific to the execution step that users may find useful. See EXPLAIN PLAN for values. |
|
DISTRIBUTION |
VARCHAR2(20) |
Stores the method used to distribute rows from producer query servers to consumer query servers |
