HP NonStop SQL/MX Messages Manual page 285

Table of Contents

Advertisement

Executor Messages (8000 through 8999)
SQL 8838
8838 Unable to receive reply from MXCMP, possibly caused by
internal errors when compiling SQL statements, processing DDL
statements, or executing the builtin stored procedures.
Cause. NonStop SQL/MX did not receive a reply it expected from MXCMP.
Effect. The operation fails.
Recovery. Verify that MXCMP is running.
SQL 8839
8839 Transaction was aborted.
Cause. A transaction failed during processing of an SQL/MX statement. NonStop
SQL/MX might have aborted an AUTOCOMMIT transaction, or a transaction was
aborted for some other reason (audit trail full, autoabort time limit reached, and so on).
Effect. The operation fails.
Recovery. Check the application event log for a detailed entry about this situation.
SQL 8840
8840 Object name provided to CLI is not valid.
Cause. The object named provided to CLI is invalid
Effect. The operation fails.
Recovery. Correct the object name and resubmit.
SQL 8841
8841 User application committed or aborted a transaction
started by SQL.
aborted by calling SQL COMMIT or ROLLBACK WORK.
Cause. NonStop SQL/MX started a transaction that was committed or aborted by an
embedded program, rather than by NonStop SQL/MX.
Effect. The operation fails.
Recovery. Commit or abort the transaction by calling SQL COMMIT or
ROLLBACKWORK.
This transaction needs to be committed or
HP NonStop SQL/MX Messages Manual—640324-001
10 -37

Hide quick links:

Advertisement

Table of Contents
loading

This manual is also suitable for:

Nonstop sql/mx 3.0

Table of Contents