Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Mon, 13 Jun 2011 @ 12:01:35 GMT


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


Subj:   Re: Pseudo table and deadlock for BATCHUSER
 
From:   Adithya K Bayyana

Anom Wrote:

  Still, my question is: If one transaction (as a part of Multi statement request), is not complete and table is still in locked state then why 2nd transaction got started? By concept of pseudo table, it should get queued. Correct?  


There is possibility that this transaction might have acquired locks on some objects and waiting for some locks acquired by some other transaction, that may be some other users or some other transactions of yours might have got those locks.

As YB told you can use locking logger if you have already aborted/came out of that deadlock. I think you can find about the locks in lokdisp utility at the time of deadlock situation.


Thanks,

Adithya



     
  <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: 15 Jun 2023