db2adutl delete inactive backups

[jailer]

We have DB2 backups that are inactive. We can view them using:
"db2adutl query full DB ldap2 verbose show inactive"
it will show
Retrieving FULL DATABASE BACKUP information.
1 Time: 20190804190503 Oldest log: S0003900.LOG DB Partition Number: 0 Sessions: 2 Mgmt Class: LX-2-0-0
2 Time: 20190803190503 Oldest log: S0003899.LOG DB Partition Number: 0 Sessions: 2 Mgmt Class: LX-2-0-0
3 Time: 20190802190503 Oldest log: S0003898.LOG DB Partition Number: 0 Sessions: 2 Mgmt Class: LX-2-0-0
4 Time: 20190801190504 Oldest log: S0003897.LOG DB Partition Number: 0 Sessions: 2 Mgmt Class: LX-2-0-0
5 Time: 20190731190504 Oldest log: S0003896.LOG DB Partition Number: 0 Sessions: 2 Mgmt Class: LX-2-0-0
6 Time: 20190707190509 Oldest log: S0003870.LOG DB Partition Number: 0 Sessions: 2 Mgmt Class: LX-2-1-30
7 Time: 20190706190509 Oldest log: S0003869.LOG DB Partition Number: 0 Sessions: 2 Mgmt Class: LX-2-1-30
8 Time: 20190705190509 Oldest log: S0003868.LOG DB Partition Number: 0 Sessions: 2 Mgmt Class: LX-2-1-30
... <snip>
16 Time: 20190627190503 Oldest log: S0003860.LOG DB Partition Number: 0 Sessions: 2 Mgmt Class: LX-2-1-30
17 Time: 20190627133828 Oldest log: S0003859.LOG DB Partition Number: 0 Sessions: 2 Mgmt Class: LX-2-1-30


The first 5 backups are active, 6-17 are inactive and only show up when the show inactive clause is used.
We want to delete numbers 6-17. However the command:
"db2adutl delete full DB ldap2 verbose older than 10 days"
Shows "Nothing to delete."

We can't delete them by name; (db2adutl delete full TAKEN at 20190703190508) - appears to work but the backup doesn't go away.
Trying to delete using the "older than days" clause doesn't work either. We don't seem to be able to affect "inactive" backups. Anyone have any ideas? We are running TM server 7.4 with an ancient version of SuSe 11.3

Thanks in advance.
Pete.

 

[mahmoudkafafi]

Hello,
I am not that much knowledgeable about DB2 ,but have you check if the same version could be selected form the "BACKUPS" table in the TSM DB ?
we may need to verify if the issue from the TSM side or DB2 side,
moreover
what could be found in the "actlog" when you performed the "db2adutl delete"?
thanks

 

[jailer]

Hello,
The actlog shows nothing other than the connection was made. However, I can issue: "select substr(LL_NAME,1,30) as LL_NAME, FILESPACE_ID, CLASS_NAME from backups where NODE_NAME='XXXX' and FILESPACE_NAME='/XXXX' and STATE='INACTIVE_VERSION' order by LL_NAME' " and see every backup that I want to delete. If I do delete them what related tables would need to be cleaned up? Would the physical backup & logs be removed? I'm guessing that the OBJECT_ID references the physical backup.
Thank you for your reply.

 

[mahmoudkafafi]

Hello ,
Playing with OBJECT_ID is so critical , and if it must go like that , I would recommend to open a case with IBM support .
meanwhile if you still have time, a "SERVICE" and "API" trace flags may be help to tell what happens in the background while deleting the backup with db2adult

 

[jailer]

Thankx