Yes.
I frequently see it if there are multiple DELETE FILESPACE commands running
at the same time.
Appears the commands both need the same page in the data base, and one gets
locked out.
I have never had it cause any real problem.
You just have to reissue the DELETE FILESPACE commands again, to let it
finish deleting the objects in the filespace.
If you run the DELETE's one at a time, you won't have the problem.

***************************************************************
Wanda Prather
The Johns Hopkins Applied Physics Lab
443-778-8769
wanda_prather AT jhuapl DOT edu

"Intelligence has much less practical application than you'd think" -
Scott Adams/Dilbert
***************************************************************






> -----Original Message-----
> From: Jim Hunt [SMTP:Jim_Hunt AT VENCOR DOT COM]
> Sent: Monday, February 08, 1999 4:28 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:
>
> Has anyone seen this before?
>
>                       BACKGROUND completed with completion state FAILURE
> at
>                       16:18:03.
> 02/08/99   16:18:08  ANR0390W A server database deadlock situation has
> been
>                       encountered: lock request for transaction 0:7307576
> will
>                       be denied to resolve the deadlock.
> 02/08/99   16:18:08  ANR9999D afutil.c(1016): Lock acquisition (ixLock)
> failed
> more...   (<ENTER> to continue, 'C' to cancel)
>
>                       for bitfile root 0.
> 02/08/99   16:18:08  ANR0859E Data storage object erasure failure, DELETE
>                       FILESPACE process aborted.
> 02/08/99   16:18:08  ANR0985I Process 9 for DELETE FILESPACE running in
> the
>                       BACKGROUND completed with completion state FAILURE
> at
>                       16:18:08.
> 02/08/99   16:18:13  ANR0390W A server database deadlock situation has
> been
>                       encountered: lock request for transaction 0:7307585
> will
>                       be denied to resolve the deadlock.
> 02/08/99   16:18:13  ANR9999D afutil.c(1016): Lock acquisition (ixLock)
> failed
>                       for bitfile root 0.
> 02/08/99   16:18:13  ANR0859E Data storage object erasure failure, DELETE
>                       FILESPACE process aborted.
> 02/08/99   16:18:13  ANR0985I Process 10 for DELETE FILESPACE running in
> the
>                       BACKGROUND completed with completion state FAILURE
> at
>                       16:18:13.
> 02/08/99   16:18:19  ANR0390W A server database deadlock situation has
> been
>                       encountered: lock request for transaction 0:7307594
> will
>                       be denied to resolve the deadlock.
> 02/08/99   16:18:19  ANR9999D afutil.c(1016): Lock acquisition (ixLock)
> failed
>                       for bitfile root 0.