IC81015: TIVOLI STORAGE MANAGER SERVER REORGANIZES TABLES AND INDICES OF TABLES THAT DON'T NEED REORGANIZING

APAR status

• Closed as program error.

Error description

• The Tivoli Storage Manager server currently does an initial
  unconditional reorganization on all
  tables (if table reorg is enabled) and all indices on all tables
  (if index reorg is enabled).  Some tables are extremely
  large and don't need to be reorganized, but are being
  reorganized anyway consuming considerable system resource.
  Reorganization processing will be updated to only perform
  reorganization when indicated by the actual database criteria.
  
    Tivoli Storage Manager Versions Affected: all V6
    Initial Impact: Low
    Additional Keywords: ZZ61 ZZ62 ZZ63 TSM REORG
  

Local fix

• Local Fix for table reorganization:
  To stop a table reorganization and prevent it from starting
  unless the database manager indicates that
  it should restart, first determine the table name:
  db2 connect to tsmdb1
  db2 set schema tsmdb1
  db2pd -d tsmdb1 -reorg
  
  Tables that are in running state or in paused state are eligible
  to be stopped.  <TABLENAME> is indicated in the subsequent
  instructions for such a table.   <TIMESTAMP> is the current date
  and time
  in the format YYYY-MM-DD-HH.MM.SS.
  
  db2 "delete from global_attributes where owner='RDB' and name
  ='REORG_TB_<TABLENAME>' "
  db2 "insert into global_attributes
         (owner,name,type,length,datetime)
         values('RDB','REORG_TB_<TABLENAME>',5,6,'<TIMESTAMP>' )"
  
  db2 "reorg table <TABLE_NAME> inplace stop"
  
  Note that if message
  SQL2219N  The specified INPLACE table reorganization action on
  table
  "TSMDB1.<TABLE_NAME>" is not allowed on one or more nodes.
  Reason code: "11"
  is displayed, this means that the reorg has already finished,
  and no further action is needed.
  
  Local Fix for index reorganization:
  To stop index reorganization for a table and prevent it from
  starting unless the database manager indicates that
  it should restart, first determine the table name:
  db2 connect to tsmdb1
  db2 set schema tsmdb1
  db2pd -d tsmdb1 -reorg index
  
  Examine the reorg index section of the output.
  Tables that are in running state or in paused state are eligible
  to be stopped.  <TABLENAME> is indicated
  in the subsequent instructions for such a table.   <TIMESTAMP>
  is the current date and time
  in the format YYYY-MM-DD-HH.MM.SS.
  
  To cancel an index reorganization through DB2:
  First update the global attributes for the indices of the table:
  db2 "delete from global_attributes where owner='RDB' and name
  ='REORG_IX_<TABLENAME>' "
  db2 "insert into global_attributes
         (owner,name,type,length,datetime)
         values('RDB','REORG_IX_<TABLENAME>',5,6,'<TIMESTAMP>' )"
  
  
  Following these instructions to actually cancel the index reorg.
  
     1. Determine the application ID of the reorganization
  process, by issuing the following commands in a DB2 Command Line
  Processor window:
           a. db2 connect to tsmdb1
           b. db2 get snapshot for all applications
  >application.out
     2. Examine the application.out file and find the "Most recent
  operation" entry like this:
        Most recent operation = Reorganize
        If that line isn't there, look for an entry like this:
        Application name = db2reorg
     3. Scroll backwards until finding the "Application handle"
  entry. It will look like something like this:
        Application handle = NNNNN (where NNNNN is the actual
  application handle)
        Ensure that the correct application handle is found.
     4. Issue the following command in the DB2 Command Line
  Processor Window substituting in the actual application handle
  in for NNNNN:
        db2 "force application (NNNNN)"
     5. Because the nature of the command being canceled and that
  the DB2 FORCE APPLICATION command is asynchronous, it might take
  up to 30 minutes for the process to be canceled.
     6. To verify that it has been canceled, issue steps 1b and 2
  again. If there is no "Most recent operation" of type Reorganize
  message displayed, it has been canceled.
  

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

Problem conclusion

• This problem was fixed.
  
  See Technote 1580621 for Local Fix Information.
  http://www.ibm.com/support/docview.wss?uid=swg21580621
  
  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

• R61A PSY

     UP

• R61H PSY

     UP

• R61L PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• 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