IC62978: ARCHIVE LOGS GROW RAPIDLY AND CAN CAUSE THE SERVER TO KEEP CRASHING DUE TO THE DB2 REORG OPERATION RUNNING TOO FREQUENTLY.

IBM Tivoli Storage Manager (TSM) server V6.1.2.x interim fix downloads
IBM Tivoli Storage Manager V6.1 Fix Pack 3 (6.1.3) Server Downloads

APAR status

• Closed as program error.

Error description

• Problem Description:
  Currently, the REORG operation runs daily. In some cases the
  operation can heavily write to the logs.  This can cause the
  Tivoli Storage Manager server to frequently crash for two
  reasons:
  1. The archive log volume can fill up the disk which can then
  fill up the active log volume. In this case, the server will not
  be able to start until the procedure in the following technote
  is followed:
  http://www-01.ibm.com/support/docview.wss?uid=swg21394424
  
  2. When REORG runs during long transactions on the server, the
  transaction can exceed the NUM_LOG_SPAN value and crash the
  server. This value is the number of logs a single transaction
  can use.
  The db2diag.log (hidden file) will reveal messages about the
  disk being full or num_log_span value was exceeded.
  Tivoli Storage Manager Versions Affected:
  All 6.1 versions
  Initial Impact: Medium
  Additional Keywords:
  reorg archive logs crash frequently zz61
  

Local fix

• The temporary fix would be to disable reorg until a fix is
  available. Edit the dsmserv.opt file to add the following option
  and restart the TSM server.
  ALLOWREORGTABLE NO
  Refer to the DB2 manual on more information about the REORG
  operation.
  

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

Problem conclusion

• This problem was fixed.
  
  Affected platforms:  AIX, HP-UX, Sun 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

• R61A PSY

     UP

• R61H PSY

     UP

• R61L PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP