SQL/MP Installation and Management Guide

Reorganizing Tables and Maintaining Data
HP NonStop SQL/MP Installation and Management Guide—523353-004
8-5
Reorganizing Partitions
If you want to change the RATE or SLACK option, you can do so in the restart
command. This command restarts the RELOAD operation for the table CUSTOMER,
but adjusts the reloading rate to 20 percent:
17> FUP
- RELOAD $VOL.SALES.CUSTOMER, RATE 20, SLACK 50
If you want to keep the same RATE and SLACK values when you restart the
reorganization process, enter the RELOAD command without the RATE and SLACK
parameters:
18> FUP
- RELOAD $VOL.SALES.CUSTOMER
After a RELOAD operation has been suspended and you want to start this operation
completely over again, enter the RELOAD command with the NEW option:
19> FUP
- RELOAD $VOL.SALES.CUSTOMER, NEW, RATE 30, SLACK 50
In the RELOAD command, the NEW option is necessary only when restarting a
RELOAD operation over again from the beginning, following a RELOAD suspension.
Reorganizing Partitions
As table partitions become full, you can reorganize the structure of a table or index by
adding, splitting, or dropping a partition, redefining the row boundaries of a partition,
changing file extent values, adding empty partitions, or creating and loading a new
table.
For many of these operations, you can specify the WITH SHARED ACCESS option to
retain full read and write access to data throughout most of the operation. Thus, many
of these operations can be performed almost entirely online. (Some operations require
the WITH SHARED ACCESS option.)
Before requesting these operations, carefully examine your situation and the desired
effect of the operation. For specific information about each of these operations, see
Section 7, Adding, Altering, Removing, and Renaming Database Objects.
Balancing Partition Sizes
When a partition of a table or index becomes full, you can split the partition to make
room for additional insert and update operations. Suppose, for example, that a table
has three partitions based on the CUSTNUM key. The table is partitioned according to
the customer number (CUSTNUM) ranges 1 through 2999, 3000 through 5999, and
6000 through 99999, respectively.
Eventually, the last partition becomes full because most new customers are assigned a
customer number in the higher ranges of the table (over 6000), adding records to the
last partition at a higher rate than the other two stable partitions. In this case, you
should split the last partition into two new partitions, one with customer numbers 6000