I had the same problem about 3 weeks ago when I upgraded to Version
3 where my expire inventory would fail after getting about 50% through the
database. Once support assisted me with finding the bad filespace, we had to
rebind all of the objects in that filespace to a new management class that
had eternal retentions. This involved re-creating (touching, to make 0 byte
files) all of the files that the ADSM server had ever backed up, but no
longer existed on the client (so even "lone" inactive files would be rebound
to the new mgtclass).
        Once this was done, the expire inventory would complete
successfully. I then renamed that filespace so the client would start from
scratch on that filesystem.
        My problem now lies in trying to get rid of that bad filespace. When
I do a "delete file..." or "delete vol..." on that data, it tells me it has
to recalculate the storage pool occupancy (message ANR1278I) and then the
sever hangs hard. Nothing, except simple "query" commands or a "halt" will
work (not backups, restores, migrates, reclamations, etc). Support says I
will have to wait till this completes, but after letting it run for up to 4
hours, I had to halt the server. I can't afford a lot of downtime on this
server because we are a 24x7 manufacturing environment, so I am just leaving
that filespace alone for now.
        Any idea how long this may take on a 10GB database?

Ben