SQL/MX 2.x Reference Manual (H06.04+)

SQL/MX Utilities
HP NonStop SQL/MX Reference Manual—540440-003
5-57
Manage System-Clustered Tables
EXTENT { ext-size }
{ (pri-ext-size, sec-ext-size) }
ext-size is an unsigned integer value. You can specify it as the size for both
primary and secondary extents of the new partition. You can specify the size of
the primary extent and secondary extents separately. If you do not specify
EXTENT, MODIFY uses the largest extent size possible using the combination
of primary, secondary and max extent values.
See EXTENT on page 8-6 and MAXEXTENTS on page 8-7.
When you add a hash partition, a subset of data from existing partitions is
redistributed to the new partition.
Manage System-Clustered Tables
A system-clustered table has no primary key and no STORE BY clause. Its primary
key defaults to the SYSKEY.
You can use MODIFY to move the existing partition of a system-clustered object to a
new location. Note that a system-clustered table can have only a single partition. Only
offline partition operations are supported.
[[catalog.]schema.]table
is the name of the system-clustered table. If you do not specify the schema and
catalog name, NonStop SQL/MX uses the current default catalog and schema of
your MXCI session.
[\node.]$volume[.subvolume.file-name]
is a disk volume or a Guardian file for the new partition. If you use disk volume
syntax, MODIFY generates the file name. \node can be either the local node or a
remote node. If you do not specify \node, the default is the Guardian system
named in your =_DEFAULTS define.
partition-size
is the size of the new partition.
partition-extent-size [ MAXEXTENTS num-extents ]
is the size of the new partition. You can specify the sizes of the primary extent and
secondary extents of the partition, and you can specify the maximum number of
The form of MODIFY for system-clustered objects is:
MODIFY TABLE [[catalog.]schema.]table
MOVE [PARTITION]
[TO] LOCATION [\node.]$volume[.subvolume.file-name]
[partition-size]