 |
 |
Archives of the TeradataForum
Message Posted: Wed, 11 Apr 2001 @ 14:57:34 GMT
Subj: | | Re: Killing a rollback process |
|
From: | | John Hall |
The GSC can dial-in to a system in the process of a rollback and using the debugger, cancel the rollback itself. On the DBS side, this
leaves the change records from the original job in the transient journal - those have to be cleaned-up before anything else is done with the
system. This clean-up is one of the things that the GSC will do while they are dialed-in. Since the rollback hasn't run to completion and
the transient journal was cleaned-up, the target table is corrupted.
| |