I would assume that it's expiration. I would make sure you have expiration
running regularly, and that it's not running up against a duration limit.
You can run expiration for specific clients, which will help cut down the
run time for it.

On Fri, May 02, 2014 at 12:52:08PM +0000, Rick Adamson wrote:
> TSM 6.3.4 on Windows.
> Recently I found that our DB2 clients were not expiring old backups and some 
> systems had accumulated them for some time.
> After the DBA's have corrected the situation on a particular machine and I 
> query the Backups table all of the objects are still reported, even though 
> the Occupancy table and DB2 client show the reduction.
>
> Does anyone know what triggers the update to the backups table to purge the 
> old object records?
>
> TIA
>
> -Rick Adamson

--
-- Skylar Thompson (skylar2 AT u.washington DOT edu)
-- Genome Sciences Department, System Administrator
-- Foege Building S046, (206)-685-7354
-- University of Washington School of Medicine