ADSM-L

database deadlock

2004-06-11 11:55:51
Subject: database deadlock
From: "Gill, Geoffrey L." <GEOFFREY.L.GILL AT SAIC DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 11 Jun 2004 08:55:11 -0700
TSM Server AIX 4.3.3

TSM Version 5.1.6.3



I've seen this error the past couple of weeks, not every day, but enough
times get me wondering. It has always happens when the script runs to move
drmedia from vault retrieve to courier retrieve. This causes the move to
fail but I can run it again with success. The references I've been able to
find on WWW don't exactly fit the situation or version.



ANR0390W A server database deadlock situation has been encountered: lock
request for transaction

0:1.2230998674 will be denied to resolve the deadlock.

ANR9999D asvolacq.c(5752): ThreadId<44> Error 262 getting volume name for
volume 36750.

ANR9999D asvolacq.c(3643): ThreadId<44> Error 262 checking repair state for
volume 36750.

ANR0390W A server database deadlock situation has been encountered: lock
request for transaction

0:1.2230998674 will be denied to resolve the deadlock.

ANR9999D asvolacq.c(5752): ThreadId<44> Error 262 getting volume name for
volume 36750.

ANR9999D asvolacq.c(3811): ThreadId<44> Error 262 checking repair state for
volume 36750.

ANR6683I MOVE DRMEDIA: Volume U00010 was moved from VAULTRETRIEVE state to
COURIERRETRIEVE.

ANR0390W A server database deadlock situation has been encountered: lock
request for transaction

0:1.2230999065 will be denied to resolve the deadlock.



Geoff Gill
TSM Administrator
NT Systems Support Engineer
SAIC
E-Mail:   gillg AT saic DOT com
Phone:  (858) 826-4062
Pager:   (877) 854-0975

<Prev in Thread] Current Thread [Next in Thread>
  • database deadlock, Gill, Geoffrey L. <=