Neoview Query Guide (R2.2)

The CURSOR_DELETE operator has no child operators. The description field for this operator
contains:
Data TypeToken DescriptionToken
integerA sequential number assigned to the fragment. 0 is always master executor
and 1 is reserved for the Explain plan. Numbers 2 to n will be ESP or DAM
fragments.
fragment_id
integerThe fragment_id for the parent fragment of the current fragment. Value is
(none) for master executor.
parent_frag
textmaster, ESP, or DAMfragment_type
textIndicates whether an optimization for short, simple operations is used.
Value is used if this optimization is used.
olt_optimization
textIndicates for short, simple operations whether a further optimization that
reduces the physical size of the plan is used.
olt_opt_lean
expr(text)Type of delete followed by table or index nameiud_type
textPresent only if partition name is specified in the DELETE statement. Returns
the name of the partition.
partition_name
expr(text)Computation of the row to be deletednew_rec_expr
expr(text)Computation of the row to be deleted into each index tablenew_idx_rec_expr
expr(text)Expression of the begin key predicatesbegin_key
expr(text)Expression of the begin key predicates on indexindex_begin_key
expr(text)Predicate expression specified on partitioning key. It is displayed only if
partitioning key differs from clustering key
part_key_predicate
textCheck constraints on the delete tablecheck_constraint
SUBSET_DELETE Operator
The SUBSET_DELETE operator describes a portion of an execution plan that details how a certain
access path is scanned: it deletes more than one row. A subset operation performs the read and
delete in a combined operation. This operation differs from CURSOR_DELETE, which performs
the read and delete in separate operations. The CURSOR_DELETE operation also involves more
messages.
This operator has no child operators. The description field for this operator contains
Data TypeToken DescriptionToken
integerA sequential number assigned to the fragment. 0 is always master executor
and 1 is reserved for the Explain plan. Numbers 2 to n will be ESP or DAM
fragments.
fragment_id
integerThe fragment_id for the parent fragment of the current fragment. Value is
(none) for master executor.
parent_frag
textmaster, ESP, or DAMfragment_type
expr(text)subset_delete followed by the table nameiud_type
text
Displays volatile and is present only if the delete is to a volatile table.
object_type
textPresent only if partition name is specified in the DELETE statement. Returns
the name of the partition.
partition_name
expr(text)Computation of the row to be deletednew_rec_expr
expr(text)Computation of the row to be deleted into each index tablenew_idx_rec_expr
Understanding Joins 51