Archives of the TeradataForum
Message Posted: Sat, 09 Mar 2003 @ 01:25:31 GMT
the BOOT command will Completely erase the AMP. It is normally used to reformat a Corrupted AMP before performing WHOLE AMP Table rebuild from fallback on the remaining GOOD AMPS. Basically any tables you have that aren't fallback are deleted and need to be reloaded.
in your case there is no reason to use the BOOT command since all your AMPS are fatal, there isn't anything to rebuild from.
The last time I saw this happen on W2K DEMO is someone was looking for disk space and saw AMP0.PDISK0 and AMP1.PDISK0 had 1 GIG worth of disk space and said cool let's delete it. we can get lots of disk space back.
If this is a REAL TERADATA ON W2K system, then someone was running Disk administrator and saw an empty raw slice (our pdisks show up as UNFORMATTED DISK) and said COOL Free diskspace and formatted the PDISKS as NTFS file systems.
Now when you try to start Teradata our data disks are corrupted and the amps go fatal.
You can look at the EVENT LOG under application and see if there are any Teradata Errors like can't open PDISKS or 5094's which mean the PDISKS are corrupted.
to correct the problem you need to get the pdisks back.
on a Real System you need to get a couple more RAW DISK slices or Get the orignal ones back and using vconfig assign them as the pdisks to the AMPS and run SYSINIT.
On the DEMO that would mean reinstalling.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|