Table of Contents
Advertisement
n1
is the time limit of the processor in seconds.
pp
is the disk process where the problem was detected.
Cause
The CPU time accumulated in an SQL disk process exceeded the limit n1 for which
the query is configured. This problem was detected in disk process pp.
Effect
The operation fails.
Recovery
or increase the limit.
SQL 8026
8026 Server declined cancel request. The query ID of the targeted query
was not found.
Cause
The query ID specified did not correspond to an executing, instrumented query.
Effect
The query is not canceled.
Recovery
SQL 8027
8027 Server declined cancel request. The message to pp timed out.
pp
is the name of the process.
Cause
The request to cancel a target query, which was sent to the MXSSMP process, did not
complete before its configured timeout period.
Effect
The query is not canceled.
Recovery
'n' command. If the problem persists, check to see if the system is very busy.
SQL 8028
8028 Server declined cancel request. The pp process was not found.
pp
is the name of the process.
Cause
The MXSSMP process, which is used to process cancel requests, is not running.
Effect
The query is not canceled.
Recovery
restart.
SQL 8029
8029 Server declined cancel request. The user is not authorized to make
this request.
Cause
An attempt was made to use the CANCEL statement by a user who is not the target
query's user, super.services or super.super.
Effect
The query is not canceled.
Recovery
SQL 8030
8030 Stored row count is invalid for table
Cause
A row count for one or more partitions has become invalid, most likely due to a
partition being moved or a DUP operation.
Effect
The statement terminates without returning a row count.
Recovery
perform a SELECT COUNT (*) instead.
188
Executor Messages (8000 Through 8999)
If possible, rewrite the query so that it can complete within the configured limit,
Correct the query ID specified or cancel the query only when it is executing.
Increase the time-out period by using SET SESSION DEFAULT RTS_TIMEOUT
Correct any problem that causes the MXSSMP process to stop and not automatically
Cancel the query using one of the authorized user accounts
Use the PURGEDATA utility or delete all rows from the affected partition(s), or
Advertisement
Table of Contents
