NonStop SQL/MP Reference Manual

NonStop SQL/MP Reference Manual—142115
C-66
Considerations—CONTINUE
operation-name
is the name of the operation to continue, as specified by the NAME option in the
DDL statement that started the operation.
If you did not specify the NAME option, operation_name is based on the type
of statement that started the operation (ALTER_TABLE, CREATE_INDEX, and so
forth).
{ COMMIT [WORK] options }
{ ROLLBACK [WORK] }
is a commit option that controls the start time for the final phase of the operation and
specifies the timeout period for lock requests and the handling of retryable errors
during the commit phase of the operation. The commit option can also direct SQL to
cancel changes made by the operation and terminate the operation.
See COMMIT Option
on page C-46 for more information.
Considerations—CONTINUE
•
CONTINUE not allowed in TMF transactions
You cannot execute the CONTINUE statement within a user-defined transaction. If
you attempt to do so, SQL terminates the operation in effect and rolls back the
transaction, canceling all changes made to the database by either the operation or the
transaction.
•
Actions allowed between warning 1619 and CONTINUE
A host language or SQLCI process that receives warning 1619 must respond with a
CONTINUE statement before terminating or taking any action that directly or
indirectly modifies a DEFINE. However, the process can execute other SQL
statements or SQLCI commands prior to executing a CONTINUE statement, except
for DDL statements or write-access utility operations on source or target objects of
the operation in progress.
If the process terminates or modifies a DEFINE prior to executing a CONTINUE
statement, the DDL operation in progress stops without being either committed or
canceled. The changes are not made (as they would be if the operation was
committed) and new SQL objects created by the operation are not removed (as they
would be if the operation was canceled).
If this scenario occurs, you must use CLEANUP to remove the new SQL objects (or
ask another user with access to the super ID to do so). If the operation was a
CREATE INDEX operation on a table with the AUDITCOMPRESS file attribute,
you might need to use ALTER TABLE to reset AUDITCOMPRESS.
An SQLCI process that uses a terminal as an IN file protects you from this situation
by not allowing any of the following commands (which terminate the SQLCI