ADSM-L

Occupancy went negative

2015-10-04 17:57:46
Subject: Occupancy went negative
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
To: ADSM-L AT VM.MARIST DOT EDU
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
<Prev in Thread] Current Thread [Next in Thread>