IBM Support

IJ41617: WRONG RELATIONSHIP WHEN CREATE ASSET DOCLINKS AT SYSTEM LEVEL

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

  • ERROR DESCRIPTION:
    
    Wrong relationship when create asset doclinks at system level.
    
    
    PROBLEM:
    
    Maximo is using the wrong relationship to fetch the attachments
    from doclinks table when using the "Create asset doclinks at
    system level?" option from Organizations.
    
    
    PERFORMANCE ISSUE: No.
    
    STEPS TO REPRODUCE:
    
    1. Go to Organizations app
    From More Actions, open the System Settings
    
    Enable "Create asset doclinks at system level?" checkbox.
    
    2. Find an Asset (asset A) with an assetid that matches with the
    assetuid of another asset (asset B).
    
    Then add attachments to these two assets.
    
    
    SELECT assetnum FROM asset WHERE assetuid<>assetid;
    SELECT assetid,assetuid,assetnum,siteid FROM asset WHERE assetid
    IN (SELECT ownerid from doclinks WHERE ownertable='ASSET');
    
    Go to Asset app.
    
    Asset A:
    ASSETUID=53
    ASSETID=52
    ASSETNUM=1001
    
    Added attachment 1034 to Asset 1001.
    
    Asset B:
    ASSETUID=52
    ASSETID=51
    ASSETNUM=12222
    
    Added attachment 1033 to Asset 12222.
    
    3. Associate Asset B to a PM record and view the attachments.
    The PM will display attachments from Asset A.
    
    Go to PM app
    Bring up the PM 1008
    Make sure asset 12222 is associated
    Open the Attachments
    
    See attachment 1034 instead of attachment 1033.
    Move to the Asset 12222 and confirm that it has attachment 1033
    there.
    
    4. Look at the performance monitor queries and see the following
    query is running:
    
    select * from doclinks where doclinksid in (select doclinksid
    from doclinks where (ownertable = 'PM' and ownerid = 45 ) union
    all select doclinksid from doclinks where
    (ownertable='LOCATIONS' and ownerid in (select locationsid from
    locations where location= '' and siteid= 'BEDFORD' )) union all
    select doclinksid from doclinks where (ownertable='ASSET' and
    ownerid in (select assetuid from asset where assetnum= '12222'
    and siteid= 'BEDFORD' )) union all select doclinksid from
    doclinks where (ownertable='MASTERPM' and ownerid in (select
    masterpmid from masterpm where masterpmnum= '' )));
    
    select * from docinfo where docinfoid=104;
    
    
    CURRENT ERRONEOUS RESULT:
    
    Wrong relationship when create asset doclinks at system level.
    
    
    EXPECTED RESULT:
    
    Should use the correct relationship when create asset doclinks
    at system level.
    
    
    ENVIRONMENT (SYSTEM INFO):
    
    Tivoli's process automation engine 7.6.1.2-IFIX20210104-1913
    Build 20200715-0100 DB Build V7612-284 HFDB Build HF7612-15
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Maximo users                                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Wrong relationship when create asset doclinks at system      *
    * level.                                                       *
    ****************************************************************
    Maximo is using the wrong relationship to fetch the attachments
    from doclinks table when using the "Create asset doclinks at
    system level?" option from Organizations.
    PERFORMANCE ISSUE: No.
    STEPS TO REPRODUCE:
    1. Go to Organizations app
    From More Actions, open the System Settings
    Enable "Create asset doclinks at system level?" checkbox.
    2. Find an Asset (asset A) with an assetid that matches with
    the
    assetuid of another asset (asset B).
    Then add attachments to these two assets.
    SELECT assetnum FROM asset WHERE assetuid<>assetid;
    SELECT assetid,assetuid,assetnum,siteid FROM asset WHERE
    assetid
    IN (SELECT ownerid from doclinks WHERE ownertable='ASSET');
    Go to Asset app.
    Asset A:
    ASSETUID=53
    ASSETID=52
    ASSETNUM=1001
    Added attachment 1034 to Asset 1001.
    Asset B:
    ASSETUID=52
    ASSETID=51
    ASSETNUM=12222
    Added attachment 1033 to Asset 12222.
    3. Associate Asset B to a PM record and view the attachments.
    The PM will display attachments from Asset A.
    Go to PM app
    Bring up the PM 1008
    Make sure asset 12222 is associated
    Open the Attachments
    See attachment 1034 instead of attachment 1033.
    Move to the Asset 12222 and confirm that it has attachment 1033
    there.
    4. Look at the performance monitor queries and see the
    following
    query is running:
    select * from doclinks where doclinksid in (select doclinksid
    from doclinks where (ownertable = 'PM' and ownerid = 45 ) union
    all select doclinksid from doclinks where
    (ownertable='LOCATIONS' and ownerid in (select locationsid from
    locations where location= '' and siteid= 'BEDFORD' )) union all
    select doclinksid from doclinks where (ownertable='ASSET' and
    ownerid in (select assetuid from asset where assetnum= '12222'
    and siteid= 'BEDFORD' )) union all select doclinksid from
    doclinks where (ownertable='MASTERPM' and ownerid in (select
    masterpmid from masterpm where masterpmnum= '' )));
    select * from docinfo where docinfoid=104;
    CURRENT ERRONEOUS RESULT:
    Wrong relationship when create asset doclinks at system level.
    EXPECTED RESULT:
    Should use the correct relationship when create asset doclinks
    at system level.
    

Problem conclusion

  • The fix for this APAR will be included in a future Release.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ41617

  • Reported component name

    SYSTEM CONFIG

  • Reported component ID

    5724R46S1

  • Reported release

    761

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-08-05

  • Closed date

    2022-08-28

  • Last modified date

    2022-08-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

    SYSTEM CONFIG

  • Fixed component ID

    5724R46S1

Applicable component levels

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

Document Information

Modified date:
29 August 2022