IBM Support

IJ48269: MTM UPDATEDB FAILS ON VIEW REBUILD FOR EXTENSION ATTRIBUTES

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

  • PROBLEM:
    
    Extension tables during the updatedb process is incorrectly
    attempting to rebuild the views which Maximo uses to integrate
    the extension tables. The error being presented is due to
    duplication of column names caused by the extension tables.
    
    PERFORMANCE ISSUE:
    N/A
    
    STEPS TO REPRODUCE:
    1. Add extension attribute to workorder object on 7612 MTM
    version.
    2. Upgrade to 7613 MTM.
    
    CURRENT ERRONEOUS RESULT:
    
    ERROR: BMXAA7025E -- Script failed while running.;
    DB2 SQL Error: SQLCODE=-612, SQLSTATE=42711,
    SQLERRMC=RPREVIEWED, DRIVER=4.29.24
    	at psdi.dbmanage.ScriptRun(ScriptRun.java: 272)
    	at psdi.tools.ScriptExecutionInfo(ScriptExecutionInfo.java:
    514)
    
    EXPECTED RESULT:
    
    Upgrade to keep and rebuild object with extensions.
    
    ADDITIONAL INFO:
    N/A
    
    ENVIRONMENT (SYSTEM INFO):
    
    TPAE 7612 to 7613.
    
    LOCAL FIX: N/A
    
    SECURITY IMPACT (Y/N): N
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * MAXIMO                                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * MTM UPDATEDB FAILS ON VIEW REBUILD FOR EXTENSION ATTRIBUTES  *
    ****************************************************************
    

Problem conclusion

  • Resolved issue with UpdateDB. Any extended attribute become part
    of the maximo view so it gets added to maxviewcolumn table. When
    extended view is build all attributes from maxviewcolumn is
    added and also columns from extended table. So extended
    attributes added twice cause an eror. The solution is to skip
    columns from maxviewcolumn if they exists in extended table
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ48269

  • Reported component name

    MAXIMO ASST MGM

  • Reported component ID

    5724R46AM

  • Reported release

    761

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-08-29

  • Closed date

    2023-09-11

  • Last modified date

    2023-09-11

  • 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

    MAXIMO ASST MGM

  • Fixed component ID

    5724R46AM

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:
12 September 2023