These keywords prevent fallback data and secondary indexes from being built on fallback tables when restoring cluster archives to all AMPs. Use this option if restoring cluster archives to a Teradata Database that was reconfigured after the cluster archives were created.
When restoring journal tables to a Teradata Database that has been reconfigured since the journal archive was made, specify NO BUILD to prevent sorting of the restored journal and distribution of fallback rows. This procedure is useful when restoring more than one journal archive (that is, restoring an all-AMPs journal archive and one or more specific AMP journal archives).
If the NO BUILD keywords are used with RESTORE, run a separate BUILD statement for all databases and/or tables that were restored. The tables will not be accessible until a BUILD statement is run.
If the NO BUILD keywords are used while restoring a database or table that contains Join or Hash indexes, the database/table will be in a 'restoring' state when Teradata ARC attempts to restore the Join/Hash indexes. When in the 'restoring' state, the Teradata Database will not allow any access to the database/table. This will cause the restore of the Join/Hash index to fail.
In order to restore the Join/Hash indexes, follow this procedure:
- Run a separate BUILD job to build the fallback rows and secondary indexes for the database/table. This will clear the 'restoring' state and allow user access to the database/table.
- Restore the Join/Hash index by rerunning the restore job and just specifying the Join/Hash indexes to be restored as individual objects in the restore list.
If the NO BUILD keywords are used while restoring a database or table that contains Stat Collections, use the same procedure above for Join/Hash indexes in order to restore them.