Re: deadlock error
2005-10-10 09:27:31
The message is well described in the Messages manual, or use the Help
command.
The situation is in reaction to a context of active sessions and/or
processes. A simple example is in having multiple simultaneous Delete
Filespace operations running for the same node, which is one case
where a deadlock has been observed. You need to examine what's going
on at the time: you may have too many things scheduled for the same
period, and the congestion is resulting in conflicts. There is a SHow
DEADLocks command which may yield info at event time.
Richard Sims
On Oct 9, 2005, at 11:35 PM, Dksh Cssc wrote:
Dear all,
Today a schedule of mine failed.
Was wondering what does this message means:
10/08/05 10:15:04 ANR0379W A server database deadlock situation
has
been en
countered: lock request for the df bitfile root
lock,will
be denied to resolve the
deadlock.
10/08/05 10:15:04 ANR1181E dftxn.c196: Data storage transaction
0:200309706
was aborted. (SESSION: 111986)
10/08/05 10:15:04 ANR0532W smnode.c2694: Transaction
0:200309706 was
aborted
for session 111986 for node KULIDES01 (WinNT).
(SESSION:
111986)
It only happens to this particular node. i suppose it's TSM database
deadlock.Does the client node contribute to this problem? Is there
any way
to fine tune it before it happens again?
Thanks and Warmest Regards,
|
|
|