Archives of the TeradataForum
Message Posted: Thu, 01 Aug 2002 @ 07:46:48 GMT
We have experienced a rollback problem when a user aborted a long running update. This update was running for several hours when they terminated their Queryman session.
Then the rollback commenced and ran for several hours. During this time, the rollback process took nearly all the CPU time and the box was barely usable. For example, users were getting logon timeouts, simple queries that normally take 2 minutes were taking 30 minutes etc.
Once the rollback completed, the system recovered to its normal performance level.
Does any one have any experience on how to handle this? Are there any options available where one can reduce the loss of service during a rollback?
We are running Teradata V2R3 which is both channel attached and ODBC attached.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|