HP NonStop SQL/MX Messages Manual page 229

Binder and Compilation Messages (4000 through
4999)
SQL 4184
4184 Columns that are part of a referential constraint cannot
be updated using embedded UPDATE statements.
Cause. You attempted to perform an embedded UPDATE statement on columns that
are part of a referential constraint.
Effect. The operation fails.
Recovery. Modify the statement and resubmit.
SQL 4193
4193 The schema name prefix volatile-schema-prefix is
reserved and cannot be used.
Where volatile-schema-prefix is a reserved schema prefix used internally to
manage volatile tables.
Cause. The volatile schema managed by the system uses a reserved schema prefix.
This prefix is a reserved word and cannot be used in an SQL statement.
Effect. None.
Recovery. Change the schema name provided as part of the two-part name to
anything other than volatile-schema-prefix and reissue the SQL statement.
SQL 4195
4195 The name, $0~string0, specified in the GROUP BY or
HAVING clause is ambiguous.
Cause. The GROUP BY expression contains a renamed column in the select list.
Effect. The statement does not compile.
Recovery. Correct the column name in the GROUP BY expression.
SQL 4196
4196 The HAVING clause that uses a renamed column cannot
contain an aggregate or a subquery.
Cause. The HAVING predicate refers to a renamed column in the select list.
Effect. The statement does not compile.
Recovery. Correct the column name in the HAVING predicate.
HP NonStop SQL/MX Messages Manual—640324-001
6- 43