Access plan
Certain data is necessary to resolve an explainable statement. An access plan specifies an order of operations for accessing this data.
An access plan lets you view statistics for selected tables, indexes, or columns; properties for operators; global information such as table space and function statistics; and configuration parameters relevant to optimization.
The optimizer produces an access plan whenever you compile an explainable SQL or XQuery statement. This happens at prep/bind time for static statements, and at run time for dynamic statements.
- Statistics in system catalog tables (if statistics are not current, update them using the RUNSTATS command.)
- Configuration parameters
- Bind options
- The query optimization class
Cost information associated with an access plan is the optimizer's best estimate of the resource usage for a query. The actual elapsed time for a query might vary depending on factors outside the scope of the database manager (for example, the number of other applications running at the same time). Actual elapsed time can be measured while running the query, by using performance monitoring.