IBM Support

PM42417: DOORS: data corrupted after restoring a dma with baselined read-locked data

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Reproducible in DOORS 9.3.0.3 by Kourosh with the following
    steps:
    1) Create a new module
    2) In this new module, create the following object structure:
    1
    2
    3
    3.1
    3.2
    4
    4.1
    4.2
    
    3) Set objects 2, 3, 3.1, 3.2, 4.2 to have access rights as
    'Everyone None'
    4) Soft delete the objects listed in step #3
    5) Baseline the module
    6) Archive the module
    7) Restore the dma as any user other than 'Administrator'
    note: at this point open the module after restore and try to
    open the baseline, notice the error!
    8) Archive the module restored in step 7
    9) Restore the dma as any user other than 'Administrator'
    note: now the error shows up during the restore process!
    
    Step 7 seems to be causing the corruption in the baseline when
    you restore as any user other than 'Administrator' (I assume the
    read-locked-data objects in the baseline are causing the
    problem). Now if you restored the module in step 7 as
    'Administrator' there are no problems. So this is one work
    around. Another workaround is to restore the module in a
    different database so the ACL's are reset.
    
    Here are steps for another aspect of the issue to look into:
    1) Create a new module
    2) Create only one object in the module
    3) Set the access rights on this one object to be 'Everyone
    None'
    4) Baseline this module
    5) Archive this module
    6) Restore this dma as any user other than 'Administrator'
    7) Open the restored dma and view the baseline
    Notice the baseline is empty and the one 'Read-locked-data'
    object which *should* be in the module is not there.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    DOORS data was getting corrupted after restoring a dma with
    baselined read-locked data with a different non-admin user.
    

Problem conclusion

  • this was happening because of a function which was
    incorrectly writing the database while restoring the dma.
    
    Fixed in version 9.3.0.5
    
    Keywords: Data corruption, Restore, Baselined read-locked
    data.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM42417

  • Reported component name

    TLOGIC DOORS

  • Reported component ID

    5724V61DR

  • Reported release

    920

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-06-24

  • Closed date

    2011-09-28

  • Last modified date

    2011-09-28

  • 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

    TLOGIC DOORS

  • Fixed component ID

    5724V61DR

Applicable component levels

  • R920 PSN

       UP



Document information

More support for: Rational DOORS

Software version: 9.2

Reference #: PM42417

Modified date: 28 September 2011