Archives of the TeradataForum
Message Posted: Wed, 04 Oct 2006 @ 17:43:28 GMT
| Subj: | | Re: Backup structures only |
| |
| From: | | Anomy Anom |
<-- Anonymously Posted: Wednesday, October 04, 2006 11:23 -->
Nazy,
| | I ran the dictionary archive, and then restored (copy) it to see if it actually only backed up the structure. | |
| | The restore completed, but trying to do a row count gives me the following error: | |
| | 2654 - Operations not allowed. databasename.tablename is being restored. | |
RESPONSE:
Please read the ARCHIVE and RECOVERY manual to get a better understanding between data backup and dictionary backup.
The dictionary back up is for total disaster condition and if you have cluster backup. It is not for restore of database object structure.
The object restored using dictionary backup will remain unusable. I am not sure build will work in this case since you have nothing to build
from.
There is nothing wrong with thinking out of box and extract the DDL then drop the object and create it using the DDL extracted. Be warn that
sometime view DDL get truncated when it exceed the size of the column in DBC.TVM to store the definition. TSET can get around from my
experience.
You are better off having a set of job that extract the DDL into a storage place or maintain your DB structure in ERWin and create from there
if necessary. The model mart allow for version control so you won't have to find out critical business logic got truncated from view DDL because
it is too big.
Hope this helps.
| 
