|Oracle® Database SQL Language Reference
11g Release 2 (11.2)
|PDF · Mobi · ePub|
physical_attributes_clause lets you specify the value of the
INITRANS parameters and the storage characteristics of a table, cluster, index, or materialized view.
You can specify the
physical_attributes_clause in the following statements:
TABLE: to set the physical attributes of the table, a table partition, the
OIDINDEX of an object table, or the overflow segment of an index-organized table (see CREATE TABLE).
TABLE: to change the physical attributes of the table, the default physical attributes of future table partitions, or the physical attributes of existing table partitions (see ALTER TABLE). The following restrictions apply:
You cannot specify physical attributes for a temporary table.
You cannot specify physical attributes for a clustered table. Tables in a cluster inherit the physical attributes of the cluster.
INDEX: to set the physical attributes of an index or index partition (see CREATE INDEX).
INDEX: to change the physical attributes of the index, the default physical attributes of future index partitions, or the physical attributes of existing index partitions (see ALTER INDEX).
VIEW: to set the physical attributes of the materialized view, one of its partitions, or the index Oracle Database generates to maintain the materialized view (see CREATE MATERIALIZED VIEW).
VIEW: to change the physical attributes of the materialized view, the default physical attributes of future partitions, the physical attributes of an existing partition, or the index Oracle creates to maintain the materialized view (see ALTER MATERIALIZED VIEW).
This section describes the parameters of the
physical_attributes_clause. For additional information, refer to the SQL statement in which you set or reset these parameters for a particular database object.
Specify a whole number representing the percentage of space in each data block of the database object reserved for future updates to rows of the object. The value of
PCTFREE must be a value from 0 to 99. A value of 0 means that the entire block can be filled by inserts of new rows. The default value is 10. This value reserves 10% of each block for updates to existing rows and allows inserts of new rows to fill a maximum of 90% of each block.
PCTFREE has the same function in the statements that create and alter tables, partitions, clusters, indexes, materialized views, and materialized view logs. The combination of
PCTUSED determines whether new rows will be inserted into existing data blocks or into new blocks. See "How PCTFREE and PCTUSED Work Together".
Specify a whole number representing the minimum percentage of used space that Oracle maintains for each data block of the database object.
PCTUSED is specified as a positive integer from 0 to 99 and defaults to 40.
PCTUSED has the same function in the statements that create and alter tables, partitions, clusters, materialized views, and materialized view logs.
PCTUSED is not a valid table storage characteristic for an index-organized table.
The sum of
PCTUSED must be equal to or less than 100. You can use
PCTUSED together to utilize space within a database object more efficiently. See "How PCTFREE and PCTUSED Work Together".
You cannot specify this parameter for an index or for the index segment of an index-organized table.
This parameter is not useful and is ignored for objects with automatic segment-space management.
See Also:Oracle Database Performance Tuning Guide for information on the performance effects of different values of
TABLESPACEsegment_management_clause for information on automatic segment-space management
In a newly allocated data block, the space available for inserts is the block size minus the sum of the block overhead and free space (
PCTFREE). Updates to existing data can use any available space in the block. Therefore, updates can reduce the available space of a block to less than
After a data block is filled to the limit determined by
PCTFREE, Oracle Database considers the block unavailable for the insertion of new rows until the percentage of that block falls beneath the parameter
PCTUSED. Until this value is achieved, Oracle Database uses the free space of the data block only for updates to rows already contained in the data block. A block becomes a candidate for row insertion when its used space falls below
See Also:FREELISTS for information on how
PCTFREEwork with freelist segment space management
Specify the initial number of concurrent transaction entries allocated within each data block allocated to the database object. This value can range from 1 to 255 and defaults to 1, with the following exceptions:
INITRANS value for a cluster is 2 or the default
INITRANS value of the tablespace in which the cluster resides, whichever is greater.
The default value for an index is 2.
In general, you should not change the
INITRANS value from its default.
Each transaction that updates a block requires a transaction entry in the block. This parameter ensures that a minimum number of concurrent transactions can update the block and helps avoid the overhead of dynamically allocating a transaction entry.
INITRANS parameter serves the same purpose in the statements that create and alter tables, partitions, clusters, indexes, materialized views, and materialized view logs.
In earlier releases, the
MAXTRANS parameter determined the maximum number of concurrent update transactions allowed for each data block in the segment. This parameter has been deprecated. Oracle now automatically allows up to 255 concurrent update transactions for any data block, depending on the available space in the block.
Existing objects for which a value of
MAXTRANS has already been set retain that setting. However, if you attempt to change the value for
MAXTRANS, Oracle ignores the new specification and substitutes the value 255 without returning an error.
storage_clause lets you specify storage characteristics for the table, object table
OIDINDEX, partition, LOB data segment, or index-organized table overflow data segment. This clause has performance ramifications for large tables. Storage should be allocated to minimize dynamic allocation of additional space. Refer to the storage_clause for more information.