SQL Codes › SQL Return Codes 0 through 243 › 170 - CONSTRAINT(S) DID NOT CONFIRM - TABLE PLACED IN CHECK STATUS

170 - CONSTRAINT(S) DID NOT CONFIRM - TABLE PLACED IN CHECK STATUS

Reason:

During an ALTER TABLE, you attempted to ADD a domain constraint, but the rows of the table violated the constraint.

The SQLSTATE that equates to this SQL return code is 01S01.

Action:

Delete the data in violation, or drop the constraint(s) violated.

1. Run the CONFIRM function of DBUTLTY to delete the row(s) in error. (You can also write them to an exception table for further action.)
2. Execute ALTER TABLE DROP CONSTRAINT to drop the constraint(s) violated. This causes the table to be reconfirmed and take it out of check status.