Home Page for the TeradataForum
 
 

 

Archives of the TeradataForum





Message Posted: Fri, 07 Nov 2003 @ 16:25:18 GMT





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




Subj:   Re: DeadLock in teradata
 
From:   John Hall



Maybe a better question is: Why is a deadlock (I assume a 2631 error) being treated like a fatal error? It's a re-tryable condition. The manual says:

This error indicates that:

1) an excessive number of transactions were queued waiting for locks and the user's request would have blocked on the lock queue or

2) the request conflicted with another request, causing a deadlock or

3) a software problem (for example, a lost message) occurred, causing the request to "time out".

This is probably a temporary situation and the job should be re-submitted.





     
  <Prev Next>   <<First <Prev Next> Last>>  
 
 
 
 
 
 
 
 
  
 
  Top Home Join Privacy Feedback  
 
 
Copyright for the TeradataForum (TDATA-L), Manta BlueSky 
Last Modified: 30 Jun 2008