Question & Answer
Question
Why are errors sometimes encountered during Inventory File Expiration?
Answer
During Expiration processing of a node errors may be seen as in the following example.
12/11/12 02:39:18 ANR0813I Inventory file expiration process 234 canceled prior to completion: examined 28971666 objects, deleting 10072515 backup objects, 18762 archive objects, 0 DB
backup volumes, and 0 recovery plan files. 10 errors were encountered. (SESSION: 71587, PROCESS: 234)
The errors in this informational message are typically due to locking contention where expiration could not get the lock on an object. There will be no prior error messages in the activity log indicating a locking issue. The lock may be held by another process or a client backup session. The next time expiration runs, the objects most likely would not be locked and would be expired.
Locking contention can occur between processes such as expiration, client backups, migration, and reclamation.
Note: Expiration using a duration parameter will cause the process to cancel. The cancel in this case is normal.
[{"Product":{"code":"SSGSG7","label":"Tivoli Storage Manager"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Server","Platform":[{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"},{"code":"PF025","label":"Platform Independent"}],"Version":"All Supported Versions","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]
Product Synonym
TSM ADSM ITSM IBM Spectrum Protect
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21628740