Neoview Messages Manual (Volume 1) (R2.5)

Recovery Verify that the Neoview database UDR server is running. If not, the Neoview
database software statement will acquire a new Neoview database 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. The
user-defined routine might be used by a trigger.
Effect The operation fails.
Recovery You must have the stored procedure’s owner or another authorized user grant
you the required EXECUTE privilege. Then resubmit. If the target routine is used by a trigger,
either abandon the operation or grant the right privilege to the trigger definer (or invoker)
and reattempt the operation.
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 HP Neoview SQL statement, the Neoview database executor
received a message from the Neoview database UDR server that was unreadable in some way.
Either the message was corrupted by the Neoview database UDR server, or an internal error
occurred within the Neoview database executor.
Effect The operation fails.
Recovery Do not attempt recovery. HP support will perform recovery operations in response
to an automatically generated dial-out message about this condition.
SQL 8909
8909 The request to allocate a stored procedure result set failed because
the provided input statement is not a CALL statement.
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. Stored procedure result sets
cannot be allocated from statements other than CALL statements.
Effect The operation fails.
Recovery None. Contact the GMCSC and report this condition.
SQL 8910
8910 Reorg command on name failed.
name
is the table, index, or materialized view where the Reorg operation fails.
Cause The reorganization failed because of unavailable resources. Common causes are a
resource being busy or a device being down.
Effect The operation fails.
Recovery To determine the cause of the problem, look in the EMS log for other messages
that report additional errors and unavailable resources. Consider searching the log for the
keyword reorg to find other errors that report problems. Fix the problem or wait until the
resources are available, and retry the Reorg operation.
SQL 8911
8911 Reorg command on name failed. reason
220 Executor Messages (8000 Through 8999)