HP NonStop SQL/MX Messages Manual page 311

Table of Contents

Advertisement

Executor Sort and Scratch File I/O Messages (10000
through 10199)
Effect. The operation fails.
Recovery. Contact your service provider.
SQL 10012
10012 Sort failed during overflow with an invalid block
number: number.
Cause. The caller specified a block number that is out of range.
Effect. The operation fails.
Recovery. Do not attempt recovery. Contact your service provider.
SQL 10013
10013 Sort could not find any appropriate disks for overflow.
Cause. The available disks on the system are not suitable for scratch usage.
Effect. The operation fails.
Recovery. Ensure that there are appropriate disks with enough space for scratch file
use. Disks such as optical disks, phantom disks, and Storage Management Foundation
(SMF) 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
10014 Sort ran out of memory while allocating an internal
data structure.
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
10015 Sort failed while calling PROCESSHANDLE_GETMINE_ with
error number.
Cause. An error occurred while calling a system level call.
Effect. The operation fails.
Recovery. Contact your service provider.
HP NonStop SQL/MX Messages Manual—640324-001
12- 3
Executor Sort Messages

Hide quick links:

Advertisement

Table of Contents
loading

This manual is also suitable for:

Nonstop sql/mx 3.0

Table of Contents