IBM Support

IT21780: REPLICATION WITH FORCERECONCILE MIGHT NEED 2 RUNS TO SYNC ALL OBJECTS

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • If an IBM Spectrum Protect replication target server has
    duplicate replicated objects that map to the same source server
    object, an issue has been identified with the replication
    process so that two FORCERECONCILE runs are needed to sync the
    server objects again.
    Under the APAR condition, the first forcereconcile=yes deletes
    all the duplicate objects on the target server and the second
    replication with forcereconcile=yes is needed to resend any
    missed objects to the target server.
    
    To verify if you are exposed to this APAR, the following SQL can
    be used before you initiate a replication with
    "FORCERECONCILE=YES":
    
    db2 connect to tsmdb1
    db2 "select count(objid), repl_OBJID, nodeid from
    tsmdb1.replicated_objects group by repl_objid, nodeid having
    count(objid)>1"
    
    If you get a non empty result back, you are exposed to this
    APAR.
    
      IBM Spectrum Protect Versions Affected: 7.1.1 and newer, 8.1
      Initial Impact: Medium
      Additional Keywords: TSM REPLICATION FORCERECONCILE sync
    server objects
    

Local fix

  • If you see the source server holding more objects than the
    target server and if you are in doubt about the replication sync
    state, run replicate node with "forcereconcile=yes" twice
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All 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.9 and 8.1.4. Note that   *
    * this is subject to change at the discretion of IBM.          *
    ****************************************************************
    

Problem conclusion

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

Temporary fix

Comments

APAR Information

  • APAR number

    IT21780

  • 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

    2017-08-04

  • Closed date

    2017-10-09

  • Last modified date

    2017-10-09

  • 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



Document information

More support for: Tivoli Storage Manager

Software version: 7.1.3

Reference #: IT21780

Modified date: 09 October 2017