ADSM-L

Re: DEADLOCK

1999-06-30 18:06:15
Subject: Re: DEADLOCK
From: "Vraspir, Mary J." <MJVraspir AT WEST DOT COM>
Date: Wed, 30 Jun 1999 17:06:15 -0500
Razdan,
I don't believe is the new code but rather  the database access you are
doing.
I am seeing the same error at 3.1.2.20.  I had expiration, migration and
delete filespace all running at the same time.
Mary Vraspir
West Teleservices
Omaha,NE

        -----Original Message-----
        From:   Ramesh Razdan [SMTP:RRazdan AT FEET DOT COM]
        Sent:   Wednesday, June 30, 1999 12:00 PM
        To:     ADSM-L AT VM.MARIST DOT EDU
        Subject:        Re: DEADLOCK

        Yesterday i also encountered the same situation when i upgraded my
server to 3.1.25. I immidiately backed out to 3.1.20

        thx
        razdan

        >>> Francisco Molero <fmolero AT YAHOO DOT COM> 06/30/99 11:57AM >>>
        Hello,
        I have a question about the deadlock, I got a deadlock error which,
I
        suppose, was due to expiration process and migration are running at
the
        same time. Well, then I want to make a further investigation in
order
        to know what happened.

        26/06/99   09:33:09      ANR0390W A server database deadlock
situation
        has been encountered: lock request for transaction 0:94367565 will
be
        denied to resolve the deadlock.

        26/06/99   09:33:09      ANR9999D afutil.c(962): Lock acquisition
        (xLock) failed for PoolId=20, cluster SrvId=0, Ck1=466, Ck2=16

        26/06/99   09:33:09      ANR1181E aftxn.c201: Data storage
transaction
        0:94367565 was aborted.

        26/06/99   09:33:09      ANR2183W imexp.c2629: Transaction
0:94367565
        was aborted.

        26/06/99   09:33:09      ANR0860E Expiration process 137 terminated
due
        to internal error: examined 171744 objects, deleting 59185 backup
        objects, 1331 archive objects, 0 DB backup volumes, and 0 recovery
plan
        files. 0 errors were encountered.

        26/06/99   09:33:09      ANR0987I Process 137 for
        EXPIRE INVENTORY running in the BACKGROUND processed 60516 items
with a
        completion state of SUCCESS at 09:33:09.

        My questions are the following:

        1.- When I see the transaction number, How can I know what the
        transaction number means?

        2.- The ANR9999D shows several codes what is the meaning of these
        codes?

        3.- If the proccess stopped due to internal error. Why does it show
0
        errors were found ?

        4.- Where can I find information about the *.c files which are shown
in
        the actlog ?

        Regards
        _________________________________________________________
        Do You Yahoo!?
        Get your free @yahoo.com address at http://mail.yahoo.com
<Prev in Thread] Current Thread [Next in Thread>