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

SQL/MX Statements
HP NonStop SQL/MX Release 3.2.1 Reference Manual—691117-005
2-9
Utilities
Privileges Required to Execute Utilities
Checking DDL Locks
Many utilities, for example, DUP, MODIFY, and POPULATE INDEX, lock both metadata
and user data during the operation. The following are three kinds of locks:
°
Transactional locks on metadata and user data rows
A utility runs in multiple TMF transactions, managed by the utility itself. If the
utility fails before completion, then TMF will back out the latest of those
transactions and then release the lock.
°
Non-transactional file locks on user data
Some utilities must hold shared locks on user data outside TMF transactions,
to prevent concurrent updates while the utility is reading the data. If the utility
operation fails before completion, such locks are automatically released.
°
Logical DDL Locks on metadata
Most utilities require that the definition of the object being worked on remains
stable for the duration of the utility operation. To ensure this, the utility inserts a
so-called 'DDL Lock' into metadata, which prevents other DDL and utility
operations from changing the definition of the object. If the utility operation fails
before completion, the DDL Lock remains intact.
If a utility operation fails before completion, you must recover the following using the
RECOVER utility:
°
Work done in TMF transactions that are internally committed by the utility.
Utility Privileges Required
DOWNGRADE Super ID.
DUP SELECT privilege on the source table.
Be the owner of the schema where the target table resides.
FASTCOPY SELECT privilege on the source table.
SELECT, INSERT, UPDATE and DELETE privilege on the target
table.
MODIFY Schema owner or object owner or super ID.
POPULATE INDEX Have ALL privileges.
PURGEDATA Have ALL privileges.
RECOVER Have the corresponding utility privileges for the utility to be
recovered.
RECOVER SCHEMA Schema owner or the security administrator.
UPGRADE Super ID.