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 Guide—523723-004
10-8
Structure Changing Operations That Can Run With
Active or Inactive DDL Locks Present
and perform a FUP RELOAD operation if the MODIFY request completes but its
ORSERV process does not complete and is not running. At the very least, a process
with the same process ID stored in the metadata exists. For more information about
recovering a failed MODIFY request, see Recovering a Failed MODIFY Request and
Resetting Flags on page 10-13. For RECOVER command syntax, see the SQL/MX
Reference Manual.
If a structure changing operation is attempted while an active or inactive DDL lock is
present, error 1134 is returned:
For more information about this error message, see the SQL/MX Messages Manual.
If the DDL lock is active, you must wait until the utility operation completes before you
can re-run the original request. If the DDL lock is inactive, you must perform a
RECOVER operation against the table or index name specified in the 1134 error. If you
attempt to perform a RECOVER operation while the utility operation is still running, the
RECOVER operation fails. Otherwise, RECOVER completes and removes the inactive
DDL lock.
If the RECOVER operation fails, you must identify and correct the cause for its failure.
For example, RECOVER might fail because of the unavailability of a system that
contains a partition from the table or index being acted on. You would have to wait until
the remote system is available before you could re-run RECOVER to cancel or resume
the operation.
When the RECOVER operation has completed successfully, you can perform the other
structure changing operations.
If you attempt to drop or alter an object that a utility operation is using, error 1250 is
returned:
For more information about the error message, see the SQL/MX Messages Manual.
Structure Changing Operations That Can Run With Active or
Inactive DDL Locks Present
Structure changing operations are sometimes allowed to run even with active or
inactive DDL locks present. Examples include:
•
Creating a view on a table with an active or inactive DDL lock
•
Dropping a view on table with an active or inactive DDL lock
1134 A concurrent utility or DDL operation is being performed
on object object-name, its parent, or one of its
dependencies. That operation must complete before the
requested operation can run.
1250 Operation cannot be performed on object object-name
because a utility operation (operation-type) associated with
DDL_LOCK lock-name is currently running.