Archives of the TeradataForum
Message Posted: Thu, 03 Apr 2003 @ 19:30:15 GMT
Sorry, I just read a note from our DBA and he provided the following answer to my question:
After an all AMP copy, copied tables do not have referential constraints. First, referential constraints are not copied into the dictionary definition tables, DBC.ReferencedTbls and DBC.ReferencingTbls, for either a referenced (parent) or referencing (child) table copied into a Teradata RDBMS. Moreover, all referential index descriptors are deleted from the archived table header before it is inserted into the copied table.
Reference constraints remain, however, on any table for which the copied table is a referenced table (a parent table) or any table the copied table (as a child table) references. Hence, when either a referenced or a referencing table is copied, the reference may be marked in the dictionary definition tables as inconsistent. While a table is marked as inconsistent with respect to referential integrity, no updates, inserts or deletes are permitted. The table is fully usable only when the inconsistencies are resolved.
? Use an ALTER TABLE DROP INCONSISTENT REFERENCES statement to drop inconsistent references.
? Use the ALTER TABLE ADD CONSTRAINT FOREIGN KEY REFERENCES to add referential constraints to the copied table.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|