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

UPDATE STATISTICS and Executor Sort Messages
(9200 through 10049)
HP NonStop SQL/MX Messages Manual523730-004
11-7
Executor Sort Messages
SQL 10012
Cause. The caller specified a block number that is out of range.
Effect. The operation fails.
Recovery. None. This is an internal error. Contact your service provider.
SQL 10013
Cause. The available disks on the system are not suitable for scratch usage.
Effect. The operation fails.
Recovery. Make sure there are appropriate disks with enough space for scratch file
use. Disks such as optical disks, phantom disks, and SMS virtual disks are not
considered suitable. See the SQL/MX Reference Manual for more information on how
to influence the placement of scratch files.
SQL 10014
Cause. An internal data structure could not be allocated because of an out of memory
condition.
Effect. The operation fails.
Recovery. None. This is an internal error. Contact your service provider.
SQL 10015
Cause. An error occurred while calling a system level call.
Effect. The operation fails.
Recovery. See the Guardian Procedure Calls Reference Manual to diagnose and
correct the problem, or contact your service provider.
10012 Sort failed during overflow with an invalid block
number: $0~int0.
10013 Sort could not find any appropriate disks for overflow.
10014 Sort ran out of memory while allocating an internal
data structure.
10015 Sort failed while calling PROCESSHANDLE_GETMINE_ with
error number.