DSF Return Codes › CON

CON

TABLE HAS CONSTRAINT

Reason:

The table, key, or column (FIELD entity-occurrence) has a referential integrity constraint, a check constraint, or a unique constraint.

• You cannot add or delete a FIELD entity-occurrence in a key that represents a unique or referential integrity constraint and you cannot delete a FIELD entity-occurrence with a check constraint on it.
• You cannot copy a TEST status structure that has no constraints to PRODuction status when the existing PRODuction status version has constraints.
• You cannot change the REDEFINES attribute-value from N to Y or change the class from simple to any other class if the FIELD entity-occurrence is involved in a constraint of any type. (This would have the same effect as deleting the occurrence, since these changes make the FIELD entity-occurrence invisible to SQL processing.)
• You cannot change the UNIQUE attribute-value to N if the key represents a unique constraint.
• You cannot change the attributes of foreign keys.
• You cannot delete a key that represents a constraint.

Action:

Drop the constraint using the ALTER TABLE statement in SQL and resubmit the Datadictionary request.