Database deadlock
1999-10-04 16:39:05
I have been seeing sequences of messages similar to the following every few
days:
10/01/1999 15:17:29 ANR0390W A server database deadlock situation has been
encountered: lock request for transaction 0:5336084 will
be denied to resolve the deadlock.
10/01/1999 15:17:29 ANR9999D ASUTIL(706): Lock acquisition (ixLock) failed
for volume root.
10/01/1999 15:17:29 ANR1181E ASTXN348: Data storage transaction 0:5336084 was
aborted.
10/01/1999 15:17:29 ANR2183W ADMDVOL1807: Transaction 0:5336084 was aborted.
10/01/1999 15:17:29 ANR1160W Transaction was aborted for volume 600052.
10/01/1999 15:17:29 ANR0986I Process 227 for DELETE VOLUME (DISCARD DATA)
running in the FOREGROUND processed 179 items for a
total of 12,172,611 bytes with a completion state of
FAILURE at 15:17:29.
As far as I can tell, there were no node sessions in progress when the failure
occurred, and no administrative processes other than process 227 itself. I
find it difficult to imagine why ADSM would have any trouble with database
contention under those circumstances. We are running a 3.1.2.20 server under
MVS. Does anyone recognize this as a know problem?
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Database deadlock,
Thomas Denier <=
|
|
|