SQL/MX 2.x Installation and Management Guide (G06.24+, H06.03+)

Reorganizing SQL/MX Tables and Maintaining Data
HP NonStop SQL/MX Installation and Management Guide523723-004
10-10
MODIFY and EMS Messages
Adding, splitting, merging, moving, and dropping partitions for range-partitioned
tables and indexes. See Using MODIFY to Manage Range-Partitioned Tables and
Indexes on page 10-14.
Adding, moving, and dropping partitions for hash-partitioned tables and indexes.
See Using MODIFY to Manage Hash-Partitioned Tables and Indexes on
page 10-18.
Managing system-clustered tables and indexes. See Managing System-Clustered
Tables and Indexes on page 10-21.
For more information about the MODIFY utility, see the SQL/MX Reference Manual.
MODIFY and EMS Messages
MODIFY generates EMS messages to report operation status. If an error occurs during
a MODIFY operation, check the EMS log for possible information about where the
process failure occurred.
Online and Offline Partition Management
MODIFY can run as either an offline or online operation. You can perform online
operations while the partition is being used by another application. You can perform
offline operations only on partitions that are not being used by other applications or that
are being used with READ access. WRITE access is prohibited.
MODIFY’s with-shared-access option supports online partition management of
range-partitioned tables and indexes in which the partitioning key is a prefix of the
clustering key. This feature provides full read and write access to a range-partitioned
table or index for the duration of most operations. Other processes can read and write
the table or index while it is being repartitioned, except during a short period at the end
when file labels and metadata are updated.
Online partition management is not supported for these types of tables and indexes:
Hash partitioned tables and indexes
System-clustered tables
Range partitioned tables and indexes where the partitioning key is not a prefix of
the clustering key
MODIFY and TMF
Many partition management requests require movement of massive amounts of data.
Because these operations can take longer than the default TMF time limit of two hours,
operations involving data movement are performed in multiple transactions.