Hi Reinhard,
We get these messages spasmodically (we had them at 3.1 and still
get them at 3.7.3 as well). Also I think Hanna Hahne reported
earlier this year as well. They occur only with archived files.
I did have a PMR a few months ago but it went nowhere because I
couldn't reproduce at will and couldn't get the tracing required.
So stalemate. [The PMR was 06414; I think Hanna also tried the
PMR route ...]. I have to hope they are not harmful!
When I find EXPIRE INVENTORY taking longer than usual I increase
the DB bufferpool size and that usually does the trick : I find
this a more accurate measure (with a large DB) than looking at
the 'Cache Hit Pct' metric, which is always well over 99% here.
Best regards, Sheelagh
--
>MIME-Version: 1.0
>Content-Transfer-Encoding: 7bit
>Date: Tue, 5 Sep 2000 08:27:08 +0200
>From: Reinhard Mersch <[EMAIL PROTECTED]>
>Subject: Long running expiration / Object already expired
>To: [EMAIL PROTECTED]
>
>Hello,
>
>on our ADSM server (3.1.2.57 on AIX), EXPIRE INVENTORY is currently
>runnning much longer than usual and issuing a lot of messages of the form
>
>ANR9999D imarqry.c(2004): Object 0.a3f74b4 of type 1 is already expired
>
>Has anybody seen this and know what that means?
>
>--
>Reinhard Mersch Westfaelische Wilhelms-Universitaet
>Zentrum fuer Informationsverarbeitung - ehemals Universitaetsrechenzentrum
>Roentgenstrasse 9-13, D-48149 Muenster, Germany Tel: +49(251)83-31583
>E-Mail: [EMAIL PROTECTED] Fax: +49(251)83-31653
Sheelagh Treweek
Oxford University Computing Services
Email: [EMAIL PROTECTED]
Phone: +44 (0)1865 273205 Fax:-273275
