IBM Support

IT13236: ANR3247W FOR SERVER DATA MOVEMENT OPERATIONS BECAUSE OF PENDING FRAGMENTS WHEN COPY OR ACTIVE STORAGE POOLS BEING USED.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Tivoli Storage Manager/Spectrum Protect server might report the
    following message for server data movement operations:
    
    ANR3247W Process <ID> skipped <#> files on volume <VOLUME>
    because of pending fragments.
    
    To be exposed to this APAR you have to be using This problem
    only occurs if copy pools or active data pools are in use. The
    symptom warning message is seen when the server deletes
    fragmented objects and when the server needs to find multiple
    copies of a fragment that needs to be deleted.
    
    
    
    
    A trace with the BFDESTROY BFSAGGR AFMOVE traceflags will show
    the following symptom:
    
    [bfsaggr.c][2348][CleanupDeletedSuperAggregate]:Deleting all
    fragments for objId 2115627596
    [bfsaggr.c][2500][CleanupDeletedSuperAggregate]:Calling
    bfDestroy for fragment 2115627596
    [bfsaggr.c][2500][CleanupDeletedSuperAggregate]:Calling
    bfDestroy for fragment 2115667728
    [bfsaggr.c][2500][CleanupDeletedSuperAggregate]:Calling
    bfDestroy for fragment 2115707778
    [bfsaggr.c][2500][CleanupDeletedSuperAggregate]:Calling
    bfDestroy for fragment 2115747780 <<<
    [bfsaggr.c][2500][CleanupDeletedSuperAggregate]:Calling
    bfDestroy for fragment 2115747780 <<<
    [bfsaggr.c][2527][CleanupDeletedSuperAggregate]:Error 1114
    destroying fragment 2115747780
    [bfsaggr.c][2579][CleanupDeletedSuperAggregate]:Exiting, rc 1114
    
    [bfsaggr.c][2348][CleanupDeletedSuperAggregate]:Deleting all
    fragments for objId 2115206134
    [bfsaggr.c][2500][CleanupDeletedSuperAggregate]:Calling
    bfDestroy for fragment 2115206134
    [bfsaggr.c][2500][CleanupDeletedSuperAggregate]:Calling
    bfDestroy for fragment 2115246136
    [bfsaggr.c][2500][CleanupDeletedSuperAggregate]:Calling
    bfDestroy for fragment 2115286138 <<<
    [bfsaggr.c][2500][CleanupDeletedSuperAggregate]:Calling
    bfDestroy for fragment 2115286138 <<<
    [bfsaggr.c][2527][CleanupDeletedSuperAggregate]:Error 1114
    destroying fragment 2115286138
    [bfsaggr.c][2579][CleanupDeletedSuperAggregate]:Exiting, rc 1114
    
    [bfsaggr.c][2348][CleanupDeletedSuperAggregate]:Deleting all
    fragments for objId 2114989351
    [bfsaggr.c][2500][CleanupDeletedSuperAggregate]:Calling
    bfDestroy for fragment 2114989351
    [bfsaggr.c][2500][CleanupDeletedSuperAggregate]:Calling
    bfDestroy for fragment 2115029353
    [bfsaggr.c][2500][CleanupDeletedSuperAggregate]:Calling
    bfDestroy for fragment 2115069355
    [bfsaggr.c][2500][CleanupDeletedSuperAggregate]:Calling
    bfDestroy for fragment 2115109357 <<<
    [bfsaggr.c][2500][CleanupDeletedSuperAggregate]:Calling
    bfDestroy for fragment 2115109357 <<<
    [bfsaggr.c][2527][CleanupDeletedSuperAggregate]:Error 1114
    destroying fragment 2115109357
    [bfsaggr.c][2579][CleanupDeletedSuperAggregate]:Exiting, rc 1114
    
    
    This APAR is less likely to happen when the primary pool is
    deduplicated and the copy pool is not deduplicated, because that
    will most likely result in the two pools having different
    bitfiles representing that fragment instead of identical
    bitfiles.
    
    | MDVREGR 7.1.3.0-TIV_5698MSV |
      Tivoli Storage Manager Versions Affected: 7.1.3
      Customer/L2 Diagnostics (If Applicable) trace BFDESTROY
    BFSAGGR AFMOVE
      Initial Impact: Medium
      Additional Keywords: reclamation TSM move 1114
    GRC_KEY_NOT_FOUND
    

Local fix

  • A server restart will reset the pending fragments table.
    

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.5. 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

    IT13236

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    71W

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-01-19

  • Closed date

    2016-01-22

  • Last modified date

    2016-02-11

  • 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: 71W

Reference #: IT13236

Modified date: 11 February 2016