IBM Support

Expire inventory process appears to hang while processing grouped objects

Troubleshooting


Problem

The expiration process runs and processes a node with a large amount of grouped objects. While processing the node, the query process shows no progress for the expiration process and appears to hang.

Symptom

Start the expiration process for the affected node using the expire inventory command. For example :

expire inventory node=large_node_name

The process starts, but the "query process" does not show progress for the examined or deleting objects fields. For example, the values remain at 0 for a long period of time :

499 Expiration Processed 1 nodes out of 1 total nodes, examined 0 objects, deleting 0
backup objects, 0 archive objects, 41 DB backup volumes, 1 recovery
plan files; 0 objects have been retried and 0 errors encountered.

Cause

Working as designed. During expiration and deletion of grouped object, the "query process" will only show the updated number after finishing processing the complete group. For a group with a large amount of group members, it is possible for the "query process " to report the same number of examined object and deleting object remain the same for a long time.

Resolving The Problem

The following steps can be used to monitor the expiration and deletion progress.

1: Obtain the nodeid value for the affected node.

Logon with the instance userid and run the following commands :

db2 connect to tsmdb1
db2 set schema tsmdb1
db2 "select nodeid from nodes where nodename='NODENAME'

Replace NODENAME with the appropriate affected nodename in uppercase.

2: Obtain the group members information using the following command :

db2 "select groupid,count(*) from backup_objects where nodeid=NNN group by groupid"

Replace NNN with the nodeid obtained from step 1.

In one example, the output showed the following group id and member information :

GID Member
1087295900 4379146
1100883004 3648876
1145673238 3608874
1138291739 3606380
1120218360 3523474
1112036237 3467689
1106246815 3433209
1057070616 2336812


3: Run the same command as in step2 after 30 minutes and compare the new output with the previous one. In this case, it shows the member count was decreased for one group. For example :


GID Member
1087295900 4379146
1100883004 3648876
1145673238 3608874
1138291739 3606380
1120218360 3523474
1112036237 3467689
1106246815 3433209
1057070616 2196572


In this last output, group id "1057070616" has a member count that was decreased from 2336812 to 2196572.

Run the same command from step 3 to continue monitoring the group members deletion.

[{"Product":{"code":"SSGSG7","label":"Tivoli Storage Manager"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Server","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Supported Versions","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
17 June 2018

UID

swg21976630