HP NonStop SQL/MX Messages Manual page 293

Table of Contents

Advertisement

Executor Messages (8000 through 8999)
SQL 8873
8873 The current statement is already associated with a QFO.
Cause. An existing quasi file object (QFO) is already associated with the current
statement.
Effect. The operation fails.
Recovery. None. Contact your service provider.
SQL 8874
8874 An error in an insert, update or delete statement caused
that statement to be rolled back but statement rollback
failed.
Cause. DP2 limits on savepoints is exceeded.
Effect. The operation fails.
Recovery. None.
SQL 8877
8877 A transaction is needed to run this query, one is not
already started, and the automatic starting of transactions
has been disabled.
Cause. A statement was run that requires a transaction. There is no existing
transaction and the transaction attribute AUTOBEGIN is set to OFF.
Effect. The statement fails to run.
Recovery. Either start a transaction or set transaction attribute AUTOBEGIN to ON
and rerun the statement.
SQL 8878
8878 Transaction has been doomed. The user should explicitly
roll back the transaction before proceeding.
Cause. The CONTROL QUERY DEFAULT value for DOOM_USERTRANSACTION is
ON, and NonStop SQL/MX encountered an unrecoverable error.
Effect. The transaction is in a doomed state. Users are unable to continue work on
this transaction.
Recovery. Use the ROLLBACK WORK statement to undo the transaction explicitly.
HP NonStop SQL/MX Messages Manual—640324-001
10 -45

Hide quick links:

Advertisement

Table of Contents
loading

This manual is also suitable for:

Nonstop sql/mx 3.0

Table of Contents