Mauro,

Thats exactly what I tried. Second expiry 18 objects expired. Third expiry 0
objects expired.
There were definitely no other processes running. I will keep an I on it
though.


> -----Original Message-----
> From: Mauro M. TINELLI [SMTP:Mauro.TINELLI AT ST DOT COM]
> Sent: 24 February 2000 12:30
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: Deadlock messages
>
> Jason,
>         I had the same problem once.  I had exaclty your fears, but then I
> repetead the 'expire inventory' later on and the problem did not show
> anymore. It actually removed the same number of objects it showed as
> errors before. It didn't repeat since then, but I'm keeping an eye on it
> though!
>
> I won't even think about an 'AUDIT DB' ...
> I'm using TSM 3.1.2.54.
>
> Mauro, STM
>
>
> > Hi,
> >
> > We have on the last couple of expiration runs been experiencing the
> > following messages for one of our clients. At first, I thought a client
> > backup at the same time might have been a problem. The messages below
> are
> > from an expiry running now. I have disabled all client access. The
> > expiration is the only process running.
> >
> > Can anyone explain how this is happening and how to resolve it ?   My
> first
> > though is that an aouditdb is required.
> >
> >
> > 02/24/00   10:52:04  ANR9999D imutil.c(2869): Lock acquisition (xLock)
> > failed
> >                       for Inventory node 11.
> >
> > 02/24/00   10:52:09  ANR0390W A server database deadlock situation has
> been
> >
> >                       encountered: lock request for transaction
> 0:188471970
> >
> >                       will be denied to resolve the deadlock.
> >
> > 02/24/00   10:52:09  ANR9999D imutil.c(2869): Lock acquisition (xLock)
> > failed
> >                       for Inventory node 11.
> >
> > 02/24/00   10:52:09  ANR9999D imexp.c(4138): Object 0.66515238 could
> not be
> >
> >                       deleted - expiration will continue.
> >
> > 02/24/00   10:52:14  ANR0390W A server database deadlock situation has
> been
> >
> >                       encountered: lock request for transaction
> 0:188471970
> >
> >                       will be denied to resolve the deadlock.
> >
> > 02/24/00   10:52:14  ANR9999D imutil.c(2869): Lock acquisition (xLock)
> > failed
> >                       for Inventory node 11.
> >
> > 02/24/00   10:52:19  ANR0390W A server database deadlock situation has
> been
> >
> >                       encountered: lock request for transaction
> 0:188471970
> >
> >                       will be denied to resolve the deadlock.
> >
> > 02/24/00   10:52:19  ANR9999D imutil.c(2869): Lock acquisition (xLock)
> > failed
> >                       for Inventory node 11.
> >
> > 02/24/00   10:52:19  ANR9999D imexp.c(4138): Object 0.66515239 could
> not be
> >
> >                       deleted - expiration will continue.
> >
> > Jason Morgan
> > Technical Support Analyst
> > Blaenau Gwent C.B.C
> >
> > Telephone: 01495 355230
> > Email: Jason.Morgan AT blaenau-gwent.gov DOT uk