Neoview Messages Manual (Volume 1) (R2.5)

Recovery Modify the statement and resubmit.
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 4189
4189 ORDER BY clause in an embedded INSERT, UPDATE, or DELETE statement
is not supported.
Cause An embedded INSERT, UPDATE, or DELETE statement has an ORDER BY clause.
Effect The statement does not compile.
Recovery Do not use ORDER BY with an embedded INSERT, UPDATE, or DELETE statement.
SQL 4190
4190 Table table-name is not a volatile table.
table-name
is the user-specified table name in the statement.
Cause The volatile table name specified in the VOLATILE TABLE SQL statement does not
exist.
Effect None.
Recovery Ensure that the volatile table with the specified table-name is created before
issuing the SQL statement.
SQL 4191
4191 Username schema-name specified as part of the volatile table or
index must be the same as the current username, user-name.
schema-name
is the user-specified schema name in the SQL statement.
user-name
is the current default SQL user name.
Cause The schema name specified in the volatile table command does not match the current
default SQL user name.
Effect None.
Recovery Ensure that schema-name matches the current default SQL user name and reissue
the SQL statement.
SQL 4192
4192 An invalid volatile object name was specified.
Cause The table name specified in the VOLATILE TABLE SQL statement should be either
a two-part name or single-part name.
Effect None.
Recovery Change the table name in the command to be either a single-part name or two-part
name and reissue the SQL statement.
158 Binder and Compilation Messages (4000 Through 4999)