 |
 |
Archives of the TeradataForum
Message Posted: Fri, 27 Aug 1999 @ 16:39:55 GMT
| Subj: | | Re: How to stop or avoid Rollback or recovery process |
| |
| From: | | Mark Andrews |
The best thing to use in the case of updates to an existing table is multiload. Then if you kill it you can blow away the table
if you want without any rollback. You may already know this, and it does not answer your original question of how to kill a
rollback. There is a way, but it is not pretty, and NOT recommended by NCR. We have had to do it in a similar situation where the
rollback would have taken several days maybe even weeks to complete, as it will run approximately 2 - 2.5 times as long as the
original insert/update. The only way I know to kill a rollback is to blow away the transient journal. I cannot overemphasize that
this is a drastic step and not to be entered into lightly. It has to be done in close coordination with NCR, and you must make sure
no other transactions are running on the box. I'm sure your support reps can tell you of all associated risks and issues associated
with doing this.
Mark Andrews
Sr. DBA
Delta Technology
| |
