IBM Support

PM84918: REBASE -COMPLETE FAILS WITH DEADMAN LOCK TIMEOUT DURING REBASE OF A STREAM IN A UCM ENVIRONMENT WITH MULTIPLE PVOBS

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • In an IBM Rational ClearCase environment involving multiple
    Project VOBs linked by a common administrative VOB, it is
    possible that simultaneous transactions in the PVOBs can cause a
    deadlock resulting in one or both processes to fail when the
    deadman lock timout is reached. One such transaction that may be
    affected is rebase completion, which involves nested
    transactions in multiple vobs when for example a stream in one
    PVOB is rebased to a baseline in another PVOB.
    
    Running 'cleartool rebase -complete' results in the following
    error on the client:
    
    Updating stream's configuration...
    cleartool: Error: Error from VOB database: '/vobs/pvob1'.
    cleartool: Error: Unable to create hlink of type 'UseBaseline'
    from 'stream1', to 'baseline1'.
    cleartool: Error: Can't update stream's configuration.
    cleartool: Error: Unable to update config.
    cleartool: Error: Unable to complete integration.
    cleartool: Error: Can't update stream's configuration.
    cleartool: Error: Unable to resume rebase.
    
    The VOB server will log the following event in the
    db_server_log:
    
    Error: Deadman lock timeout.  Client
    'client1,pid==<pid>,euid==UNIX:UID-<uid>,cleartool 'rebase'
    '-complete'' idle while holding locks.
    
    Steps to reproduce: The exact circumstances are unknown. This
    problem may only be seen under certain conditions where there is
    heavy load on multiple PVOBs and nested transactions are taking
    place in both concurrently. In theory it will only take two
    clients to reproduce the timeout.
    
    Workaround: Retry the operation until it succeeds, or lock all
    PVOBs using the -nusers switch to exempt one user whose
    operation is failing due to deadman timeout.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Rebase -complete may fail  with deadman lock timeout during
    rebase of a stream in a UCM environment with multiple PVOBs
    

Problem conclusion

  • A fix is available in ClearCase versions 7.1.2.11 and
    8.0.0.7
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM84918

  • Reported component name

    CC&CC MSITE WIN

  • Reported component ID

    5724G3300

  • Reported release

    712

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-03-15

  • Closed date

    2013-06-27

  • Last modified date

    2013-06-27

  • 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

    CC&CC MSITE WIN

  • Fixed component ID

    5724G3300

Applicable component levels

  • R712 PSN

       UP



Document information

More support for: Rational ClearCase MultiSite

Software version: 7.1.2

Reference #: PM84918

Modified date: 27 June 2013