Expiration doesnt run for some nodes.

Hi All,

Many times i have seen this during node by node expiration that the expiration process starts for a particular node but doesn't do anything and completes successfully , even without inspecting objects for that node.
Due to this data is getting increased for those nodes.
Could someone please explain this behavior of tsm.

tsm: xxxxx>expi I beginnodeid=289 endnodeid=289
ANS8003I Process number 12881 started.


12,881 Expiration Examined 8 objects, deleting 0 backup objects, 0
archive objects, 0 DB backup volumes, 0 recovery
plan files; 0 errors encountered.


tsm: xxxxxx>q ac s=12881


Date/Time Message
-------------------- ----------------------------------------------------------
04/10/13 11:17:52 ANR0984I Process 12881 for EXPIRE INVENTORY started in the
BACKGROUND at 11:17:52. (SESSION: 1602920, PROCESS:
12881)
04/10/13 11:17:52 ANR0811I Inventory client file expiration started as
process 12881. (SESSION: 1602920, PROCESS: 12881)
04/10/13 11:17:52 ANR2369I Database backup volume and recovery plan file
expiration starting under process 12881. (SESSION:
1602920, PROCESS: 12881)
04/10/13 11:18:07 ANR0812I Inventory file expiration process 12881
completed: examined 8 objects, deleting 0 backup objects,
0 archive objects, 0 DB backup volumes, and 0 recovery
plan files. 0 errors were encountered. (SESSION: 1602920,
PROCESS: 12881)
04/10/13 11:18:07 ANR0985I Process 12881 for EXPIRE INVENTORY running in the
BACKGROUND completed with completion state SUCCESS at
11:18:07. (SESSION: 1602920, PROCESS: 12881)
04/10/13 11:18:15 ANR2017I Administrator xxxxx issued command: QUERY ACTLOG
s=12881 (SESSION: 1602920)




Thanks,
Harsh.