Which three factors does the estimator depend on for overall cost estimation of a given execution plan?

Which three factors does the estimator depend on for overall cost estimation of a given execution
plan?

Which three factors does the estimator depend on for overall cost estimation of a given execution
plan?

A.
Cardinality

B.
Sort area size

C.
OPTIMIZER_FEATURE_ENABLE parameter

D.
NOT NULL_FEATURE_ENABLE parameter

E.
NOT NULL constraint on a unique key column

F.
Library cache size

G.
The units of work such as disk input/output, CPU usage, and memory used in an operation

Explanation:
C: OPTIMIZER_FEATURES_ENABLE acts as an umbrella parameter for enabling a
series of optimizer features based on an Oracle release number.
Note: The estimator determines the overall cost of a given execution plan. The estimator
generates three different types of measures to achieve this goal:
* Selectivity

This measure represents a fraction of rows from a row set. The selectivity is tied to a query
predicate, such as last_name=’Smith’, or a combination of predicates.
* Cardinality
This measure represents the number of rows in a row set.
1,
* Cost
This measure represents units of work or resource used. The query optimizer uses disk I/O, CPU
usage, and memory usage as units of work.
If statistics are available, then the estimator uses them to compute the measures. The statistics
improve the degree of accuracy of the measures.



Leave a Reply 4

Your email address will not be published. Required fields are marked *


vasya_pupkin

vasya_pupkin

The estimator is the component of the optimizer that determines the overall cost of a given execution plan. The estimator uses three different types of measures to achieve this goal:
*Selectivity
*Cardinality
*Cost (This measure represents units of work or resource used. The query optimizer uses disk I/O, CPU usage, and memory usage as units of work.)

So, A and G – correct.
Answer C – wrong.
Which of the others answers concerns selectivity – I don’t know.

pvd

pvd

optimizer controlling parameter :- PGA_AGGREGATE_TARGET
so what about Sort area size