IBM Support

PM42345: VOB shared memory mutex never recovers and database processes loop in db_VISTA -926 timed out waiting for lock

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • VOB shared memory mutex never recovers and database processes
    loop in db_VISTA -926 timed out waiting for lock
    
    
    ClearCase 7.1.2.x
       VOB Storage stored on a NAS Device
    
    
    RedHat 5 Update 5 and Update 6
    
    
    
    Symptoms:
    
    
    When using a VOB server on RedHat with NAS storage, the
    following may be seen within the db_server or vobrpc_server logs
    if a specific VOB becomes unresponsive:
    
    db_server(*****): Ok: CRRDM0532I Rollforward recovery using
    ?/ccstg/vobs/test.vbs/db/vista.tjf? started Mon Jun 13 12:31:12
    2011
    db_server(*****): Ok:
    db_server(*****): Ok: CRRDM0605I Rollforward recovery using
    ?/ccstg/vobs/test.vbs/db/vista.tjf? finished Mon Jun 13 12:31:12
    2011
    db_server(*****): Ok:
    .
    .
    2011-06-14T00:36:09+05:30 db_server(*****): Ok: CRRDM0656E ***
    db_VISTA database error -926 - problem in shared memory lock
    manager: Process 2291 timed out waiting for lock.
    2011-06-14T00:36:09+05:30 db_server(*****): Ok: Timeout getting
    lock in VOB ?/ccstg/vobs/test.vbs/db?.
    .
    .
    2011-06-14T00:41:09+05:30 db_server(*****): Ok: CRRDM0656E ***
    db_VISTA database error -926 - problem in shared memory lock
    manager: Process 2291 timed out waiting for lock.
    2011-06-14T00:41:09+05:30 db_server(*****): Ok: Timeout getting
    lock in VOB ?/ccstg/vobs/test.vbs/db?.
    
    
    The error message above repeats every 5 minutes for the same
    server process, and never recovers.  The VOB indicated within
    the message will not respond to any cleartool commands during
    this period of time.
    
    
    Workaround:  None
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    VOB shared memory mutex never recovers and database
    processes loop in db_VISTA -926 timed out waiting for lock
    
    
    ClearCase 7.1.2.x
       VOB Storage stored on a NAS Device
    
    
    RedHat 5 Update 5 and Update 6
    
    
    
    Symptoms:
    
    
    When using a VOB server on RedHat with NAS storage, the
    following may be seen within the db_server or vobrpc_server
    logs if a specific VOB becomes unresponsive:
    
    db_server(*****): Ok: CRRDM0532I Rollforward recovery using
    ?/ccstg/vobs/test.vbs/db/vista.tjf? started Mon Jun 13
    12:31:12 2011
    db_server(*****): Ok:
    db_server(*****): Ok: CRRDM0605I Rollforward recovery using
    ?/ccstg/vobs/test.vbs/db/vista.tjf? finished Mon Jun 13
    12:31:12 2011
    db_server(*****): Ok:
    .
    .
    2011-06-14T00:36:09+05:30 db_server(*****): Ok: CRRDM0656E
    *** db_VISTA database error -926 - problem in shared memory
    lock manager: Process 2291 timed out waiting for lock.
    2011-06-14T00:36:09+05:30 db_server(*****): Ok: Timeout
    getting lock in VOB ?/ccstg/vobs/test.vbs/db?.
    .
    .
    2011-06-14T00:41:09+05:30 db_server(*****): Ok: CRRDM0656E
    *** db_VISTA database error -926 - problem in shared memory
    lock manager: Process 2291 timed out waiting for lock.
    2011-06-14T00:41:09+05:30 db_server(*****): Ok: Timeout
    getting lock in VOB ?/ccstg/vobs/test.vbs/db?.
    
    
    The error message above repeats every 5 minutes for the same
    server process, and never recovers.  The VOB indicated
    within the message will not respond to any cleartool
    commands during this period of time.
    
    
    Workaround:  None
    

Problem conclusion

  • A fix is available in ClearCase versions 7.1.1.8, 7.1.2.5
    and 8.0.0.1
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM42345

  • Reported component name

    CLEARCASE UNIX

  • Reported component ID

    5724G2901

  • Reported release

    712

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-06-23

  • Closed date

    2011-12-16

  • Last modified date

    2011-12-16

  • 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

    CLEARCASE UNIX

  • Fixed component ID

    5724G2901

Applicable component levels

  • R712 PSN

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSSH27","label":"Rational ClearCase"},"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:
16 December 2011