Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Sat, 20 Nov 2010 @ 09:50:18 GMT


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


Subj:   Deadlock and BTEQ
 
From:   Faible Mou

First of all, thank you Dieter for answering all my previous questions in details.

Now,

From the book "Introduction to Teradata Warehouse" Release 12.0, B035-1091-067A, March 2010

     ,-----
     | If you used BTEQ to submit the transaction, the database reports the
     | deadlock abort to BTEQ.  BTEQ resubmits only the request that caused
     | the error (the default behavior), not the complete transaction.
     | Because this can result in partially committed transactions, you must
     | take care when writing a BTEQ script to ensure that the transaction is
     | one request.
     `-----

I'm still not completely sure of the above.

If I write the statements in the following way, BTEQ will see them as only one request, thus will resubmit both statements when the deadlock occurs, correct?

     sel * from x
     ; sel * from y;

*To me* the term "request" and "transaction" are interchangeable here. What's the actual difference? How come resubmitting the request can result in partially committed transactions?

What will happen if the deadlock occurs in the middle of BEGIN TRANSACTION/END TRANSACTION statement?


Thanks

FM



     
  <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