HP NonStop SQL/MX Messages Manual page 299

Executor Messages (8000 through 8999)
Recovery. The SQL/MX statement will acquire a new SQL/MX UDR server if it is
executed again. If the MXCI user was attempting to halt a long-running stored
procedure, investigate to determine whether or not problems within the stored
procedure might be causing the delay.
SQL 8904
8904 SQL/MX did not receive a reply from MXUDR, possibly
caused by internal errors while executing user-defined
routines.
Cause. During execution of an SQL/MX statement, NonStop SQL/MX did not receive
an expected reply from the SQL/MX UDR server.
Effect. The operation fails.
Recovery. Verify that the SQL/MX UDR server is running. If not, the SQL/MX
statement will acquire a new SQL/MX UDR server when it is next executed.
SQL 8905
8905 The user does not have privilege-type privilege on
user-defined routine routine-name.
Cause. You do not have the required EXECUTE privilege on a stored procedure.
Effect. The operation fails.
Recovery. You must have the stored procedure's owner or another authorized user
grant you the required EXECUTE privilege, and then resubmit.
SQL 8906
8906 An invalid or corrupt MXUDR reply could not be
processed, possibly due to memory corruption in MXUDR while
executing user-defined routines or an internal error in
SQL/MX.
Cause. During execution of an SQL/MX statement, the SQL/MX executor received a
message from the SQL/MX UDR server that was unreadable in some way. Either the
message was corrupted by the SQL/MX UDR server, or an internal error occurred
within the SQL/MX executor.
Effect. The operation fails.
Recovery. If you have linked a native method library into the SQL/MX UDR server,
determine whether code in that library could be causing the problem. Otherwise,
contact your service provider.
HP NonStop SQL/MX Messages Manual—640324-001
10 -51