About Teradata deadlock issue

[ThunderRice]

Hello,

Recently, I encountered a Teradata deadlock problem when I used Fastexport utility, please see the error log below:

0002 .LOGTABLE LOGDB.TRANS_log;
**** 16:41:33 UTY8400 Default character set: ASCII
**** 16:41:33 UTY8400 Maximum supported buffer size: 64K
**** 16:41:36 UTY1008 RDBMS failure: 2631, Transaction ABORTed due to Deadlock.
**** 16:41:36 UTY1017 Resubmitting the last request because a retryable error occurred.
**** 16:41:36 UTY1006 CLI error: 0, Transaction ABORTed due to Deadlock.
**** 16:41:36 UTY2410 Total processor time used = '0.046875 Seconds'
. Start : 16:41:30 - SUN JUL 04, 2004
. End : 16:41:36 - SUN JUL 04, 2004
. Highest return code encountered = '12'.
run_fexp_command() = 1

I just curious what kind of situration will caused "deadlock" problem of Teradata RDBMS
and how to solve or avoid this situration?

Thanks in advance.

 

[dnoeth]

Check the V2R5.1 Performance Optimization Manual, mainly Ch. 14: Database Locks and Performance

But it's strange to have a deadlock during a Select...

Dieter