IBM Support

IT15176: "GENERATE BACKUPSET" MIGHT LOOK HUNG FOR VERY LARGE FILESYSTEMS WHILE RESETTING SEARCH BOUNDARIES.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Tivoli Storage Manager GENERATE BACKUPSET command is running
    very slow and might look hung when processing very large
    filesystems, even with the fix for IT07676
    installed. The symptom has been reported for a filesystem having
    70 million active objects.
    
    Customer/L2 Diagnostics:
    Looking at server instrumentation data, look for the
    ProcessNodes thread, the output might look like with the
    following example:
    
    Thread 397 ProcessNodesThread parent=396
    14:41:35.506-->15:02:28.319
    Operation       Count  Tottime  Avgtime  Mintime  Maxtime
    InstTput  Total KB
    ----------------------------------------------------------------
    ------------
    DB2 Reg Exec        2 1252.678  626,339  112.807 1139.870
    DB2 Reg Fetch    2001    0.114    0,000    0.000    0.000
    Unknown                  0.020
    ----------------------------------------------------------------
    ------------
    Total                 1252.813
    
    SHOW TXNT reports the ProcessNodes thread (with ThreadId 397)
    processing RegSqlId=0x0300000C, running a SELECT on the
    Backup.Ojects table:
    
    Tsn=0:75016, Resurrected=False, InFlight=True,
    Distributed=False, Persistent=True, Addr 0x7fff84000918
      Start ThreadId=397, Timestamp=20.08.2015 13:47:17,
    Creator=tbtbl.c(7051)
      Restart ThreadId=397, Timestamp=04.09.2015 03:52:15,
    Source=tbtbl.c(7212)
      End ThreadId=397, Timestamp=04.09.2015 03:52:15,
    Source=tmtxn.c(507)
      Last known in use by ThreadId=397
      Participants=2, summaryVote=Commit
      EndInFlight False, endThreadId 397, tmidx 0, processBatchCount
    0, mustAbort False.
        Participant DB: voteReceived=False, ackReceived=False
          DB: Txn 0x7fff24081aa8, ReadOnly(NO),
    connP=0x7fff24081878, applHandle=11285, openTbls=3:
          DB: --> OpenP=0x7fff240be4a8 for
    tempTable=(Backupset.Temp.Objects,BKSETOBJS).
          DB: --> OpenP=0x7fff3c083208 for table=Filespaces.
          DB: --> OpenP=0x7fff2c0387a8 for table=Global.Attributes.
          DB: --> RegSqlId=0x0300000C SELECT for
    table=Backup.Objects, executed(Yes).
        Participant IM: voteReceived=False, ackReceived=False
    
    A trace with traceflag OBJSET will show the delay (here: about
    80 minutes) for Thread 397 as with the following example:
    
    09:51:45.067 [397][imobjgen.c][3251][FindObjects]:re-executing
    reg sql
    09:51:45.067 [397][imobjgen.c][4755][SetResetSearch]:Resetting
    search bounds to nodeid=<NODEID>, fsid=<OBJID>,
    objtype=<OBJTYPE>, state=<STATE>
    09:51:45.067 [397][imobjgen.c][4804][SetResetSearch]:Setting
    search bounds in registered sql stmt 0x7fff24282128 input row
    0x7fff242821e8 to nodeid=<NODEID>, fsid=<FSID>,
    objtype=<OBJTYPE>, state=<STATE>.  lastobjid=<OBJID>.
    11:11:44.117 [397][imobjgen.c][3322][FindObjects]:found
    objId=<OBJID>
    
    Note that the trace snippet has been collected separately from
    the SHOW and instrumentation data above, so the timestamps do
    not match.
      Tivoli Storage Manager Versions Affected: all supported
      Initial Impact: Medium
      Additional Keywords: TSM IBM Spectrum Protect
    IMSTMT_BKSETFETCH_SQL
    

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 7.1.8 and 8.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.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT15176

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    71L

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-05-09

  • Closed date

    2016-12-14

  • Last modified date

    2016-12-14

  • 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

  • R71A PSY

       UP

  • R71H PSY

       UP

  • R71L PSY

       UP

  • R71S PSY

       UP

  • R71W PSY

       UP



Document information

More support for: Tivoli Storage Manager

Software version: 7.1.3

Reference #: IT15176

Modified date: 14 December 2016