Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Sun, 17 Mar 2002 @ 18:07:20 GMT


     
  <Prev Next>   <<First <Prev Next> Last>>  


Subj:   Re: DEADLOCK Errors
 
From:   Thomas F. Stanek

Tony,

I've seen this message get generated for two different reasons.

1) The most likely reason is that you are in contention with a resource locked by another user. If that's the case, PMON can show you the blocking session and the resource which is blocked, if you monitor your transaction while the block is occurring.

2) Less likely and more difficult to identify, is the situation where you time out because you are not getting certain system level resources. Particularly in early versions of V2R3, when the system is processing a lot of activity on the ByNet, there can be internal system congestion when passing messages between vprocs. This usually occurs when there is a lot of row re-distribution occurring. The result can be the same 3111/2631 timeout error.

If you can't identify a culprit through PMON, the second situation I described might be the culprit. The way to check on this is to use the UNIX puma -m command. I believe there is a discussion of it in the Performance Optimization guide.

If the problem really looks like the message passing problem, let me know and I can give you more details about what to look for.

Thomas F. Stanek
TFS Consulting
www.tfsconsulting.com



     
  <Prev Next>   <<First <Prev Next> Last>>  
 
 
 
 
 
 
 
 
  
  Top Home Privacy Feedback  
 
 
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 27 Dec 2016