IT14687: REPLICATE NODE FAILING WITH AN ANR9999D_1682615140

7.1.5.200-TIV-TSMSRV-AIX
7.1.5.200-TIV-TSMSRV-HP-UX
7.1.5.200-TIV-TSMSRV-Linuxppc64
7.1.5.200-TIV-TSMSRV-Linuxs390x
7.1.5.200-TIV-TSMSRV-Linuxx86_64
7.1.5.200-TIV-TSMSRV-SolarisSPARC
7.1.5.200-TIV-TSMSRV-WIN
7.1.6.000-TIV-TSMSRV-AIX
7.1.6.000-TIV-TSMSRV-HP-UX
7.1.6.000-TIV-TSMSRV-Linuxx86_64
7.1.6.000-TIV-TSMSRV-SolarisSPARC
7.1.6.000-TIV-TSMSRV-WIN
7.1.6.000-TIV-TSMSRV-Linuxppc64
7.1.6.000-TIV-TSMSRV-Linuxs390x
CNF3LML.ova
IBM Spectrum Protect Server V7.1.5.X interim fix downloads
IBM Spectrum Protect Server V7.1 Fix Pack 6 (7.1.6.000) Downloads

APAR status

• Closed as program error.

Error description

• During the split of large metadata chunk sizes, the container
  does not have enough range allocated for metadata chunk,
    causing an invalid object header
    Replication and restore operations are likely to fail without
    errors, as in this example message:
    ANR1893E Process 51 for Replicate Node completed with a
    completion state of FAILURE.
    After a failed restore or replication operation, the object's
    non-deduplicated extent, which contains the object's metadata,
    is marked as damaged. If the container of this
    non-deduplicated extent is audited,  the following error can
    occur:
    ANR2338E smtrans.c(7062): Invalid header received for object
    10331953, length 446. Size (321), pushed (4), skipped (0),
    status (0). Found length (0), type (0), size (4).
  Tivoli Storage Manager Versions Affected:
    Tivoli Storage Manager Server 7.1.3
  Customer/L2 Diagnostics (If Applicable)
    The following diagnostic message can be found in the activity
    log of the replication target server.
    ANR9999D 1682615140 sdProcessDedupChunk(sddedup.c:1505)
  Thread<1725>:
      Data received 218 doesn't match expected 679746,
      E23072E80E9D60F6E5B7608EE0E93DB488C6532C, SHA1
    ANR9999D Thread<1725> issued message 9999 from:
    ANR9999D Thread<1725>  0x000000010001ec8c StdPutText
    ANR9999D Thread<1725>  0x000000010001f860 OutDiagToCons
    ANR9999D Thread<1725>  0x000000010000a374 outDiagfExt
    ANR9999D Thread<1725>  0x000000010093ded0 sdProcessDedupChunk
    ANR9999D Thread<1725>  0x00000001009883ac smProcessDedupChunk
    ANR9999D Thread<1725>  0x00000001003d5398 DoProcessDedupChunk
    ANR9999D Thread<1725>  0x00000001003d3ce0 SmRecvNextData
    ANR9999D Thread<1725>  0x0000000100763224 SdStore
    ANR9999D Thread<1725>  0x0000000100762b54 sdCreate
    ANR9999D Thread<1725>  0x000000010075608c CreateBitfile
    ANR9999D Thread<1725>  0x00000001007534c4 bfCreate
    ANR9999D Thread<1725>  0x00000001006ae168 CreateBitfile
    ANR9999D Thread<1725>  0x000000010068cecc
  SmDoBackInsNormEnhanced
    ANR9999D Thread<1725>  0x000000010096264c SmReplServerSession
    ANR9999D Thread<1725>  0x00000001003b9974 DoReplServer
    ANR9999D Thread<1725>  0x00000001003af588 smExecuteSession
    ANR9999D Thread<1725>  0x0000000100377700 psSessionThread
    ANR9999D Thread<1725>  0x000000010000d674 StartThread
  Initial Impact:
    HIGH
  Additional Keywords:
    TSM REPL DEDUP CONTAINER
  

Local fix

•   N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Tivoli Storage Manager server users with container       *
  * storage pools.                                               *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * In a container storage pool (STGTYPE=CONTAINER or            *
  * STGTYPE=CLOUD), storing files with metadata sizes that are   *
  * greater than 4 KB can result in metadata loss.  The files    *
  * most likely to be affected includes Windows System State     *
  * files and UNIX, Linux, and Macintosh files with extended     *
  * attributes or access control lists that exceed 4 KB.         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available. This problem is currently *
  * projected to be fixed in level 7.1.5.200 and 7.1.6. Note     *
  * that this is subject to change at the discretion of IBM.     *
  ****************************************************************
  

Problem conclusion

• This problem was fixed.  See technote 21981566 for resolution
  details:
  www.ibm.com/support/docview.wss?uid=swg21981566
  
  Affected platforms: AIX, 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