Dead Lock Issue "Error code 2631 : Transaction ABORTed due to Deadlock."

Database
The Teradata Database channel includes discussions around advanced Teradata features such as high-performance parallel database technology, the optimizer, mixed workload management solutions, and other related technologies.
Enthusiast

Dead Lock Issue "Error code 2631 : Transaction ABORTed due to Deadlock."

Hi,

 

 

One of the informatica session got failed with the error "Transaction ABORTed due to Deadlock."

The querytext which is got failed with this error is  "Database databaseName;"

This statement only set the perticular database as DEFALT DATABASE.

 

I checked in DBQL logs and found no DDL or DML running at that time by the same user.

What could be the reason for this deadlock issue.

 

 

Thanks,

Shakt60.

1 REPLY
Senior Apprentice

Re: Dead Lock Issue "Error code 2631 : Transaction ABORTed due to Deadlock."

Hi,

 

A deadlock may not be (and usually isn't) between two commands from the same user. It is simply a conflict between two different transactions.

 

The 'database' command places row hash locks (one read, one write) on two different tables, it is this type of command which can deadlock with something else.

 

I think you've just been (very) unlucky with timing of this command.

 

If this happens a lot then you may need to speak to Teradata CS. Otherwise can you trap this specific error for the 'database' command and retry?

 

HTH

Dave

Ward Analytics Ltd - information in motion
www: http://www.ward-analytics.com