Home Page for the TeradataForum

Archives of the TeradataForum

Message Posted: Wed, 09 Mar 2005 @ 21:30:17 GMT

  <Prev Next>  
Next> Last>>  

Subj:   Lock Statement causing Deadlocking
From:   Claybourne Barrineau


Please help: (below is an extract from a BTEQ job)

      *** Failure 2631 Transaction ABORTed due to DeadLock.
                     Statement# 1, Info =0
      *** Total elapsed time was 19 seconds.

Should this be possible? I was attempting to execute this Lock at the beginning of a BT\ET transaction in BTEQ. The primary reason for executing this Lock was to prevent global deadlocks for occuring later in the transaction...now, I'm finding out that merely executing a Locking statement can cause Global dead-locking....%!%*&)$@!

Any help would be greatly appreciated!



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