Oracle® Database SQL Reference 10g Release 2 (10.2) Part Number B14200-02 |
|
|
View PDF |
Purpose
Use the ANALYZE
statement to collect statistics, for example, to:
Collect or delete statistics about an index or index partition, table or table partition, index-organized table, cluster, or scalar object attribute.
Validate the structure of an index or index partition, table or table partition, index-organized table, cluster, or object reference (REF
).
Identify migrated and chained rows of a table or cluster.
Note:
Do not use theCOMPUTE
and ESTIMATE
clauses of ANALYZE
to collect optimizer statistics. These clauses are supported for backward compatibility. Instead, use the DBMS_STATS
package, which lets you collect statistics in parallel, collect global statistics for partitioned objects, and fine tune your statistics collection in other ways. The optimizer, which depends upon statistics, will eventually use only statistics that have been collected by DBMS_STATS
. See PL/SQL Packages and Types Reference for more information on the DBMS_STATS
package.
You must use the ANALYZE
statement (rather than DBMS_STATS
) for statistics collection not related to the cost-based optimizer, such as:
To use the VALIDATE
or LIST
CHAINED
ROWS
clauses
To collect information on freelist blocks
Prerequisites
The schema object to be analyzed must be local, and it must be in your own schema or you must have the ANALYZE
ANY
system privilege.
If you want to list chained rows of a table or cluster into a list table, then the list table must be in your own schema, or you must have INSERT
privilege on the list table, or you must have INSERT
ANY
TABLE
system privilege.
If you want to validate a partitioned table, then you must have the INSERT
object privilege on the table into which you list analyzed rowids, or you must have the INSERT
ANY
TABLE
system privilege.
Syntax
analyze::=
for_clause::=
into_clause::=
estimate_statistics_clause ::=
Semantics
schema
Specify the schema containing the table, index, or cluster. If you omit schema
, then Oracle Database assumes the table, index, or cluster is in your own schema.
Specify a table to be analyzed. When you collect statistics for a table, Oracle Database also automatically collects the statistics for each conventional and domain index of the table unless you specify the for_clause
.
When you analyze a table, the database collects statistics about expressions occurring in any function-based indexes as well. Therefore, be sure to create function-based indexes on the table before analyzing the table. Please refer to CREATE INDEX for more information about function-based indexes.
When analyzing a table, the database skips all domain indexes marked LOADING
or FAILED
.
For an index-organized table, the database also analyzes any mapping table and calculates its PCT_ACCESSS_DIRECT
statistics. These statistics estimate the accuracy of guess data block addresses stored as part of the local rowids in the mapping table.
Oracle Database collects the following statistics for a table. Statistics marked with an asterisk are always computed exactly. Table statistics, including the status of domain indexes, appear in the data dictionary views USER_TABLES
, ALL_TABLES
, and DBA_TABLES
in the columns shown in parentheses.
Number of rows (NUM_ROWS
)
* Number of data blocks below the high water mark--that is, the number of data blocks that have been formatted to receive data, regardless whether they currently contain data or are empty (BLOCKS
)
* Number of data blocks allocated to the table that have never been used (EMPTY_BLOCKS
)
Average available free space in each data block in bytes (AVG_SPACE
)
Number of chained rows (CHAIN_COUNT
)
Average row length, including the row overhead, in bytes (AVG_ROW_LEN
)
Restrictions on Analyzing Tables Analyzing tables is subject to the following restrictions:
You cannot use ANALYZE
to collect statistics on data dictionary tables.
You cannot use ANALYZE
to collect statistics on an external table. Instead, you must use the DBMS_STATS
package.
You cannot use ANALYZE
to collect default statistics on a temporary table. However, if you have already created an association between one or more columns of a temporary table and a user-defined statistics type, then you can use ANALYZE
to collect the user-defined statistics on the temporary table.
You cannot compute or estimate statistics for the following column types: REF
column types, varrays, nested tables, LOB column types (LOB column types are not analyzed, they are skipped), LONG
column types, or object types. However, if a statistics type is associated with such a column, then Oracle Database collects user-defined statistics.
See Also:
Oracle Database Reference for information on the data dictionary views
Specify the partition
or subpartition
on which you want statistics to be gathered. You cannot use this clause when analyzing clusters.
If you specify PARTITION
and table
is composite-partitioned, then Oracle Database analyzes all the subpartitions within the specified partition.
Specify an index to be analyzed.
Oracle Database collects the following statistics for an index. Statistics marked with an asterisk are always computed exactly. For conventional indexes, when you compute or estimate statistics, the statistics appear in the data dictionary views USER_INDEXES
, ALL_INDEXES
, and DBA_INDEXES
in the columns shown in parentheses.
* Depth of the index from its root block to its leaf blocks (BLEVEL
)
Number of leaf blocks (LEAF_BLOCKS
)
Number of distinct index values (DISTINCT_KEYS
)
Average number of leaf blocks for each index value (AVG_LEAF_BLOCKS_PER_KEY
)
Average number of data blocks for each index value (for an index on a table) (AVG_DATA_BLOCKS_PER_KEY
)
Clustering factor (how well ordered the rows are about the indexed values) (CLUSTERING_FACTOR
)
For domain indexes, this statement invokes the user-defined statistics collection function specified in the statistics type associated with the index (see ASSOCIATE STATISTICS). If no statistics type is associated with the domain index, then the statistics type associated with its indextype is used. If no statistics type exists for either the index or its indextype, then no user-defined statistics are collected. User-defined index statistics appear in the STATISTICS
column of the data dictionary views USER_USTATS
, ALL_USTATS
, and DBA_USTATS
.
Note:
When you analyze an index from which a substantial number of rows has been deleted, Oracle Database sometimes executes aCOMPUTE
statistics operation (which can entail a full table scan) even if you request an ESTIMATE
statistics operation. Such an operation can be quite time consuming.Restriction on Analyzing Indexes You cannot analyze a domain index that is marked IN_PROGRESS
or FAILED
.
See Also:
CREATE INDEX for more information on domain indexes
Oracle Database Reference for information on the data dictionary views
Specify a cluster to be analyzed. When you collect statistics for a cluster, Oracle Database also automatically collects the statistics for all the tables in the cluster and all their indexes, including the cluster index.
For both indexed and hash clusters, the database collects the average number of data blocks taken up by a single cluster key (AVG_BLOCKS_PER_KEY
). These statistics appear in the data dictionary views ALL_CLUSTERS
, USER_CLUSTERS
and DBA_CLUSTERS
.
See Also:
Oracle Database Reference for information on the data dictionary views and "Analyzing a Cluster: Example"Specify VALIDATE
REF
UPDATE
to validate the REF
values in the specified table, check the rowid portion in each REF
, compare it with the true rowid, and correct it, if necessary. You can use this clause only when analyzing a table.
If the owner of the table does not have SELECT
object privilege on the referenced objects, then Oracle Database will consider them invalid and set them to null. Subsequently these REF
values will not be available in a query, even if it is issued by a user with appropriate privileges on the objects.
SET DANGLING TO NULL SET
DANGLING
TO
NULL
sets to null any REF
values (whether or not scoped) in the specified table that are found to point to an invalid or nonexistent object.
Specify VALIDATE
STRUCTURE
to validate the structure of the analyzed object. The statistics collected by this clause are not used by the Oracle Database optimizer, as are statistics collected by the COMPUTE
STATISTICS
and ESTIMATE
STATISTICS
clauses.
See Also:
"Validating a Table: Example"For a table, Oracle Database verifies the integrity of each of the data blocks and rows. For an index-organized table, the database also generates compression statistics (optimal prefix compression count) for the primary key index on the table.
For a cluster, Oracle Database automatically validates the structure of the cluster tables.
For a partitioned table, Oracle Database also verifies that each row belongs to the correct partition. If a row does not collate correctly, then its rowid is inserted into the INVALID_ROWS
table.
For a temporary table, Oracle Database validates the structure of the table and its indexes during the current session.
For an index, Oracle Database verifies the integrity of each data block in the index and checks for block corruption. This clause does not confirm that each row in the table has an index entry or that each index entry points to a row in the table. You can perform these operations by validating the structure of the table with the CASCADE clause.
Oracle Database also computes compression statistics (optimal prefix compression count) for all normal indexes.
Oracle Database stores statistics about the index in the data dictionary views INDEX_STATS
and INDEX_HISTOGRAM
.
See Also:
Oracle Database Reference for information on these viewsIf Oracle Database encounters corruption in the structure of the object, then an error message is returned. In this case, drop and re-create the object.
INTO The INTO
clause of VALIDATE
STRUCTURE
is valid only for partitioned tables. Specify a table into which Oracle Database lists the rowids of the partitions whose rows do not collate correctly. If you omit schema
, then the database assumes the list is in your own schema. If you omit this clause altogether, then the database assumes that the table is named INVALID_ROWS
. The SQL script used to create this table is UTLVALID.SQL
.
CASCADE Specify CASCADE
if you want Oracle Database to validate the structure of the indexes associated with the table or cluster. If you use this clause when validating a table, then the database also validates the indexes defined on the table. If you use this clause when validating a cluster, then the database also validates all the cluster tables indexes, including the cluster index.
If you use this clause to validate an enabled (but previously disabled) function-based index, then validation errors may result. In this case, you must rebuild the index.
ONLINE | OFFLINE Specify ONLINE
to enable Oracle Database to run the validation while DML operations are ongoing within the object. The database reduces the amount of validation performed to allow for concurrency.
Note:
When you validate the structure of an objectONLINE
, Oracle Database does not collect any statistics, as it does when you validate the structure of the object OFFLINE
.Specify OFFLINE
, to maximize the amount of validation performed. This setting prevents INSERT
, UPDATE
, and DELETE
statements from concurrently accessing the object during validation but allows queries. This is the default.
Restriction on ONLINE You cannot specify ONLINE
when analyzing a cluster or index.
LIST
CHAINED
ROWS
lets you identify migrated and chained rows of the analyzed table or cluster. You cannot use this clause when analyzing an index.
In the INTO
clause, specify a table into which Oracle Database lists the migrated and chained rows. If you omit schema
, then the database assumes the chained-rows table is in your own schema. If you omit this clause altogether, then the database assumes that the table is named CHAINED_ROWS
. The chained-rows table must be on your local database.
You can create the CHAINED_ROWS
table using one of these scripts:
UTLCHAIN.SQL
uses physical rowids. Therefore it can accommodate rows from conventional tables but not from index-organized tables. (See the Note that follows.)
UTLCHN1.SQL
uses universal rowids, so it can accommodate rows from both conventional and index-organized tables.
If you create your own chained-rows table, then it must follow the format prescribed by one of these two scripts.
If you are analyzing index-organized tables based on primary keys (rather than universal rowids), then you must create a separate chained-rows table for each index-organized table to accommodate its primary-key storage. Use the SQL scripts DBMSIOTC.SQL
and PRVTIOTC.PLB
to define the BUILD_CHAIN_ROWS_TABLE
procedure, and then execute this procedure to create an IOT_CHAINED_ROWS
table for each such index-organized table.
See Also:
Oracle Database Upgrade Guide for compatibility issues related to the use of the UTL
* scripts
The DBMS_IOT
package in PL/SQL Packages and Types Reference for information on the packaged SQL scripts
Oracle Database Administrator's Guide for information on eliminating migrated and chained rows
Specify DELETE
STATISTICS
to delete any statistics about the analyzed object that are currently stored in the data dictionary. Use this statement when you no longer want Oracle Database to use the statistics.
When you use this clause on a table, the database also automatically removes statistics for all the indexes defined on the table. When you use this clause on a cluster, the database also automatically removes statistics for all the cluster tables and all their indexes, including the cluster index.
Specify SYSTEM
if you want Oracle Database to delete only system (not user-defined) statistics. If you omit SYSTEM
, and if user-defined column or index statistics were collected for an object, then the database also removes the user-defined statistics by invoking the statistics deletion function specified in the statistics type that was used to collect the statistics.
See Also:
"Deleting Statistics: Example"This clause is supported for backward compatibility only. Please refer to the note in "Purpose".
COMPUTE
STATISTICS
instructs Oracle Database to compute exact statistics about the analyzed object and store them in the data dictionary. When you analyze a table, both table and column statistics are collected.
Both computed and estimated statistics are used by the Oracle Database optimizer to choose the execution plan for SQL statements that access analyzed objects. These statistics may also be useful to application developers who write such statements.
Specify SYSTEM
if you want Oracle Database to compute only system (not user-defined) statistics. If you omit SYSTEM
, then the database collects both system-generated statistics and statistics generated by the collection functions declared in a statistics type.
See Also:
Oracle Data Cartridge Developer's Guide for information on creating statistics collection functions
Oracle Database Performance Tuning Guide for information on how these statistics are used
The for_clause
lets you specify whether an entire table or index, or just particular columns, will be analyzed. The following clauses apply only to the ANALYZE
TABLE
version of this statement.
FOR TABLE Specify FOR
TABLE
to restrict the statistics collected to only table statistics rather than table and column statistics.
FOR COLUMNS Specify FOR
COLUMNS
to restrict the statistics collected to only column statistics for the specified columns and scalar object attributes, rather than for all columns and attributes. For attribute
, specify the qualified column name of an item in an object.
FOR ALL COLUMNS Specify FOR
ALL
COLUMNS
to collect column statistics for all columns and scalar object attributes.
FOR ALL INDEXED COLUMNS Specify FOR
ALL
INDEXED
COLUMNS
to collect column statistics for all indexed columns in the table. Column statistics can be based on the entire column or can use a histogram by specifying SIZE.
Oracle Database collects the following column statistics:
Number of distinct values in the column as a whole
Maximum and minimum values in each band
See Also:
Oracle Database Performance Tuning Guide for more information on histogramsColumn statistics appear in the data dictionary views USER_TAB_COLUMNS
, ALL_TAB_COLUMNS
, and DBA_TAB_COLUMNS
. Histograms appear in the data dictionary views USER_TAB_HISTOGRAMS
, DBA_TAB_HISTOGRAMS
, and ALL_TAB_HISTOGRAMS
; USER_PART_HISTOGRAMS
, DBA_PART_HISTOGRAMS
, and ALL_PART_HISTOGRAMS
; and USER_SUBPART_HISTOGRAMS
, DBA_SUBPART_HISTOGRAMS
, and ALL_SUBPART_HISTOGRAMS
.
Note:
TheMAXVALUE
and MINVALUE
columns of USER_
, DBA_
, and ALL_TAB_COLUMNS
have a length of 32 bytes. If you analyze columns with a length >32 bytes, and if the columns are padded with leading blanks, then Oracle Database may take into account only the leading blanks and return unexpected statistics.If a user-defined statistics type has been associated with any columns, then the for_clause
collects user-defined statistics using that statistics type. If no statistics type is associated with a column, then Oracle Database checks to see if any statistics type has been associated with the type of the column, and uses that statistics type. If no statistics type has been associated with either the column or its user-defined type, then no user-defined statistics are collected. User-defined column statistics appear in the STATISTICS
column of the data dictionary views USER_USTATS
, ALL_USTATS
, and DBA_USTATS
.
If you want to collect statistics on both the table as a whole and on one or more columns, then be sure to generate the statistics for the table first, and then for the columns. Otherwise, the table-only ANALYZE
will overwrite the histograms generated by the column ANALYZE
. For example, issue the following statements:
ANALYZE TABLE emp ESTIMATE STATISTICS; ANALYZE TABLE emp ESTIMATE STATISTICS FOR ALL COLUMNS;
FOR ALL INDEXES Specify FOR
ALL
INDEXES
if you want all indexes associated with the table to be analyzed.
FOR ALL LOCAL INDEXES Specify FOR
ALL
LOCAL
INDEXES
if you want all local index partitions to be analyzed. You must specify the keyword LOCAL
if the PARTITION
clause and INDEX
are specified.
SIZE Specify the maximum number of buckets in the histogram. The default value is 75, minimum value is 1, and maximum value is 254.
Oracle Database does not create a histogram with more buckets than the number of rows in the sample. Also, if the sample contains any values that are very repetitious, then Oracle Database creates the specified number of buckets, but the value indicated by the NUM_BUCKETS
column of the ALL_
, DBA_
, and USER_TAB_COLUMNS
views may be smaller because of an internal compression algorithm.
This clause is supported for backward compatibility only. Please refer to the note in "Purpose".
ESTIMATE
STATISTICS
instructs Oracle Database to estimate statistics about the analyzed object and store them in the data dictionary.
Both computed and estimated statistics are used by the Oracle Database optimizer to choose the execution plan for SQL statements that access analyzed objects. These statistics may also be useful to application developers who write such statements.
Specify SYSTEM
if you want Oracle Database to estimate only system (not user-defined) statistics. If you omit SYSTEM
, then the database estimates both system-generated statistics and statistics generated by the collection functions declared in a statistics type.
See Also:
Oracle Data Cartridge Developer's Guide for information on creating statistics collection functionsfor_clause Please refer to the description under compute_statistics_clause .
SAMPLE Specify the amount of data from the analyzed object Oracle Database should sample to estimate statistics. If you omit this parameter, then the database samples 1064 rows.
The default sample value is adequate for tables up to a few thousand rows. If your tables are larger, then specify a higher value for SAMPLE
. If you specify more than half of the data, then the database reads all the data and computes the statistics.
When you analyze an index from which a substantial number of rows has been deleted, Oracle Database sometimes executes a COMPUTE
statistics operation (which can entail a full table scan) even if you request an ESTIMATE
statistics operation. Such an operation can be quite time consuming.
ROWS
causes Oracle Database to sample integer
rows of the table or cluster or integer
entries from the index. The integer must be at least 1.
PERCENT
causes Oracle Database to sample integer
percent of the rows from the table or cluster or integer
percent of the index entries. The integer can range from 1 to 99.
See Also:
Oracle Database Performance Tuning Guide for information on how these statistics are usedvalidation_clauses
The validation clauses let you validate REF
values and the structure of the analyzed object.
Examples
Deleting Statistics: Example The following statement deletes statistics about the sample table oe.orders
and all its indexes from the data dictionary:
ANALYZE TABLE orders DELETE STATISTICS;
Analyzing an Index: Example The following statement validates the structure of the sample index oe.inv_product_ix
:
ANALYZE INDEX inv_product_ix VALIDATE STRUCTURE;
Validating a Table: Example The following statement analyzes the sample table hr.employees
and all of its indexes:
ANALYZE TABLE employees VALIDATE STRUCTURE CASCADE;
For a table, the VALIDATE
REF
UPDATE
clause verifies the REF
values in the specified table, checks the rowid portion of each REF
, and then compares it with the true rowid. If the result is an incorrect rowid, then the REF
is updated so that the rowid portion is correct.
The following statement validates the REF
values in the sample table oe.customers
:
ANALYZE TABLE customers VALIDATE REF UPDATE;
The following statement validates the structure of the sample table oe.customers
while allowing simultaneous DML:
ANALYZE TABLE customers VALIDATE STRUCTURE ONLINE;
Analyzing a Cluster: Example The following statement analyzes the personnel
cluster (created in "Creating a Cluster: Example"), all of its tables, and all of their indexes, including the cluster index:
ANALYZE CLUSTER personnel VALIDATE STRUCTURE CASCADE;
Listing Chained Rows: Example The following statement collects information about all the chained rows in the table orders
:
ANALYZE TABLE orders LIST CHAINED ROWS INTO chained_rows;
The preceding statement places the information into the table chained_rows
. You can then examine the rows with this query (no rows will be returned if the table contains no chained rows):
SELECT owner_name, table_name, head_rowid, analyze_timestamp FROM chained_rows; OWNER_NAME TABLE_NAME HEAD_ROWID ANALYZE_TIMESTAMP ---------- ---------- ------------------ ----------------- OE ORDERS AAAAZzAABAAABrXAAA 25-SEP-2000