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

Executor Messages (8000 through 8999)
HP NonStop SQL/MX Messages Manual—523730-004
10-45
SQL 8902
Cause. The SQL/MX UDR server generated an improperly formatted identifier when
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. 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, 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.
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.
8904 SQL/MX did not receive a reply from MXUDR, possibly
caused by internal errors while executing user-defined
routines.