Archives of the TeradataForum
Message Posted: Fri, 22 Sep 2006 @ 10:43:34 GMT
Last week we had a strange problem. One of the users had run a query which screwed up all the system resources and also create AMP Worker Task Deadlock.
As discussed with NCR we need to apply a os-level patch.
Is there any other things we need to consider on the database side to make the query non responsive after the timeout.
Thanks and regards,
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|