Maintaining Tables with Related Constraints › Impact of ALTER TABLE on TEST and HIST Status Versions

Impact of ALTER TABLE on TEST and HIST Status Versions

When an SQL ALTER TABLE statement adds a constraint to a table, CA Datacom Datadictionary sets the CONSTRAINT attribute to A on all TEST and HIST status versions of that table. If you later attempt to copy one of these versions (or a structure containing one of these versions) to PROD status, CA Datacom Datadictionary prevents the copy, issues an error message, and identifies the table which has been altered. To recover, do one of the following:

• If you were copying a structure to PROD status and the table identified in the CA Datacom Datadictionary message as having been altered was not one of the tables you modified in the TEST status version of the structure, copy only the modified tables from TEST to PROD status.
• If the table altered through SQL is the table you modified in TEST status in CA Datacom Datadictionary, use one of the following procedures:

  1. Restore the TABLE entity-occurrence from PROD status to TEST.	1. Drop the constraints.
  2. Reapply any changes you had made through CA Datacom Datadictionary.	2. Copy the entity-occurrence to PROD status.
  3. Copy the entity-occurrence to PROD status.	3. Re-add the constraints.