[I wrote the following on 27 July, but from an ID caused the post
    to be rejected .. wts]

Quoting Gerrit van Zyl <gvanzyl AT FARITEC.CO DOT ZA>:
> Im receiving the following DB errors (during expiration and sometimes
> when deleting a volume) and I would like to know if a backup - delete -
> restore of the database will resolve this problem or a audit of the DB
> or any other recommendations?
>
> Aix ver 4.3.2
> ADSM Server ver 3.1.2.50
...
> 07/21/00   06:00:58  ANR9999D imutil.c(1296): Error deleting object
(0
>                       88937611)
...
> 07/21/00   06:28:02  ANR0104E astxn.c(1266): Error 2 deleting row
from
> table
>                       "AS.Volume.Status".
> 07/21/00   06:28:02  ANR1181E astxn.c356: Data storage transaction
> 0:2702006
>                       was aborted.
> 07/21/00   06:28:03  ANR9999D imexp.c(4202): Expiration Delete
> Transaction
...

In my limited experience, (1) don't release any DB backups until this
is resolved, (2) get thee to ADSM Customer support, and (3) be firm
that the problem must be resolved and without a DB audit (unless you
really can afford one!).  This method has worked for me in the past.
However, ...

Unable to correct one problem (it also had "error 2 deleting row" (of
same table)), I was able to bypass it by marking the tapes being used
at the time of the problem as READONLY.  That was back in V2, but
even today if I allow ADSM 3.1.2.50 to write on any of those tapes, I
still/again get this error.  Guess I should follow my own advice in (2)
above, but the simple bypass (in my case) makes me not want to
"waste" time really correcting the DB.

Hope this helps,

Wayne T. Smith                          ADSM AT Maine DOT edu
ADSM Technical Coordinator - UNET       University of Maine System