ADSM-L

Re: Expiration Problems with 3.1.2.13

1999-02-11 14:16:02
Subject: Re: Expiration Problems with 3.1.2.13
From: Joel Fuhrman <joelf AT CAC.WASHINGTON DOT EDU>
Date: Thu, 11 Feb 1999 11:16:02 -0800
index.storsys.ibm.com:/adsm/fixtest/v3r1/aixsrv/3.1.2.13

IBM: Since 3.1.2.1 is not usable, please put a README.CRITICAL in the
release directory which explains the problem and where to find the patch
level if the customer decides to install 3.1.2.1

On Thu, 11 Feb 1999, Hilton Tina wrote:

> Why do I see the latest release of the server as 3.1.2.1 on the ftp site.
> Where is .13 at?
>
> > -----Original Message-----
> > From: Gogineni, Sri [SMTP:SGogineni AT CAISO DOT COM]
> > Sent: Wednesday, February 10, 1999 7:12 PM
> > To:   ADSM-L AT VM.MARIST DOT EDU
> > Subject:      Re: Expiration Problems with 3.1.2.13
> >
> > Hi Gerhard,
> >            I have a similar problem of not being able to cancel migration
> > and reclamation processes. However I do not have any problem with
> > expiration
> > at AIX 4.1.5
> > and 3.2.1.13 ADSM.
> >
> > Regards
> >
> > Sri
> >
> > -----Original Message-----
> > From: Gerhard Rentschler [mailto:g.rentschler AT RUS.UNI-STUTTGART DOT DE]
> > Sent: Wednesday, February 10, 1999 7:33 AM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Expiration Problems with 3.1.2.13
> >
> >
> > Hi,
> > this morning I upgraded ADSM 3.1.1.3 on AIX to 3.2.1.13.
> > Everything seemed to be fine until I started expire inventory.
> > First interesting info in actlog is the following:
> >
> > 10.02.1999 15:28:41 ANR0104E imarins.c(1303): Error 2 deleting row from
> > table "Archive.Descriptions".
> > 10.02.1999 15:28:41 ANR9999D imutil.c(1161): Error deleting object (0
> > 18097336)
> > 10.02.1999 15:28:41 ANR9999D imexp.c(1350): Error 8 deleting expired
> > object (0 18097336) - deletion will be re-tried.
> > 10.02.1999 15:28:41 ANR0104E imarins.c(1303): Error 2 deleting row from
> > table "Archive.Descriptions".
> >
> > This looks very much like APAR IX79626 which I thought is fixed since
> > 3.1.2.0. Could it be that it slipped in again?
> > What makes the situation worse is the fact that the expiration process
> > went into a loop. Cancelling the process did not work. The q proc
> > command shows "expiration Cancel in Progress".
> > What can I do?
> > Best regards
> > Gerhard
> > ---
> > Gerhard Rentschler            email:g.rentschler AT rus.uni-stuttgart DOT de
> >
> > Regional Computing Center     tel.   ++49/711/685 5806
> > University of Stuttgart       fax:   ++49/711/682357
> > Allmandring 30a
> > D 70550
> > Stuttgart
> > Germany
>
<Prev in Thread] Current Thread [Next in Thread>