[no subject]

ADSM NT Ver 3.1.2.1
NT SP4

Hi,

We've got the following problem when running expiration:

11/11/1999 08:00:17  ANR2017I Administrator ADMIN issued command: EXPIRE

                      INVENTORY
11/11/1999 08:00:17  ANR0984I Process 59 for EXPIRE INVENTORY started in
the
                      BACKGROUND at 08:00:17.
11/11/1999 08:00:17  ANR0811I Inventory client file expiration started
as
                      process 59.
11/11/1999 08:00:17  ANR2756I Scheduled command EXPIRATION started
                      successfully.
11/11/1999 08:00:18  ANR9999D aferase.c(528): Invalid logSizeRatio
                      134209777.062500 (logSize=0.6664, size=0.32,
                      aggrSize=0.261126) for aggregate 0.3443736.
11/11/1999 08:00:18  ANR9999D imutil.c(1197): Error deleting object (0
3320353)
11/11/1999 08:00:18  ANR9999D imexp.c(1350): Error 19 deleting expired
11/11/1999 08:00:18  ANR9999D imexp.c(1350): Error 19 deleting expired
object
                      (0 3320353) - deletion will be re-tried.
11/11/1999 08:00:18  ANR9999D bftxn.c(238): BF commit prohibited -
transaction
                      failed.
11/11/1999 08:00:18  ANR1181E bftxn.c242: Data storage transaction
0:72891846
                      was aborted.
11/11/1999 08:00:18  ANR2183W imexp.c2629: Transaction 0:72891846 was
aborted.
11/11/1999 08:00:18  ANR2369I Database backup volume and recovery plan
file
                      expiration starting under process 59.
11/11/1999 08:00:18  ANR0860E Expiration process 59 terminated due to
internal
                      error: examined 322 objects, deleting 32 backup
objects,
                      0 archive objects, 0 DB backup volumes, and 0
recovery
                      plan files. 0 errors were encountered.
11/11/1999 08:00:18  ANR0987I Process 59 for EXPIRE INVENTORY running in
the
                      BACKGROUND processed 32 items with a completion
state of
                      SUCCESS at 08:00:18.

Has anyone seen this before and/or know how to fix this.  We've tried
doing a full backup and restore of the ADSM Database without any
success.  I'm busy downloading the latest fixes for the ADSM Server and
will install that and see if that resolve the problem.

Thanks and regards
Gerrit van Zyl