Are you running any migration or reclamation at the same time you're running
expiration? This might be why you're getting the deadlocks.
(ADSM might be trying to expire a file at the same time it's moving it)

On Wednesday, August 25, 1999 5:41 AM, Bates, Richard
[SMTP:Richard.Bates AT VERTEX.CO DOT UK] wrote:
> Ben,
>
> re: expiration problems
>
> I can't find any common factor between those servers which work and those
> which do not.  Out of 7 servers:
>
>  - 3 are OK
>  - 3 get stuck on expiration and process a few objects an hour! (and cannot
> be cancelled)
>  - 1 completes with 50 or so errors like that below.
>
> 08/24/99 08:11:44 ANR0390W A server database deadlock
> situation has been encountered: lock request for transaction
> 0:55712799 will be denied to resolve the deadlock.
> 08/24/99 08:11:44 ANR9999D imutil.c(2869): Lock acquisition (xLock)
> failed for Inventory node 69.
> 08/24/99 08:11:45 ANR9999D imexp.c(4222): Object 0.18706841
> could not be deleted - expiration will continue.
>
> This all started occuring the day after we upgraded to 3.1.2.40.
> Unfortunately the
> server we tested for a week or so exhibited no problems.
>
> IBM recommend that we go back to 3.1.2.20 on our affected servers.
>
> Richard.
>
> =====================================
> Technical Services (ADSM) - Dawson House
> Int: 33298  Ext: 01925 233298
> =====================================
>
> > -----Original Message-----
> > From: bbullock [SMTP:bbullock AT MICRON DOT COM]
> > Sent: 24 August 1999 16:00
> > To:   ADSM-L AT VM.MARIST DOT EDU
> > Subject:      Re: Adsm server 3.1.2.40, problems?
> >
> >         Oh Richard, you strike fear in my soul. I too am running 6 ADSM
> > servers on various versions of AIX. I  need to upgrade to version 3.1.2.40
> > to use the new 3590E tape drives. I have upgraded 3 so far and have been
> > monitoring the expire inventory for just these types of problems. So far
> > (knock on wood), all my servers on 3.1.2.40 seem to be working fine. My
> > questions for you would be:
> >
> > Did the expire inventory problem show up immediately after the upgrade?
> > Does there seem to be a common factor on the servers with the problem? (DB
> > size, OS version)
> > Any idea why your other 3 servers are working properly with this ADSM
> > version?
> >
> >         I'd really like to avoid the grief you are going through if
> > possible.
> >
> > Thanks,
> > Ben
> > Micron Technology Inc,
> > Boise, ID
> >
> > > -----Original Message-----
> > > From: Bates, Richard [mailto:Richard.Bates AT VERTEX.CO DOT UK]
> > > Sent: Tuesday, August 24, 1999 3:20 AM
> > > To: ADSM-L AT VM.MARIST DOT EDU
> > > Subject: Re: Adsm server 3.1.2.40, problems?
> > >
> > >
> > > We have 7 ADSM servers all running a mix of AIX 4.1.5 and 4.3.
> > > We have been at 3.1.2.40 for about a week or so.  4 of our
> > > servers are having big problems with expiration. For example
> > > on one server expiration ran for about 3 days and processed just
> > > a handful of objects. We can not cancel the expiration process
> > > with either "can pro" or "cancel expiration".
> > >
> > > As a result, our database is getting bigger and bigger!!
> > >
> > > We have a call open with IBM,  who inform us that there is
> > > an APAR (ic24611) which references this exact problem - but
> > > on Sun Solaris.
> > >
> > > Not sure whether any other platforms are affected.
> > >
> > > Sigh!
> > > Richard.
> > >
> > > =====================================
> > > Technical Services (ADSM) - Dawson House
> > > Int: 33298  Ext: 01925 233298
> > > =====================================
> > >
> > > > -----Original Message-----
> > > > From: Toora, Kuli [SMTP:kulbinder.toora AT MEB.CO DOT UK]
> > > > Sent: 23 August 1999 16:32
> > > > To:   ADSM-L AT VM.MARIST DOT EDU
> > > > Subject:      Re: Adsm server 3.1.2.40, problems?
> > > >
> > > > We plan to install the code on a test system and run it
> > > there for a while
> > > > until we are happy that there are no problems.
> > > > I will post any findings.
> > > >
> > > > Thanks,
> > > >
> > > > Kuli.
> > > >
> > > > Kulbinder Toora
> > > > 01384 296191 x3498
> > > > e-mail - Kulbinder.toora AT meb.co DOT uk
> > > > NPEC (National Power Energy Company)
> > > >
> > > > > -----Original Message-----
> > > > > From: Lambelet,Rene,VEVEY,FC-SIL/INF.
> > > [SMTP:Rene.Lambelet AT NESTLE DOT COM]
> > > > > Sent: Monday, August 23, 1999 4:01 PM
> > > > > To:   ADSM-L AT VM.MARIST DOT EDU
> > > > > Subject:      Adsm server 3.1.2.40, problems?
> > > > >
> > > > > Hello,
> > > > > has anyone already installed or upgraded to adsm 3.1.2.40
> > > under OS/390 ?
> > > > >
> > > > > If yes, what are the problem you ever met?
> > > > > I wonder if it is now time to run this new code, we need
> > > it for the long
> > > > > name support of Netware clients.
> > > > > Any advices would be appreciated...
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Rene Lambelet
> > > > > Nestec SA - 55, Av. Nestle - CH-1800 Vevey
> > > > > Tel: ++41'21'924'35'43 / Fax: ++41'21'924'45'89
> > > > > E-Mail: rene.lambelet AT nestle DOT com
> > > > >
> > > > > ================================================================
> > > > >
> > > > > This incoming e-mail (and any attachments) has been
> > > checked at MEB,
> > > > > and has been found to be clean from any virus infection
> > > > > (using Sophos SAVI 3.24 and Dr Solomon's v7.96).
> > > > >
> > > > > Virus queries - Tech Support (09 3521)
> > > > > E-mail system - External Postmaster (09 3673)
> > > > >
> > > > > ================================================================
> > > > ================================================================
> > > >
> > > > This outgoing e-mail (and any attachments) has been checked
> > > > (using Sophos SAVI 3.24 and Dr Solomon's v7.96) before leaving us
> > > > (UK 01384 296191), and has been found to be clean from any virus
> > > > infection.
> > > >
> > > > Virus queries - PC Tech Support (09 3521)
> > > > E-mail system - External Postmaster (09 3673).
> > > >
> > > > ================================================================
> > > **********************************************************************
> > > This email and any files transmitted with it are confidential and
> > > intended solely for the use of the individual or entity to whom they
> > > are addressed. If you have received this email in error please notify
> > > the system manager.
> > >
> > > This footnote also confirms that this email message has been swept by
> > > MIMEsweeper for the presence of computer viruses.
> > >
> > > www.mimesweeper.com
> > > **********************************************************************
> > >
> **********************************************************************
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they
> are addressed. If you have received this email in error please notify
> the system manager.
>
> This footnote also confirms that this email message has been swept by
> MIMEsweeper for the presence of computer viruses.
>
> www.mimesweeper.com
> **********************************************************************