SQL/MX 2.x Messages Manual (G06.24+, H06.03+)

Utility Messages (20000 through 23099)
HP NonStop SQL/MX Messages Manual—523730-004
17-91
Recovery. If the timestamp check failed at the beginning of the commit phase,
perform a RECOVER command to undo partial processing. Then, retry the MODIFY
operation with a timestamp sufficiently in the future.
SQL 20732
Cause. The MODIFY command includes a COMMIT AFTER timestamp clause, and
the timestamp specifies a time that is more than 30 days in the future.
Effect. The MODIFY operation fails.
Recovery. Correct the COMMIT AFTER clause to use a time within 30 days of the
present, and resubmit.
SQL 20734
Where error number is the returned file system number.
Cause. When processing COMMIT BEFORE or COMMIT AFTER clauses, the
MODIFY command encountered an error number from the CONVERTTIMESTAMP
Guardian procedure when converting the current time to local civil time.
Effect. The MODIFY operation fails.
Recovery. See the Guardian Procedure Calls Reference Manual topic
CONVERTTIMESTAMP Procedure for the meaning of error number and possible
recovery actions.
SQL 20751
Cause. A TMF transaction is currently active. The VERIFY process does not allow
active transactions.
Effect. The operation fails.
Recovery. Commit or terminate the current transaction and resubmit.
20732 The time given in the AFTER clause is more than 30 days
in the future.
20734 Error error number was returned by CONVERTTIMESTAMP
while trying to obtain local civil time.
20751 A user-defined transaction has been started. VERIFY
cannot be performed.