Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Tue, 29 Oct 2002 @ 17:02:58 GMT


     
  <Prev Next>   <<First <Prev Next> Last>>  


Subj:   Re: When to archive dictionary tables
 
From:   Richard Perry

Anomy,

My preferred approach for this process would be to carry out the following:

Run a checktable level 2. Pass any errors to NCR.

Archive database (DBC).
Archive dictionary (DBC) all.
Archive data tables.

Delete database (DBC) all, exclude (DBC)
Restore database (DBC).
Tpareset.
Restore dictionary (DBC) all Exclude (DBC)
Restore data tables.
Run a build on all databases. Build data tables (DBC) all exclude (DBC)

The Archive of the data tables is probably best split into a number of similar size blocks, this will allow you to be restoring the first archive while later archives are still running (Not necessary if time is not a problem.)

If you wish to use restore, I would suggest that you restore the dictionary archive first. You cannot issue a restore against a table/database/macro/view which is not defined in the Dictionary. The other alternative is to use copy, which does not require a dictionary restore, but I would imagine that this is not advisable.

The detail above is not a recommendation, it purely details how I would approach the migration that you are considering.

If you are in any doubt, liaise with your local NCR support team, they are always very helpful on these kind of matters.

Richard.



     
  <Prev Next>   <<First <Prev Next> Last>>  
 
 
 
 
 
 
 
 
  
  Top Home Privacy Feedback  
 
 
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 15 Jun 2023