SQL/MX 3.2.1 Management Manual (H06.26+, J06.15+)

FUP
- RELOAD $DATA08.ZSDAWVHH.J8MGRZ00, RATE 20, SLACK 50
If you want to keep the same RATE and SLACK values when you restart the reorganization process,
enter the FUP RELOAD command without the RATE and SLACK parameters:
FUP
- RELOAD $DATA08.ZSDAWVHH.J8MGRZ00
After a FUP RELOAD operation has been suspended and you want to start this operation completely
over again, enter the FUP RELOAD command with the NEW option:
FUP
- RELOAD $DATA08.ZSDAWVHH.J8MGRZ00, NEW, RATE 30, SLACK 50
In the FUP RELOAD command, the NEW option is necessary only when restarting a RELOAD
operation over again from the beginning, following a RELOAD suspension.
DDL Lock Considerations for MODIFY, import, POPULATE INDEX, DUP,
FASTCOPY, and PURGEDATA
A utility operation usually occurs over several TMF transactions, time during which other operations
might attempt to run. However, operations that change metadata and label information for the
same table or index, including DDL requests and other utility operations, are considered structure
changing operations. To prevent other structure changing operations from running before it
completes, a running utility obtains and holds a DDL lock for the duration of its execution.
The DDL lock persists across the boundaries of the TMF transactions that compose the utility
operation. The DDL lock signifies that a structure change is in progress for a given table or one of
its indexes. Other structure changing operations cannot be performed until the operation that holds
the DDL lock completes. DDL locks are usually obtained for utilities that run in multiple operations
and therefore require compensating work to recover the utility operations.
The utility request informs NonStop SQL/MX that it is running, performs commands over as many
TMF transactions as necessary, then informs NonStop SQL/MX that the operation has completed.
Structure changing operations include:
• A DDL operation that changes the definition of the object (for example, alter table, add column,
or create index)
• A DDL operation on a dependent object (for example, an index, constraint, or trigger)
• A utility operation that changes the definition of the object.
These SQL/MX utilities use DDL locks:
• MODIFY. See “Using MODIFY to Manage Table and Index Partitions” (page 184).
• import (for the fast loading option only). See “Using import to Load SQL/MX Tables”
(page 194).
• POPULATE INDEX
• DUP. See “Using DUP to Copy Tables Into Tables” (page 207).
• FASTCOPY. See “Using FASTCOPY to Copy Tables into Tables” (page 208).
• PURGEDATA. See “Using PURGEDATA to Delete Data From Tables” (page 210).
A DDL lock is obtained when any of these utilities starts. When the utility operation completes, the
DDL lock is removed. While the DDL lock exists, other structure changing operations cannot be
run.
A utility that holds a DDL lock can terminate without removing the DDL lock. For example, suppose
that a resource on which a utility operation is running becomes unavailable, causing the MXCMP
process and the utility to fail. Because the DDL lock is persistent, it still exists after the operation
fails as an inactive DDL lock. If a utility operation fails and an inactive DDL lock is present, you
DDL Lock Considerations for MODIFY, import, POPULATE INDEX, DUP, FASTCOPY, and PURGEDATA 181