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

Data Definition Language (DDL) Messages (1000
through 1999)
HP NonStop SQL/MX Release 3.2 Messages Manual—691121-001
3-79
Recovery. None.
SQL 1615
Where $0~String0 is the type of constraint, NOT NULL or primary key.
Where $1~String1 is the referential action.
Cause. The NOT NULL constraint cannot be created on a referencing column with the
SET NULL referential action on it. (OR) The primary key constraint cannot be created
on the referencing column with the referential action specified because the primary key
cannot be updated.
Effect. The operation fails.
Recovery. Drop the referential integrity constraint.
SQL 1616
Where reason can be nested views or a view with VALUES constructor.
Cause. When Similarity Check is enabled for views, creating or altering a view
containing nested views or a VALUES constructor is not supported. For more
information, see the SQL/MX 3.2 Reference Manual.
When a view definition contains nested views or a VALUES constructor or both, this
error is returned for the following conditions:

CREATE or ALTER VIEW statement syntax with Similarity Check enabled

CREATE VIEW statement syntax does not specify the Similarity Check option and
the CQD DDL_VIEW_SIMILARITY_CHECK is set to ON.
Effect. The operation fails.
Recovery. Modify the syntax by removing references to the nested views or VALUES
constructor and resubmit the statement.
SQL 1617
Where string is enabled or disabled.
Cause. You issued an ALTER VIEW statement for one of the following conditions:
1615 $0~String0 cannot be created, since it conflicts with
$1~String1 referential action of the referential constraint
$2~ConstraintName.
1616 Similarity Check is not supported for reason.
1617 Similarity Check is already string.