SQL/MX 3.2 Messages Manual (H06.25+, J06.14+)

SQL/MX MXCMP Messages (2000 through 2999)
HP NonStop SQL/MX Release 3.2 Messages Manual—691121-001
4-24
SQL 2102
Cause. NonStop SQL/MX was unable to compile this query using the MINIMUM
optimization level.
Effect. NonStop SQL/MX is unable to process this query.
Recovery. Resubmit the query with MEDIUM optimization level. Precede the
statement with:
CONTROL QUERY DEFAULT OPTIMIZATION-LEVEL 'MEDIUM';
SQL 2103
Cause. NonStop SQL/MX was unable to compile this query, either because it was not
able to use the MINIMUM optimization level or because you used an incompatible
CONTROL QUERY SHAPE specification.
Effect. NonStop SQL/MX is unable to process this query.
Recovery. If applicable, resubmit the query with MINIMUM optimization level. Precede
the statement with:
CONTROL QUERY DEFAULT OPTIMIZATION-LEVEL 'MEDIUM';
Correct the CONTROL QUERY SHAPE specification and resubmit.
SQL 2104
Cause. NonStop SQL/MX was unable to compile this query, either because it was not
able to use the MEDIUM optimization level or because you used an incompatible
CONTROL QUERY SHAPE specification.
Effect. NonStop SQL/MX is unable to process this query.
2102 This query could not be compiled with 'MINIMUM'
optimization level. Suggestion: Retry with 'MEDIUM'
optimization level.
2103 This query could not be compiled for one/both of the
following reasons: a) Use of 'MINIMUM' optimization level, or
b) incompatible Control Query Shape specifications.
2104 This query could not be compiled for one of two reasons:
a) incompatible Control Query Shape (CQS) specifications, or
b) 'MEDIUM' optimization level is not sufficient to satisfy
the CQS in effect. Suggestion: a) inspect the CQS in effect;
or b) raise the optimization level to 'MAXIMUM'. Note that
for this query, 'MAXIMUM' optimization level may result in a
long compile time.