Hi,

You have a deadlock between a node and (one of) that node's filespace(s).

Without knowing the platform of level of your server, it's nearly
impossible to tell what's causing the deadlock.

Give a call to the support team and I'm certain they'll identify the source
of the deadlock and more importantly, how to resolve it.

Glen Hattrup
Tivoli Systems
TSM Server Development


"Leijnse, Finn F SSI-ISES-31" <Finn.F.Leijnse AT IS.SHELL DOT 
COM>@VM.MARIST.EDU>
on 06/14/2001 02:19:04 AM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To:   ADSM-L AT VM.MARIST DOT EDU
cc:
Subject:  database deadlock



hello all,

I have encountered a database deadlock and I was wondering if anyone can
explain to me how to read the following output. Is it possible to find out
what causes the deadlock?

Operation Results
A Deadlock was found:
Transaction 0:34806584.
  Waiting for Lock mode sLock on: Type=19001, NameSpace=0, Key='49'
  Held by transaction 0:34806600 in mode ixLock.
Transaction 0:34806600.
  Waiting for Lock mode xixLock on: Type=19002, NameSpace=0, Key='49.1'
  Held by transaction 0:34806584 in mode xLock.


> met vriendelijke groeten, regards et salutations,
> Finn Leijnse
> ISES/31 - Central Data Storage Management
> Shell Services International bv.
> Leidschendam
> email: Finn.F.Leijnse AT IS.shell DOT com
>