| Operation | Option | Description |
|---|---|---|
|
|
|
Operation accepting multiple sets of rowids, returning the intersection of the sets, eliminating duplicates. Used for the single-column indexes access path. |
|
|
|
|
|
|
|
|
|
|
|
Merges several bitmaps resulting from a range scan into one bitmap. |
|
|
|
Subtracts bits of one bitmap from another. Row source is used for negated predicates. Can be used only if there are nonnegated predicates yielding a bitmap from which the subtraction can take place. An example appears in "Viewing Bitmap Indexes with EXPLAIN PLAN". |
|
|
|
Computes the bitwise |
|
|
|
Computes the bitwise |
|
|
|
Takes each row from a table row source and finds the corresponding bitmap from a bitmap index. This set of bitmaps are then merged into one bitmap in a following |
|
|
|
Retrieves rows in hierarchical order for a query containing a |
|
|
|
Operation accepting multiple sets of rows returning the union-all of the sets. |
|
|
|
Operation counting the number of rows selected from a table. |
|
|
Count operation where the number of rows returned is limited by the | |
|
|
|
Retrieval of one or more rowids from a domain index. The options column contain information supplied by a user-defined domain index cost function, if any. |
|
|
|
Operation accepting a set of rows, eliminates some of them, and returns the rest. |
|
|
|
Retrieval of only the first row selected by a query. |
|
|
|
Operation retrieving and locking the rows selected by a query containing a |
|
(These are join operations.) |
|
Operation joining two sets of rows and returning the result. This join method is useful for joining large data sets of data (DSS, Batch). The join condition is an efficient way of accessing the second table. CBO uses the smaller of the two tables/data sources to build a hash table on the join key in memory. Then it scans the larger table, probing the hash table to find the joined rows. |
|
|
|
Hash anti-join. |
|
|
|
Hash semi-join. |
|
(These are access methods.) |
|
Retrieval of a single rowid from an index. |
|
|
|
Retrieval of one or more rowids from an index. Indexed values are scanned in ascending order. |
|
|
|
Retrieval of one or more rowids from an index. Indexed values are scanned in descending order. |
|
|
|
Retrieval of all rowids from an index when there is no start or stop key. Indexed values are scanned in ascending order. |
|
|
|
Retrieval of all rowids from an index when there is no start or stop key. Indexed values are scanned in descending order. |
|
|
|
Retrieval of all rowids (and column values) using multiblock reads. No sorting order can be defined. Compares to a full table scan on only the indexed columns. Only available with the cost based optimizer. |
|
|
|
Retrieval of rowids from a concatenated index without using the leading column(s) in the index. Introduced in Oracle9i. Only available with the cost based optimizer. |
|
|
|
Iterates over the next operation in the plan for each value in the |
|
|
|
Operation accepting two sets of rows and returning the intersection of the sets, eliminating duplicates. |
|
(These are join operations.) |
|
Operation accepting two sets of rows, each sorted by a specific value, combining each row from one set with the matching rows from the other, and returning the result. |
|
|
|
Merge join operation to perform an outer join statement. |
|
|
|
Merge anti-join. |
|
|
|
Merge semi-join. |
|
|
|
Can result from 1 or more of the tables not having any join conditions to any other tables in the statement. Can occur even with a join and it may not be flagged as |
|
|
|
Retrieval of rows in hierarchical order for a query containing a |
|
|
|
Operation accepting two sets of rows and returning rows appearing in the first set but not in the second, eliminating duplicates. |
|
(These are join operations.) |
|
Operation accepting two sets of rows, an outer set and an inner set. Oracle compares each row of the outer set with each row of the inner set, returning rows that satisfy a condition. This join method is useful for joining small subsets of data (OLTP). The join condition is an efficient way of accessing the second table. |
|
|
|
Nested loops operation to perform an outer join statement. |
|
|
|
Access one partition. |
|
|
|
Access many partitions (a subset). |
|
|
|
Access all partitions. |
|
|
|
Similar to iterator, but based on an |
|
|
Indicates that the partition set to be accessed is empty. | |
|
Iterates over the next operation in the plan for each partition in the range given by the | ||
|
|
|
Retrieval of data from a remote database. |
|
|
|
Operation involving accessing values of a sequence. |
|
|
|
Retrieval of a single row that is the result of applying a group function to a group of selected rows. |
|
|
|
Operation sorting a set of rows to eliminate duplicates. |
|
|
|
Operation sorting a set of rows into groups for a query with a |
|
|
|
Operation sorting a set of rows before a merge-join. |
|
|
|
Operation sorting a set of rows for a query with an |
|
(These are access methods.) |
|
Retrieval of all rows from a table. |
|
|
|
Retrieval of sampled rows from a table. |
|
|
|
Retrieval of rows from a table based on a value of an indexed cluster key. |
|
|
|
Retrieval of rows from table based on hash cluster key value. |
|
|
|
Retrieval of rows from a table based on a rowid range. |
|
|
|
Retrieval of sampled rows from a table based on a rowid range. |
|
|
|
If the table rows are located using user-supplied rowids. |
|
|
|
If the table is nonpartitioned and rows are located using index(es). |
|
|
|
If the table is partitioned and rows are located using only global indexes. |
|
|
If the table is partitioned and rows are located using one or more local indexes and possibly some global indexes. | |
|
The partition boundaries might have been computed by: A previous The | ||
|
|
|
Operation accepting two sets of rows and returns the union of the sets, eliminating duplicates. |
|
|
|
Operation performing a view's query and then returning the resulting rows to another operation. |