IBM Support

IT05548: "GENERATE BACKUPSET" CAN FAIL WITH ANR0102E ANR9999D_1585665753 ANR3503E IF NUM_LOG_SPAN LIMIT IS VIOLATED.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • "Generate backupset" for a node or a group of nodes can fail
    with following error
    in  activity log:
    
    ANR0171I imobjgen.c(6993): Error detected on
    58:5, database in evaluation mode.
    
    ANR0157W Database operation INSERT for table
    Backupset.Temp.Objects failed with result code
    4522 and tracking ID: 000000001AAF2730.
    
    ANR0158W Database operation INSERT for table
    Backupset.Temp.Objects failed with operation
    code 4522 and tracking id 000000001AAF2730. The data for column
    0 is:
    (string, len=6)0x4558504F5254.
    
    ANR0102E imobjgen.c(7032): Error 4522 inserting
     row in table "Temp TOC Table for Backupset".
    
    ANR9999D_1585665753
    imRecordObjInTOC(imobjgen.c:1527) Thread<61>: RecordObjInToc
    failed,
    objId=23183019195, rc=9996
    
    ANR3503E Generation of backup set for NODE_NAME as
    ABC-DEF-2014.23872560986 (data type File)
    failed.
    
    In db2diag.xx.log it will be seen:
    
    2014-08-23-13.28.01.065000+000 E84682372F755        LEVEL: Error
    PID     : 5036                 TID : 5564           PROC :
    db2syscs.exe
    INSTANCE: SERVER1              NODE : 000           DB   :
    TSMDB1
    HOSTNAME: host1
    EDUID   : 5564                 EDUNAME: db2loggr (TSMDB1)
    FUNCTION: DB2 UDB, data protection services,
    sqlpScanTranTableForLowTran, probe:550
    MESSAGE : ADM1541W  Application "dsmsvc.exe" with application
    handle "0-16346"
              and application id "*LOCAL.SERVER1.140822161733"
    executing under
              authentication id "X-SVC-TSMDB" has been forced off of
    the database
              for violating database configuration parameter
    NUM_LOG_SPAN (current
              value "231"). The unit of work will be rolled back.
    
    
    
    
    The problem can occur when the "generate backupset" is not able
    to
    process 1000 files before the TOC transaction spans too many log
    files.
    
    There are several factors involved here:
    the "generate backupset" throughput of bytes of processing
    files, the stress on the server (how
    fast the activelog is written), the size of processed files.
    
    With these we have chance that the transaction can last for a
    long time, and therefore has chance to span
    the logs and reach NUM_LOG_SPAN limit.
    
    
    
    
    Tivoli Storage Manager Versions Affected:
    Tivoli Storage Manager Server 6.3.x and 7.1.x on all supported
    platforms
    
    
    
    
    Initial Impact: Medium
    
    Additional Keywords: zz63 zz71 generate backupset gen log
    num_log_span
    

Local fix

  • With Server 7.1.1, there is option that allows activelogsize to
    be increased to 512GB.
    This may allow the "generate backupset" to complete.
    

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 level 7.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, Solaris, Linux, and Windows.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT05548

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    71W

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-11-17

  • Closed date

    2014-12-09

  • Last modified date

    2015-01-29

  • 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

[{"Line of Business":{"code":"LOB26","label":"Storage"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGSG7","label":"Tivoli Storage Manager"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.1.3"}]

Document Information

Modified date:
25 September 2021