SQL/MP Messages Manual

SQLCI Utility Processor Messages (9000 to 9999)
HP NonStop SQL/MP Messages Manual—427720-006
11-55
(APPEND will accept a recovery file that exists, but is incomplete — it will write fresh
recovery information to the recovery file.)
SQL 9181
Cause. You entered an APPEND command that specifies a recovery file that already
exists, indicating that an APPEND was already in progress and had been interrupted.
An APPEND command can only start an APPEND operation; it cannot restart one, so it
will not use an existing recovery file. One exception: If the information in the recovery
file is incomplete, as when an initial APPEND is interrupted before it finishes setting up
the recovery file, APPEND will accept that recovery file and write fresh recovery
information to it.
Effect. The command fails. The target is not modified.
Recovery. If you are trying to restart an APPEND that had been interrupted, use the
APPENDRESTART command.
SQL 9182
Cause. You may have misspelled the recovery file name, or you may have tried to
cancel an APPEND that had completed. If neither of those are the case, you entered
an APPENDCANCEL command to cancel an APPEND that had been interrupted, but
the original APPEND command was interrupted before it created the recovery file or
before it had finished writing the recovery information to the file.
Effect. The command fails. The target is not modified.
Recovery. If the original APPEND had completed, no recovery is needed. If the
problem was incorrect spelling of the recovery file name, correct the spelling and retry
the command. Otherwise, if you are sure this is a case of the recovery file being
incomplete, just purge the recovery file.
9181 The recovery file specified in the APPEND already exists
and contains recovery data.
9182 The recovery file specified in the APPENDCANCEL command
does not exist or does not contain complete recovery data.