Perhaps it's a timing issue.  For DB2 you have to issue "db2adutl delete
older than x days without prompting" otherwise DB2 will keep backups
forever.  In TSM you run "expire inventory".  Both are necessary to remove
all pieces of the db2 backup.  Perhaps for this database you run the DB2
command AFTER the TSM one.  This would allow a not so short period of time
where you are able to display these "expire immediate" objects.

Date:    Sun, 7 Oct 2007 12:36:01 -0400
From:    Daad Ali <daad_l AT YAHOO DOT CA>
Subject: Re: Deleted DB2 backup still in TSM

Thanks Richard,
 =20
 Yes, I am running expire inventory daily. And I don't see anything in t=
he activity log that would indicate that the expiration is not working.
 =20
 DESCRIPTION: Daily Script to run Expiration process to remove expired d=
ata
     COMMAND: expire inventory wait=3Dno
    PRIORITY: 5
   STARTDATE: 2003-01-18
   STARTTIME: 23:00:00
    DURATION: 1
    DURUNITS: HOURS
      PERIOD: 1
    PERUNITS: DAYS
   DAYOFWEEK: ANY
  EXPIRATION:
      ACTIVE: YES
    CHG_TIME: 2003-07-25 08:43:52.000000
   CHG_ADMIN: BBROWN
     PROFILE:
 SCHED_STYLE: CLASSIC
   ENH_MONTH:
  DAYOFMONTH:
 WEEKOFMONTH:


Richard Sims <rbs AT BU DOT EDU> wrote:
 On Oct 6, 2007, at 7:30 AM, Daad Ali wrote:

...
1- Is there a way of restoring these database backups?

If it's expired, it's beyond your retrieval capability: the only
recourse is to restore your TSM system to some time in the past,
which is unpalatable, if even possible to the point you may need.

2- Since they are deleted from the client , how do I remove it from
showing up in TSM.

Are you running Expire Inventory regularly, and allowing it to run to
completion? I would expect that operation to remove the entries from
the database. If not, see if any issues reflected in your Activity Log.

Richard Sims