IBM Support

PI94407: RUNNING A PROCESS THAT RESOLVES A RESOURCE PROPERTY CAUSES A NONUNIQUERESULTEXCEPTION: QUERY DID NOT RETURN A UNIQUE RESULT: #

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

  • Running a process that attempts to resolve a resource property
    causes the step to fail with the following:
    
    "org.hibernate.NonUniqueResultException: query did not return a
    unique result: 13"
    
    Recreation steps:
    
    1) create a component
    2) give the component a "Resource Property Definition" with a
    default value (unsure if a default value is needed).
        let's use the property def 'testProp" as an example
    3) add the component to a resource tree. Mine was base -> agent
    resource -> component resource
    4) give testProp a value on the component resource
    5) create a generic process with a shell step "echo
    ${p:resource/testProp}"
    6) run the generic process on the component resource
    
    this should get a "query did not return unique result" error
    message.
    

Local fix

  • add the following line to the servers installed.properties file
    and restart the server:
    
    com.urbancode.ds.workflow.copyChildPropertiesToParentContext=tru
    e
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All end users on all supported browsers.                     *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Running a process that attempts to resolve a resource        *
    * property                                                     *
    * causes the step to fail with the following:                  *
    *                                                              *
    * "org.hibernate.NonUniqueResultException: query did not       *
    * return a                                                     *
    * unique result: 13"                                           *
    *                                                              *
    * Recreation steps:                                            *
    *                                                              *
    * 1) create a component                                        *
    * 2) give the component a "Resource Property Definition" with  *
    * a                                                            *
    * default value (unsure if a default value is needed).         *
    *     let's use the property def 'testProp" as an example      *
    * 3) add the component to a resource tree. Mine was base ->    *
    * agent                                                        *
    * resource -> component resource                               *
    * 4) give testProp a value on the component resource           *
    * 5) create a generic process with a shell step "echo          *
    * ${p:resource/testProp}"                                      *
    * 6) run the generic process on the component resource         *
    *                                                              *
    * this should get a "query did not return unique result" error *
    * message.                                                     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Fixed in version 6.2.7.2                                     *
    ****************************************************************
    

Problem conclusion

  • Fix is provided in IBM UrbanCode Deploy 6.2.7.2
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI94407

  • Reported component name

    UC DEPLOY

  • Reported component ID

    5725M5400

  • Reported release

    627

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-02-27

  • Closed date

    2018-04-04

  • Last modified date

    2018-04-04

  • 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"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"627","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
04 April 2018