IBM Support

PM87416: Deleting renamed subproject fails, causes database corruption

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • User having only the developer role checks out a subproject with
    the intention of renaming it.
    
    User performs these steps:
    
    1. Set a task.
    2. From a working project structure, rename a subproject via the
    GUI.
    3. Update the subproject. Update unuses all members besides the
    root directory (which is associated with current task), since
    there is no project having the new name in the latest baseline.
    
    4. Attempt to delete the project from the GUI. It fails because
    it cannot bind the previous version back to the parent project.
    The message view reports:
    
    Member NewName-joeuser removed from project
    ParentProject-joeuser
    Setting path for work area of 'NewName-joeuser' to
    'C:/Users/joeuser/Documents/Synergy/ccm_wa/testdb/NewName-joeuse
    r'...
    Warning: Project update failed; unable to bind new member.
    Unable to add object directory entry to directory.
    --- Begin Error Reporting ---
    CRCCM0003: The operation failed. See the error description for
    more detailed information.
    Member NewName-joeuser removed from project
    ParentProject-joeuser
    Setting path for work area of 'NewName-joeuser' to
    'C:/Users/joeuser/Documents/Synergy/ccm_wa/testdb/NewName-joeuse
    r'...
    Project update failed; unable to bind new member.
    Unable to add object directory entry to directory.
    
    --- End Error Reporting ---
    
    Result:
    
    The project remains in the database and the user's parent
    project is left without the subproject under the new or old
    name.
    
    Further, the next ccmdb check report multiple errors: 'Parent CV
    [directory name/cvid] not bound in assembly [project
    name/cvid]'.
    
    If these errors are not cleared (see
    http://www-01.ibm.com/support/docview.wss?uid=swg21325223) then
    project cannot be deleted as it is reported as an assembly with
    bindings.
    

Local fix

Problem summary

  • Deleting renamed subproject fails, causes database corruption
    

Problem conclusion

  • Fixed in Synergy 7.2.05
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM87416

  • Reported component name

    TLOGIC SYNERGY

  • Reported component ID

    5724V66SN

  • Reported release

    720

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-04-19

  • Closed date

    2013-10-07

  • Last modified date

    2013-10-07

  • 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 SYNERGY

  • Fixed component ID

    5724V66SN

Applicable component levels

  • R720 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSC6Q5","label":"Rational Synergy"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.2","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
22 December 2020