SQL/MP Messages Manual

SQL Executor Messages (8000 to 8999)
HP NonStop SQL/MP Messages Manual—427720-006
10-24
SQL 8238
Cause. The file system could not perform a buffered update or insert operation. To
determine the cause, see the supplied file system error code.
Effect. The current transaction is aborted. For nonaudited tables, data might be lost.
Recovery. Reissue the statement. If the error persists, use a CONTROL TABLE
statement to disable sequential insert and update operations.
SQL 8239
Cause. A partition of the file was not available at run time, and the user used a
CONTROL TABLE statement to request that SQL/MP skip the partition.
Effect. The unavailable partition is skipped and a warning is returned.
Recovery. If the partition is not to be skipped, issue a CONTROL TABLE... STOP AT
UNAVAILABLE PARTITION statement. This causes SQL/MP to return an error if a
partition is not available at run time.
SQL 8240
Cause. You used a CREATE INDEX NO INVALIDATE operation to create an index on
a column that is affected by this statement and that was not part of an alternate index
before this operation.
Effect. The statement executes, but updates of the new index cause additional
messages and therefore change performance characteristics.
Recovery. No recovery is necessary. To avoid this message, SQL compile the
application program or PREPARE the dynamic statement again. However, this will not
change the performance of this SQL statement.
8238 Error value-1 was returned by the file system during
flush of a sequential buffer for insert/update.
8239 Partition value-1 was skipped. See file system code
value-2 for details.
8240 A new index on table value-1 caused a change in the
execution plan of this SQL statement. Instead of a subset
operation that takes place in the disk process, NonStop
SQL/MP now performs a cursor update or delete, causing
multiple messages to be sent to and from the disk process.