SQL/MX 3.2 Messages Manual (H06.25+, J06.14+)

Executor Messages (8000 through 8999)
HP NonStop SQL/MX Release 3.2 Messages Manual—691121-001
10-53
SQL 8903
Where process name is the name of an SQL/MX UDR server process.
Cause. NonStop SQL/MX received an interrupt signal, possibly caused by an MXCI
user pressing Ctrl-C while the SQL/MX UDR server was executing a stored procedure.
Effect. The operation fails, and if PROCESS_STOP_ was successful (as indicated by
a return value of 0), the SQL/MX UDR server is stopped.
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
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
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.
8903 An attempt was made by SQL/MX to kill the MXUDR server
for this statement (process name). PROCESS_STOP_ returned
value.
8904 SQL/MX did not receive a reply from MXUDR, possibly
caused by internal errors while executing user-defined
routines.
8905 The user does not have privilege-type privilege on
user-defined routine routine-name.