Home Page for the TeradataForum

Archives of the TeradataForum

Message Posted: Mon, 30 Aug 2010 @ 08:39:04 GMT

  <Prev Next>  
Next> Last>>  

Subj:   2631: Transaction ABORTed due to Deadlock - did not retry
From:   Mori, Naoko

[2631: Transaction ABORTed due to Deadlock.] has occured, and it did not retry.

     [Select xx from table] was executed when [Delete from dbc.accesslog] was in a session.
     The message 2631 was returned and [Select ...] job was abended.

     When RetryAccLogDeadlock on DBSCONTROL/Internal is set TRUE,
     2631 should be returned, then Teradata is supposed to retry the query.

     However, this time, DBQL did not show any record that it retried.
     This job abended.

     The [Select...] job is connecting to Teradata using SAS Access to Teradata (ANSI mode).
     (Version SAS 9.1 Foundation)
     (Teradata Version V2R.06.02)

My question is why it did not retry.

I was wondering if [SAS Access to Teradata] is a cause.

If so, what can I do to avoid this?

If anyone has any idea, please help me!

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