IBM Support

IT36437: IMPORTED DATA MAY FAIL TO RESTORE WITH ANR9999D_3632385001 "INVALID OBJECT HEADER SIZE 0"

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Attempts to restore data from legacy storage pool ( disk, tape
    and file) that was previously imported could fail
    with:
    
    ANR9999D_3632385001 SmSendData(smtrans.c:3725)
    Thread<31124038>: Invalid object header size 0, found
    471.
    ANR9999D Thread<31124038> issued message 9999
    from:
    ANR9999D Thread<31124038> 0x000000010003719c StdPutText
    
    ANR9999D Thread<31124038> 0x000000010003846c OutDiagToCons
    
    ANR9999D Thread<31124038> 0x000000010000d018 outDiagfExt
    
    ANR9999D Thread<31124038> 0x0000000100486764 SmSendData
    
    ANR9999D Thread<31124038> 0x0000000100cf5478
    IPRA.$RtrvFramed
    ANR9999D Thread<31124038> 0x0000000100cf3bc8
    ssRtrv
    ANR9999D Thread<31124038> 0x0000000100d63f1c DfRtrv
    
    ANR9999D Thread<31124038> 0x00000001009da44c IPRA.$RtrvOne
    
    ANR9999D Thread<31124038> 0x00000001009d7ae4
    IPRA.$RtrvFragment
    ANR9999D Thread<31124038>
    0x00000001009d370c bfRtrv
    ANR9999D Thread<31124038>
    0x0000000100c82a08 SmRetrieveBitfile
    ANR9999D Thread<31124038>
    0x0000000100babb94 SmDoObjRtrv
    ANR9999D Thread<31124038>
    0x0000000100b91508 SmNodeSession
    ANR9999D Thread<31124038>
    0x000000010046abfc IPRA.$HandleNodeSession
    ANR9999D
    Thread<31124038> 0x00000001004548e0 smExecuteSession
    ANR9999D
    Thread<31124038> 0x00000001005bb648 psSessionThread
    ANR9999D
    Thread<31124038> 0x0000000100010a70 StartThread
    ANR1165E Error
    detected for file in storage pool POOL1: Node NODE1, Type
    Archive, File space /filespace1, fsId 46, File name
    /file1//2008040215550228#13A06C.0A46.
    ANR9999D_3632385001
    SmSendData(smtrans.c:3725) Thread<31124492>: Invalid object
    header size 0, found 471.
    
    
    Audit volume on imported data also
    results in damaged files being found.
    
     ANR2317W Audit Volume
    found damaged file on volume (volume_name): Node NODE1, Type
    Archive, File space /filespace1, fsId 46, File name (filename)
    is number 2 of 2 versions. (SESSION: 1449675, PROCESS:
    266)
    ANR4133I Audit volume process ended for volume
    (volume_name); 4572116 files inspected, 40689 damaged files
    found and marked as damaged, 0 files previously marked as
    damaged reset to undamaged, 0 objects need updating. (SESSION:
    1449675, PROCESS: 266)
    
    The header size for each object is
    stored in the database along with the data itself. When data is
    restored or audited, the header size from the database is being
    compared with the header size stored within the data.
    When data
    is imported, the header size is stored as a 0 size within the
    database, When a restore attempt or an audit volume operation
    is made from imported data, the header size will not match so
    the error is seen and data is then marked damaged and cannot be
    restored. This is caused by stricter header size checking which
    was brought in by APAR IT32310, and the data is marked as
    damaged even though it is not. The changes in APAR IT32310 do
    not directly affect the import node operation so any Import
    Node operation at the affected server level should not fail
    
    |
    MDVREGR 8.1.10.100-TIV_5698MSV | (IT32310)
    
    Spectrum Protect
    Versions Affected::
    Spectrum Protect Server 7.1.11, 8.1.10.100,
    8.1.11 and above on all supported platforms.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All Tivoli Storage Manager and IBM Spectrum Protect 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.13.200, 7.1.14,          *
    * 8.1.10.300, 8.1.12.100, and 8.1.13. Note that this is        *
    * subject to change at the discretion of IBM.                  *
    ****************************************************************
    

Problem conclusion

  • This problem was fixed.
    Affected platforms for reported release: AIX, HP-UX, Linux,
    Solaris, and Windows.
    Platforms fixed:  AIX, HP-UX, Linux, Solaris, and Windows.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT36437

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    81A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-04-01

  • Closed date

    2021-04-28

  • Last modified date

    2021-04-28

  • 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

  • R81A PSY

       UP

  • R81L PSY

       UP

  • R81W PSY

       UP

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

Document Information

Modified date:
17 December 2021