IBM Support

PH19472: UPGRADE OF UCD FAILS IF THE 'MANAGE PROPERTIES' PERMISSION ALREADY EXISTS ON THE 'UC AUTO DISCOVERY' ROLE

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • Upgrading to UCD 7041 can fail during database upgrade if
    user has manually given Manage Properties permission to UC
    Auto Discovery role. The upgrade references an id that might not
    be present in the database and will insert a record if it is not
    present. If the user has already given the role this permission,
    then the id on this mapping will be different and the upgrade
    will produce a unique constraint violation error on
    action_resource_role_mapping for the sec_role_action table.
    

Local fix

  • Delete the mapping between role and action that already exists
    and let the upgrade recreate it. To do this, in the UCD release
    you are upgrading from, turn off the 'Manage Properties'
    permission for Resource on the 'UC AutoDiscovery' Role under
    'Settings -> Role Configuration -> UC Auto Discovery -> Resource
    -> Edit', before you start the upgrade.
    
    Then re-attempt the upgrade.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All end users on all supported browsers.                     *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Upgrading to UCD 7041 can fail during database upgrade if    *
    * user has manually given Manage Properties permission to UC   *
    * Auto Discovery role. The upgrade references an id that might *
    * not                                                          *
    * be present in the database and will insert a record if it is *
    * not                                                          *
    * present. If the user has already given the role this         *
    * permission,                                                  *
    * then the id on this mapping will be different and the        *
    * upgrade                                                      *
    * will produce a unique constraint violation error on          *
    * action_resource_role_mapping for the sec_role_action table.  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Fixed in version 7.1.0.0                                     *
    ****************************************************************
    

Problem conclusion

  • Fix is provided in IBM UrbanCode Deploy 7.1.0.0
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH19472

  • Reported component name

    UC DEPLOY

  • Reported component ID

    5725M5400

  • Reported release

    704

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-11-20

  • Closed date

    2020-07-22

  • Last modified date

    2020-07-22

  • 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

    UC DEPLOY

  • Fixed component ID

    5725M5400

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS4GSP","label":"IBM UrbanCode Deploy"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"704","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
23 July 2020