SQL/MX 2.x Installation and Management Guide (H06.04+)

Reorganizing SQL/MX Tables and Maintaining Data
HP NonStop SQL/MX Installation and Management Guide—540436-001
10-12
MODIFY and Table Reloading
on target rows. Avoid choosing a default value greater than 500, because DP2
escalates locking from selected rows to the entire partition if the partition has more
than 511 row and file locks.
MODIFY and Table Reloading
Some MODIFY command options start the online reload process ORSERV, which runs
in the background. Until the ORSERV process completes, you cannot perform DDL
operations and utility operations—including another MODIFY command—on the
affected table or index. ORSERV keeps the file open and does not terminate for five
minutes after the reload operation completes.
For range-partitioned tables and indexes, the MODIFY command starts one or more
ORSERV processes when:
•
You specify an offline ADD request (that is, a prefix of a suffix split operation), and
the specified key range contains data.
•
You specify an online ADD request using the WITH SHARED ACCESS clause.
•
You specify a MOVE request for a move-partition-boundary operation, and the
specified key range contains data but does not include the entire partition.
•
You use the WITH SHARED ACCESS clause to specify an online MOVE request
for a move-partition-boundary operation, and the specified key range does not
include the entire partition.
For hash-partitioned tables and indexes, the MODIFY command starts one or more
ORSERV processes when:
•
You specify an ADD request.
•
You specify a DROP request.
For information about MODIFY command syntax, see the SQL/MX Reference Manual.
MODIFY assigns these default values of the FUP RELOAD parameters to ORSERV:
FUP RELOAD Parameter Default Value
DEALLOCATE No
NEW True
RATE (percentage) 100
DSLACK (percentage) 15
ISLACK (percentage) 15
SHARE False
SLACK (percentage) 15
RECLAIM for range partition True
RECLAIM for hash partition False