Archives of the TeradataForum
Message Posted: Tue, 20 Nov 2001 @ 14:54:58 GMT
I have some questions on how best to handle a bad mload....
We had an MLOAD come in the wrong input dataset (5 days worth of load instead of one). The application team cancelled the job through MVS and then dropped all the error tables and then tried to release the mload lock. They couldn't, so I suspect that the load was in the application phase already.
1) Did I have any options besides a restore and reply 4 days worth of loads?
2) The table has a NUPI, but based on tests I just ran, it would have rejected all the duplicates. Does this make sense?
3) Could I have just re-created the error tables and restarted?
4) Is there a way to restore the table without the secondary indexes (just to speed things up). I'm not referring to the nobuild option on the restore, but dropping the indexes?
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|