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

Executor Messages (8000 through 8999)
HP NonStop SQL/MX Messages Manual—523730-004
10-23
SQL 8613
Cause. An application started a transaction outside of SQL/MX that SQL/MX could not
commit or rollback.
Effect. The operation fails.
Recovery. The application that started the transaction must perform a commit or
rollback. SQL/MX must start any transactions it will later commit or rollback.
SQL 8614
Cause. SQL/MX cannot start a transaction when multiple contexts are present.
Effect. The transaction is unable to start.
Recovery. None. Contact your service provider.
SQL 8690
Cause. The source contains a character that cannot be translated to the target.
Effect. The operation fails.
Recovery. Make sure the source data is clean and translatable and resubmit.
SQL 8700
Cause. An ESP encountered an error during a query.
Effect. The query fails.
Recovery. Use the EMS event log information in the event generated by this failure to
diagnose and correct the problem. You might need to allocate page file space or
memory. If this does not correct the problem, contact your service provider.
8613 SQL cannot commit or rollback a transaction that was
started by application.
8614 SQL cannot begin a transaction when multiple contexts
exist.
8690 An invalid character value encountered in TRANSLATE
function.
8700 An assertion failure or out-of-memory condition occurred
during parallel execution.