IBM Support

PM50931: syncreplica import produces Nonsequential oplog ids detected

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • IBM Rational ClearCase MultiSite import produces an error,
    Nonsequential oplog ids detected, even though the oplog exists
    and is in the correct order.
    
    multitool: Error: Nonsequential oplog ids detected: expected
    this oplog id to be 27.
    The previous oplog id from the replica is 26.
    multitool: Error: Unable to replay oplog entry 60: error
    detected by ClearCase subsystem.
    60:
    op=mklabel
    replica_oid= XYZ (RemoteReplica)
    oplog_id= 25
    op_time= 2011-10-18T07:39:07Z  create_time= 2011-10-18T07:39:07Z
    event comment= 'Moved label
    
    
    Verifying the problem:
    In general this error should not occur on import. Just seeing
    this error indicates the likelihood that you are experiencing
    this defect.
    
    To confirm:
    1)  Note the failing oplog id from the error message
    (oplog_id=25) as well as the replica associated with that oplog
    replica_oid= XYX (RemoteReplica)
    
    2)  Run multitool lsepoch ?local replica name?
    
    3)  Verify that the oplog ID associated with the replica listed
    in the error is only one oplog behind the oplog listed in the
    error.
    
    Example:
    lsepoch Myreplica
    Oplog IDs for row 'Myreplica'
    ABC=xyz (Myreplica)
    XYZ=24 (RemoteReplica)
    Note that the problem replica has the expected oplog.
    
    
    WORKAROUND
    
    Generate a syncreplica packet where the last entry is the
    'previous oplog id' mentioned in the error message.
    
    This is most easily done on a 7.1.x VOB server that has the
    required oplog entries, using the '-oprange' argument.
    
    Using the example:
    syncreplica import returns error: Nonsequential oplog ids
    detected
    
    multitool: Error: Nonsequential oplog ids detected: expected
    this oplog id to be 27.
    The previous oplog id from the replica is 26.
    multitool: Error: Unable to replay oplog entry 60: error
    detected by ClearCase subsystem.
    60:
    op=mklabel
    replica_oid= XYZ (RemoteReplica)
    oplog_id= 25
    op_time= 2011-10-18T07:39:07Z  create_time= 2011-10-18T07:39:07Z
    event comment= 'Moved label'
    
    Do the command:
    multitool syncreplica -export -fship -oprange
    RemoteReplica=25:26  [target-replica]
    
    This does NOT have to be done AT 'RemoteReplica'; it can be, OR
    it can be done at any replica that has successfully imported
    these oplog entries.
    
    Notes:
    'RemoteReplica' taken from line beginning 'replica_oid='
    '25' taken from line beginning 'oplog_id='
    '26' taken from line beginning 'The previous oplog id from the
    replica is'
    
    The range required may be more than 2 oplog entries.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    IBM Rational ClearCase MultiSite import produces an error,
    Nonsequential oplog ids detected, even though the oplog
    exists and is in the correct order.
    

Problem conclusion

  • A fix is available in ClearCase versions 7.1.2.5 and 8.0.0.1
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM50931

  • Reported component name

    CLRCASE MSITE U

  • Reported component ID

    5724G3201

  • Reported release

    712

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-10-26

  • Closed date

    2011-12-19

  • Last modified date

    2012-01-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

    CLRCASE MSITE U

  • Fixed component ID

    5724G3201

Applicable component levels

  • R712 PSN

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSSH3S","label":"Rational ClearCase MultiSite"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.1.2","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
09 January 2012