IBM Support

PM68052: albd_server should rename the .new or .old registry files on startup if the permanent files do not exist

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • albd_server should rename the .new or .old registry files on
    startup if the permanent files do not exist
    
    
    
    ClearCase 7.1.2.x and 8.x Registry Servers
    
    ALL UNIX and Linux hosts
    
    
    Description of the Problem:
    
    1)  The Registry files were located on a NAS share for High
    Availability
    
    2)  At some point, journaling was interrupted by a network
    outage
    
    3)  ClearCase is then restarted and the following was noted
    within the albd_log:
    
    albd_server(***): Warning: Registry file
    '/var/adm/rational/clearcase/rgy/view_object' not found.
    albd_server(***): Warning: New registry file
    '/var/adm/rational/clearcase/rgy/view_object' created.
    albd_server(***): Warning: Registry file
    '/var/adm/rational/clearcase/rgy/view_tag' not found.
    albd_server(***): Warning: New registry file
    '/var/adm/rational/clearcase/rgy/view_tag' created.
    
    4)  When ClearCase finally starts, all of the views are gone
    
    5)  Looking into the rgy directory, the following is seen:
    
       view_tag.old
       view_object.old
       view_tag.new
       view_object.new
    
    
    Workaround:  None
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    After a network outage, ClearCase was restarted and there
    were .old and .new versions of the registry data files, but
    the registry server was unable to recover the data
    correctly.
    

Problem conclusion

  • This problem has been fixed in ClearCase 7.1.2.9 and
    8.0.0.5.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM68052

  • Reported component name

    CLEARCASE UNIX

  • Reported component ID

    5724G2901

  • Reported release

    712

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-07-02

  • Closed date

    2012-12-15

  • Last modified date

    2012-12-15

  • 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:
15 December 2012