IT00231: SERVER CAN REPORT "ANR9999D_0257577322 FORCETSMAPPLICATIONSTHREAD" IF REORG IS TOO LONG IN LOCK-WAIT

APAR status

• Closed as program error.

Error description

• Following messages can be logged in the server activity log:
  
  ANR9999D_0257577322 ForceTSMApplicationsThread(tbreorg.c:
   5866) Thread<48>: Error occurred but reorg still in
   lockwait. Forcing the reorg, agentId 14170, rc = 0.
  ANR9999D Thread<48> issued message 9999 from:
  ANR9999D Thread<48>  000007FEE65A9809 OutDiagToCons()+159
  ANR9999D Thread<48>  000007FEE65A31CA outDiagfExt()+11a
  ANR9999D Thread<48>  000007FEE634DDA7
   RdbReorgHasForcedAppl()+19b7
  
  ANR9999D_1153344844 HandleDb2ReorgErrors(tbreorg.c:7244)
   Thread<105>: Reorg(IdxStart)(flags 0x0) for
   "TSMDB1"."AS_SEGMENTS" failed with sqlca.code -1224,
   reasonCode 0.
  ANR9999D Thread<105> issued message 9999 from:
  ANR9999D Thread<105>  000007FEE65A9809 OutDiagToCons()+159
  ANR9999D Thread<105>  000007FEE65A31CA outDiagfExt()+11a
  ANR9999D Thread<105>  000007FEE634E46C
   RdbReorgHasForcedAppl()+207c
  ANR9999D Thread<105>  000007FEE634F21F
   RdbReorgHasForcedAppl()+2e2f
  ANR9999D Thread<105>  000007FEE634F557
   RdbReorgHasForcedAppl()+3167
  ANR9999D Thread<105>  000007FEE5D46384 startThread()+124
  ANR9999D Thread<105>  0000000074611D9F endthreadex()+43
  ANR9999D Thread<105>  0000000074611E3B endthreadex()+df
  ANR9999D Thread<105>  00000000772C652D
   BaseThreadInitThunk()+d
  ANR9999D Thread<105>  00000000774FC541
   RtlUserThreadStart()+21
  
  This can happen if the database reorganization process has a
  lock conflict with other server transactions. DB2 cannot swap
  the reorganized rows with the un-reorganized rows when there is
  a read-only transaction on the table of interest, so the
  reorganization process goes into a lock-wait state. However
  reorganization can hold other locks on that table and that will
  prevent Tivoli Storage Manager server read-write transactions
  from obtaining exclusive locks on that table and the read-write
  transaction goes into lock-wait state, effectively resulting in
  a deadlock. In case when there is a deadlock, some transactions
  need to be aborted to resolve condition. The method for the
  lock-wait resolution is to cancel Tivoli Storage Manager server
  transactions, starting with the oldest read-only transaction,
  then verify if the lock-wait condition has been resolved, if not
  select and cancel the second oldest transaction and so forth
  until all of the related transactions are forced. After all
  server transactions have been forced and if DB2 is still
  reporting that reorganization is in lock-wait condition, then
  the final option is to force the reorganization itself.
  
  The ANR9999D message logged in this case is mis-leading, as this
  behaviour is expected.
  
  In this case the table AS_SEGMENTS was affected, however this
  can happen with any table that is currently being reorganized.
  
  TSM Versions Affected:
  Tivoli Storage Manager server 6.2, 6.3, 7.1 on all platforms.
  
  Initial Impact:
  Low
  
  Additional Keywords:
  TSM zz63 zz71 ForceTSMApplicationsThread HandleDb2ReorgErrors
  RdbReorgHasForcedAppl
  

Local fix

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.3.5 and 7.1.1. Note that   *
  * this is subject to change at the discretion of IBM.          *
  ****************************************************************
  

Problem conclusion

• This problem was fixed.
  Affected platforms:  AIX, HP-UX, Solaris, Linux, and Windows.
  
  A new message will be issued.
  -----------
  ANR3549W Reorganization was canceled because of a conflicting
  lock on
  table <table name>.
  ___________
  

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

• R63A PSY

     UP

• R63H PSY

     UP

• R63L PSY

     UP

• R63S PSY

     UP

• R63W PSY

     UP

• R71A PSY

     UP

• R71H PSY

     UP

• R71L PSY

     UP

• R71S PSY

     UP

• R71W PSY

     UP