That's exactly what I am seeing.
I'm testing some variations on how we delete. I think
I may have discovered something but I need to test some more.

Possibly a bug or glitch in the software....

C

__________________________________________________
Cris Robinson
Sr. Technical Analyst
Enterprise Storage Management / TSM (ADSM)
Liberty Mutual Insurance
Portsmouth, New Hampshire
603.431.8400.54837
mailto:cris.robinson AT libertymutual DOT com

        -----Original Message-----
        From:   Adam Slesinger [SMTP:aslesinger AT US.BNSMC DOT COM]
        Sent:   Wednesday, February 02, 2000 3:02 PM
        To:     ADSM-L AT VM.MARIST DOT EDU
        Subject:        Re: database deadlocks

        Chris,

        The only time I've seen database deadlock situations occur is when
I've run more
        than one delete filespace process at the same time.

        adam
        __________________
        Adam Slesinger
        Corporate Information Systems
        Brown & Sharpe, RI
        Phone: (401) 886-2236
        Pager: (800) 913-5395
        Email: aslesinger AT us.bnsmc DOT com


        Cris Robinson wrote:

        > Does anyone know what would cause the database to deadlock while
deleting a
        > filespace if NO other processes were running?
        > I have some, understatement, a bunch , ok, a few thousand old
filespaces to
        > delete from an active server so i can't just
        > wipe the server and start over. The clients are Win95 and the
server is NT
        > 4.0 SP4  ADSM server running 3.1.2.40 code level.
        >
        > here is the message...
        >
        > Date and Time       Message
        >
        >
----------------------------------------------------------------------------
        >
        >
----------------------------------------------------------------------------
        > -----------------
        > -----------------
        > 02/02/2000 08:20:59 ANR0390W A server database deadlock situation
has been
        > encountered: lock request for transaction 0:49241731 will be
denied to
        > resolve the deadlock.
        > 02/02/2000 08:20:59 ANR9999D asutil.c(782): Lock acquisition
(xLock) failed
        > for volume id 712.
        >
        > 02/02/2000 08:20:59 ANR1181E astxn.c352: Data storage transaction
0:49241731
        > was aborted.
        >
        > 02/02/2000 08:20:59 ANR2183W imfsdel.c1532: Transaction 0:49241731
was
        > aborted.
        >
        > 02/02/2000 08:20:59 ANR0826I DELETE FILESPACE LIBERTY for node
        > SILVEY_K-0500P encountered a transaction failure.
        >
        > 02/02/2000 08:20:59 ANR0827I DELETE FILESPACE LIBERTY will be
retried for
        > node SILVEY_K-0500P.
        >
        > __________________________________________________
        > Cris Robinson
        > Sr. Technical Analyst
        > Enterprise Storage Management / TSM (ADSM)
        > Liberty Mutual Insurance
        > Portsmouth, New Hampshire
        > 603.431.8400.54837
        > mailto:cris.robinson AT libertymutual DOT com

        --