IC80584: MOVE DRMEDIA ORPHAN TRANSACTION HANG SEQUENTIAL VOLUME HISTORY

APAR status

• Closed as program error.

Error description

• Unexpected or internal server errors during DRM operations like
  MOVE DRMEDIA can result in orphan transactions which causes
  future interactions with sequential volume history to hang.
  Here are some examples of operations that can be impacted if
  this problem occurs:
  QUERY VOLHISTORY, DELETE VOLHISTORY, CHECKIN LIBV
  Assigning a SCRATCH volume to a storage pool
  Emptying a storage pool volume and returning to SCRATCH
  BACKUP DB, GENERATE BACKUPSET, EXPORT SERVER, EXPORT NODE
  Library Manager changing ownership of Library Client volumes
  Customer/L2 Diagnostic:
  A prior DRM process may log error messages similar to the
  following in the Tivoli Storage Manager server activity log:
  12/15/2011 09:00:07 ANR2017I Administrator ADMIN issued
  command:
  MOVE DRMEDIA *dbbackup* wherestate=VAULTRetrieve
  tostate=ONSITERetrieve
  ANR4513E A database lock conflict was encountered in
  processing sequential volume history information.
  ANR2033E MOVE DRMEDIA: Command failed - lock conflict.
  SHOW TXNT and SHOW THREADS can be used to identify an orphan
  transaction.  An orphan transaction is a transaction listed
  by SHOW TXNT where the corresponding thread no longer exists
  and is not listed in the output of SHOW THREADS.
  Here is an example of a transaction:
  Tsn=0:9780294, Resurrected=False, InFlight=True,
    Distributed=False, Persistent=True, Addr 0x1885f18
    Start ThreadId=856297, Timestamp=12/15/2011 09:00:07 AM,
    Creator=ormadm.c(3010)
    Last known in use by ThreadId=856297
  If Thread 856297 is not in SHOW THREADS, the transaction is
  orphaned.  The Timestamp of that transaction can be used to
  correlate to the activity log to get more context.
  Versions Affected:
  Tivoli Storage Manager 6.1, 6.2 and 6.3 on all platforms
  Initial Impact:
  Medium
  

Local fix

• Recycle/restart the Tivoli Storage Manager Server to clear the
  orphan transaction.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Tivoli Storage Manager server users.     *
  ****************************************************************
  * PROBLEM DESCRIPTION: See ERROR DESCRIPTION.                  *
  ****************************************************************
  * RECOMMENDATION: Apply fixing level when available.           *
  *                 This problem is currently projected to be    *
  *                 fixed in levels 6.2.4 and 6.3.1.             *
  *                 Note that this is subject to change at       *
  *                 the discretion of IBM.                       *
  ****************************************************************
  *
  

Problem conclusion

• The described problem has been resolved.
  
  AFFECTED PLATFORMS:
  AIX, HP-UX, Solaris, Linux, and Windows.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  TSM SERVER

• Fixed component ID

  5698ISMSV

Applicable component levels

• R62A PSY

     UP

• R62H PSY

     UP

• R62L PSY

     UP

• R62S PSY

     UP

• R62W PSY

     UP

• R63A PSY

     UP

• R63H PSY

     UP

• R63L PSY

     UP

• R63S PSY

     UP

• R63W PSY

     UP