IBM Support

IJ32167: UPDATEDB SCRIPT V7612_189 UPDATES CHILDREN RELATIONSHIP ON LOCATIONS OBJECT INAPPROPRIATELY

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

  • DESCRIPTION:
    After applying the TPAE 7.6.1.2 Fix Pack and running UpdateDB,
    the Warnings log shows the following message:
    
    Script V7612_189:
    BMXAA8310W -- The relationship already exists with a different
    target or where clause.
    The relationship CHILDREN from LOCATIONS was modified.
    The existing relationship was to the LOCHIERARCHY table with a
    where clause of "parent=:location and systemid=:systemid and
    siteid = :siteid".
    
    It is observed that the relationship was changed to the
    LOCATIONS table with a where clause of
    "storeroomparent=:location and siteid=:siteid".  Before the
    Feature Pack update, the LOCATIONS.CHILDREN relationship would
    find the children of a Location in a particular System. This
    relationship is using a non-persistent SystemID in the
    Locations object and it is not clear how it gets set.
    
    STEPS TO REPRODUCE:
    *General condition - see Description
    -Log in to maxdemo
    -After applying 7.6.1.2 IFIX, run updateDB script at command
    prompt
    -View the updatedb.log
    
    RESULT:
    Error message logged for Script V7612_189:
    BMXAA8310W -- The relationship already exists with a different
    target or where clause.
    The relationship CHILDREN from LOCATIONS was modified.
    The existing relationship was to the LOCHIERARCHY table with a
    where clause of "parent=:location and systemid=:systemid and
    siteid = :siteid".
    
    EXPECTED RESULT:
    The script will not update the CHILDREN relationship on the
    LOCATIONS object, and a different relationship will be created
    to support any peripheral application functionality
    
    REPORTED IN VERSION:
    Tivoli's process automation engine 7.6.1.2 Build 20200715-0100
    DB Build V7612-284
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Maximo users                                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * UPDATEDB SCRIPT V7612_189 UPDATES CHILDREN RELATIONSHIP ON   *
    * LOCATIONS OBJECT INAPPROPRIATELY                             *
    ****************************************************************
    

Problem conclusion

  • The fix for this APAR is contained in the following maintenance
    package:The fix for this APAR is contained in the following
    maintenance package: | release\fix pack\interim fix for Release
    7.6.1.3 of Base Services
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ32167

  • Reported component name

    PRODUCT INSTALL

  • Reported component ID

    5724R46IT

  • Reported release

    761

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-04-16

  • Closed date

    2021-05-05

  • Last modified date

    2021-05-05

  • 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

    PRODUCT INSTALL

  • Fixed component ID

    5724R46IT

Applicable component levels

[{"Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"IBM Maximo Asset Management"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"761"}]

Document Information

Modified date:
06 May 2021