Identifies the schema that will qualify the table name.
If omitted, the current session associated with the user session schema is used. Schema-name is required if there is no current session schema.
Identifies the table that is constrained by an indexed constraint.
Identifies constraints and indexes on the current table that is being tuned.
If omitted, all indexed constraints and indexes on the current table are processed.
Identifies an sql-defined area to be selected for processing.
All tables with indexed constraints in the area are processed.
Identifies the dbname to be used when binding the subschema.
Identifies the subschema to be used for processing a non-SQL database.
Identifies the indexed sets within the subschema that are to be processed.
If omitted, all linked indexed sets defined in the subschema are processed. (Linked indexed sets are indexed sets with index pointers.)
Specifies the commit interval. After every cmt-interval record read, a commit is issued. If omitted, the default interval is 100. If specified as zero (0), no commits are issued.
Specifies the length of the notify interval in minutes. After each interval expires, a message is issued stating how far the job has progressed. If the notify interval is specified as 0 or allowed to default to 0, no notify messages are created.
Identifies an indexed constraint on the current table that is to be tuned.
Identifies an index on the current table that is to be tuned.
The tune options to be used during the processing of an index if tune options have not been specifically specified.
Specifies whether to rebalance the index. A well-balanced index has the minimum number of index levels and best performance if the index is frequently accessed vertically from top to bottom.
Rebalances the index.
Note: Rebalancing an index can be resource-intensive.
No rebalancing is done.
Specifies whether to resequence the index. A properly sequenced index is important only if the index is frequently accessed sequentially at the bottom level.
Resequences the index for optimum performance.
Note: Resequencing an index can be resource-intensive.
No resequencing is done.
Specifies a temporary override for the operation. If not specified, the current run-time value for INDEX BLOCK CONTAINS is used and index blocks are used at 100%.
Specifies the percentage of the maximum number of entries that each index block should contain after tuning is complete. ixutil-pct is an integer in the range 10 through 100. The number of entries of an index block is computed as index-block-contains * ixutil-pct / 100.
Specifies the maximum number of entries that each index block should contain after tuning is complete. key-count is an integer in the range 3 through 8180.
Note: If the specified value exceeds the current run-time value of the INDEX BLOCK CONTAINS, the key-count value is ignored and the INDEX BLOCK CONTAINS value will be used.
Specifies a temporary override of the page reserve for the area in which the index resides. If not specified or specified as NULL, the page reserve of the area in which the index resides is used.
Specifies the percentage of each page to leave as free space if it contains a portion of an index being tuned. page-reserve-pct is an integer in the range 0 through 30. The page reserve of the area is computed as area-page-size * page-reserve-pct / 100.
Specifies the number of characters to reserve on each page to accommodate increases in the length of records or rows stored on the page if it contains a portion of an index being tuned. reserve-character-count is an integer with a value not larger than 30% of the page size.
|
Copyright © 2014 CA.
All rights reserved.
|
|