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-54
SQL 8906
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.
SQL 8907
Where procedure-name is the ANSI name of a stored procedure.
Cause. You are running an SQL/MX version that does not support stored procedure
result sets and attempted to compile a CALL statement for a stored procedure that
returns result sets. This message indicates a downgrade has been performed without
removing stored procedures that return result sets.
Effect. The SQL/MX statement is not compiled.
Recovery. Migrate to an SQL/MX version that supports stored procedure result sets.
SQL 8909
Cause. A call-level interface (CLI) application attempted to allocate a stored procedure
result set but the specified input statement is not a CALL statement. The stored
procedure result sets cannot be allocated from statements other than CALL
statements.
Effect. The operation fails.
Recovery. None. Contact your service provider.
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.
8907 Procedure procedure-name is registered to return result
sets and stored procedure result sets are not yet supported.
8909 The request to allocate a stored procedure result set
failed because the provided input statement is not a CALL
statement.