HP NonStop SQL/MX Messages Manual page 121

SQL/MX MXCMP Messages (2000 through 2999)
Recovery. If applicable, use the MAXIMUM optimization level, correct the CONTROL
QUERY SHAPE specification, and resubmit.
SQL 2105
2105 This query could not be compiled because of incompatible
Control Query Shape (CQS) specifications. Inspect the CQS in
effect.
Cause. NonStop SQL/MX was unable to compile this query because you used an
incompatible CONTROL QUERY SHAPE specification.
Effect. NonStop SQL/MX is unable to process this query.
Recovery. Correct the CONTROL QUERY SHAPE specification and resubmit.
SQL 2106
2106 This statement could not be compiled since it is too
long. Break up large statements into smaller pieces.
Cause. NonStop SQL/MX was unable to compile this query because it is too long.
Effect. NonStop SQL/MX is unable to process this query.
Recovery. Try breaking the statement into smaller pieces.
SQL 2107
2107 This statement could not be compiled. Suggestion:
Address the issue(s) raised in the reported warning(s).
Cause. NonStop SQL/MX was unable to compile the query.
Effect. The operation fails.
Recovery. Use the warning messages returned by the compiler to diagnose and
correct the problem.
SQL 2108
2108 Statement was compiled as if query plan caching were
off.
Cause. The SQL/MX compiler attempted to compile this query with query caching on
but failed. It then successfully compiled this query with caching turned off.
Effect. The SQL/MX compiler has compiled the query as if query plan caching was
turned off even though caching is currently on. The prepared query can be executed as
usual.
HP NonStop SQL/MX Messages Manual—640324-001
4- 25