Question & Answer
Question
While performing simultaneous operation such as backup, migration, reclamation and DB reorganization (6.x only), following deadlock detection messages might be logged and an operation is aborted. ANR0379W A server database deadlock situation has been encountered (5.5) ANR0159E Database deadlock detected (6.x) I would like to know how to avoid such deadlocks.
Cause
Tivoli Storage Manager adopts multithread processing and it enables to process multiple jobs at the same time.
And it also allows to perform operations effectively.
However by the nature of the multithread processing, a number of thread might access database data simultaneously and a deadlock might be happened.
In this case, above messages are logged and a process is aborted to help other processes continue.
Answer
The operation is usually succeeded when it is reexecuted. This is a limitation while using Tivoli Storage Manager.
To avoid the unexpected deadlocks completely, you need to coordinate number of concurrent operations in advance or reduce the number of concurrent operations.
Product Synonym
tsm
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21666399