Update for inquiring minds...
Unfortunately this problem has not been resolved yet. I have been trying to
avoid a database audit due to the prolonged potential ADSM outage that would
be entailed. (At least a week according to IBM support for a 24 GB database
on NT.) I received a test fix earlier, but it did not resolve the problem.
So I'm patiently waiting for either my ADSM server to implode upon itself
(It has about 2-3 more days of DB capacity) or the receipt of another fix
that will allow me to expire inventory.
Christopher Bushman
NT Technical Services
AMP Incorporated
81(0-2589)
cbushman AT amp DOT com
> -----Original Message-----
> From: Dan Giles [SMTP:Dan_Giles AT MANULIFE DOT COM]
> Sent: Monday, June 22, 1998 10:58 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Occupancy went negative
>
> I'm a little behind on the newsgroup, but scanning ahead slightly I
> haven't seen
> any more references to this problem.
>
> If this hasn't been resolved yet, I would recommend doing a database
> audit. (Use
> FIX=NO the first time through to find out what it's going to do to you!)
> If
> errors show up, contact ADSM support to find out how you should proceed.
> If
> there are errors, and you don't have software support with ADSM, then you
> can
> try the FIX=YES, or restore from a previous version of the DB backup
> before this
> error started.
>
>
>
>
>
> From: Eric van Loon <evanloon AT KLM DOT NL> on 06/16/98 02:22 PM GMT
>
> Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> To: ADSM-L AT VM.MARIST DOT EDU
> cc: (bcc: ADSM)
> Subject: Re: Occupancy went negative
>
>
>
>
> Hi Christopher!
> What is the result from a DELETE VOLUME 208 DISCARDDATA=YES?
> Kindest regards,
> Eric van Loon
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
> Bushman, Christopher M
> Sent: Tuesday, June 16, 1998 13:52
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Occupancy went negative
>
> Eric,
> That was my initial thought also, but volume 208 does not exist. All our
> storage volumes are labeled using a six character alpha-numeric label. Is
> it possible that this is an internal ADSM reference to a particular
> filespace or volume?
> -----Original Message-----
> From: Eric van Loon [SMTP:evanloon AT KLM DOT NL]
> Sent: Tuesday, June 16, 1998 6:32 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Occupancy went negative
> Hi Christopher!
> Have you tried a "AUDIT VOLUME 208 FIX=YES"?
> Kindest regards,
> Eric van Loon
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On
> Behalf
> Of
> Bushman, Christopher M
> Sent: Monday, June 15, 1998 19:34
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Occupancy went negative
>
> Hello ADSM'ers,
> I'm in a bit of a bind here. I have a V2 ADSM server running
> under
> windows
> NT. My daily processes usually begin with an expiration, but
> lately
> this
> message appears in the Activity Log. Has anyone else experienced
> this
> problem or know of any solution. So far, IBM second level is
> looking into
> the problem, but I haven't gotten a definitive response yet. I'm
> starting
> to get a little concerned due to the database growth rate since
> this
> problem
> arose.
> 06/15/1998 06:00:06 ANR9999D aftxn.c(855): Cluster occupancy went
> negative
> for
> Volid=208, Ck1=51, Ck2=2, PoolId=-1.
> 06/15/1998 06:00:06 ANR1181E aftxn.c190: Data storage transaction
> 0:141096280
> was aborted.
> 06/15/1998 06:00:06 ANR2183W imexp.c1871: Transaction 0:141096280
> was
> aborted.
> 06/15/1998 06:00:06 ANR0865E Expiration processing failed -
> internal server
> error.
> 06/15/1998 06:00:06 ANR0860E Expiration process 21 terminated due
> to
> internal
> error: deleted 3 backup files and 0 archive
> files.
> Any suggestions would be greatly appreciated,
> Christopher Bushman
> NT Technical Services
> AMP Incorporated
> 81(0-2589)
> cbushman AT amp DOT com
|
