SQL/MX 2.x Messages Manual (H06.04+)

Executor Messages (8000 through 8999)
HP NonStop SQL/MX Messages Manual—540498-003
10-46
SQL 8901
Cause. During execution of an SQL/MX statement, an attempt was made to contact a
nonexistent SQL/MX UDR server.
Effect. The operation fails.
Recovery. Retry the SQL/MX statement.
SQL 8902
Cause. The SQL/MX UDR server generated an improperly formatted identifier when
NonStop SQL/MX was executing a stored procedure.
Effect. The operation fails.
Recovery. None. Contact your service provider.
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.
8901 The MXUDR server for this statement is no longer
running. The statement will be assigned a new MXUDR server if
it is executed again.
8902 An internal error occurred: MXUDR returned a UDR handle
that is not valid.
8903 An attempt was made by SQL/MX to kill the MXUDR server
for this statement (process name). PROCESS_STOP_ returned
value.