Re: Occupancy went negative
2015-10-04 17:57:46
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
|
|
|