Archives of the TeradataForum
Message Posted: Fri, 23 Jan 2004 @ 15:56:28 GMT
Join Indexes are NOT handled properly by ARC.
You can archive the tables belonging to a join index fine. However, when you restore/copy the table the table's header is messed up. This happens for both DICTIONARY and DATA archive/restores. We have seen no difference in retoring with a COPY or RESTORE. NCR's recommendation has been to drop the join index before you archive and restore the join index after the backup is completed. Since some of our join indices are non- trivial, this is not an acceptable answer.
After the restore, there is nothing in the dictionary to tell you which tables are effected.
We either have had to get the GSC to drop the table and then recreate it (this seems to be limited to table level archive/restores) or drop the table and recreate it ourselves (database level restores).
UNfortunately we already had Join Indices in production when we uncovered these problems (since V2R4). We (the DBA group) are not allowing Join Indices to be propogated any further.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|