SQL/MX 2.x Reference Manual (G06.24+, H06.03+)

SQL/MX Utilities
HP NonStop SQL/MX Reference Manual—523725-004
5-53
Manage System-Clustered Tables
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
extents the partition can have. If you do not specify MAXEXTENTS, MODIFY uses
the value of the primary partition.
partition-extent-size
is the extent size of the new partition
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]