IBM Support

LO57266: SCR DOES NOT UPDATE A CONFLICT DOCUMENT CORRECTLY

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • Streaming cluster replication does not update a conflict
    document correctly.
    
    Steps to Reproduce:
    1. Prepare following 3 servers
    - Server1(non-cluster)
    - Server2 and Server3(clustered)
    2. In Server2, set DEBUG_SCR=127 in order to confirm that
    streaming cluster replication occurs
    3. Create a discussion database db1.nsf on Server1
    4. Create replica of db1.nsf on Server2 and Server3
    5. Open db1.nsf and create doc1 on Server1
    6. Replicate db1.nsf manually between Server1 and Server2
    7. Confirm that doc1 is replicated to Server3 (by Streaming
    cluster replication)
    8. Open doc1 on Server1, edit Subject, and save
    9. Open doc1 on Server2, edit Subject, and save
    10. Replicate db1.nsf manually between Server1 and Server2
    11. Confirm that a conflict document is generated and the
    conflict document is replicated to Server3 (by Streaming cluster
    replication)
    12. Open the conflict document on Server1, edit the document,
    and remain open
    13. Press Ctrl+S, and wait several seconds
    14. Click Save&Close
    15. Confirm that the conflict document is no longer displayed as
    conflict, and the document sequence number is increased by 2
    16. Replicate db1.nsf manually between Server1 and Server2
    17. Confirm that the update (confirmed in Step 15) is correctly
    replicated to Server2
    18. Confirm that the update is replicated to Server3 (by
    Streaming cluster replication)
    
    Bug:
    The replicated doc on Server3 is still displayed as conflict,
    although the updated content is replicated and the document
    sequence number is correctly increased by 2.
    The fields $Conflict, $ConflictItems, and $REF are not removed.
    
    This problem does not occur when SCR is disabled with
    DEBUG_SCR_DISABLED=1.
    

Local fix

Problem summary

  • This APAR is closed as FIN. We have deferred the fix to a
     future release.
    

Problem conclusion

Temporary fix

Comments

  • This APAR is associated with SPR# CAOA8CD86H.
    The problem will be fixed in the next release of the product.
    

APAR Information

  • APAR number

    LO57266

  • Reported component name

    DOMINO SERVER

  • Reported component ID

    5724E6200

  • Reported release

    850

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-12-22

  • Closed date

    2012-06-21

  • Last modified date

    2012-06-21

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

  • R850 PSN

       UP

[{"Business Unit":{"code":"BU055","label":"Cognitive Applications"},"Product":{"code":"SSKTMJ","label":"Lotus Domino"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
21 June 2012