IBM Support

IJ44169: NULL POINTER EXCEPTION ENCOUNTERED IN THE MAXATTRIBUTE TABLE WITH NON-NULL MAXATTRIBUTE.SCALE VALUES THAT CORRESPOND TO COLUMNS

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

  • When the Integrity Checker is analyzing Maximo attributes
    against the Oracle definition, a null pointer exception is
    encountered if there are attributes defined in the MAXATTRIBUTE
    table with non-null MAXATTRIBUTE.SCALE values that correspond to
    columns in Oracle with a null ALL_TAB_COLUMNS.DATA_SCALE values.
    
    
    The errors identified by the integrity checker ...
    1) BMXAA0443E -- Error - BMXAA8803E -- The sequence
    CRONTASKHISTORYSEQ is not setup correctly.
    
    
    2) BMXAA0443E -- Error - BMXAA0494E -- The definition of this
    column does not match the actual column. The native column
    definition does not match the servers metadata. Run the
    Integrity Checker in repair mode.
    BMXAA9803I -- ALLINVTRANS.ACTUALCOST, Maximo definition is
    DECIMAL(22.4), expected database definition is number (22, 4),
    actual definition is NUMBER(12.4)
    
    3) BMXAA0443E -- Error - BMXAA0494E -- The definition of this
    column does not match the actual column. The native column
    definition does not match the servers metadata. Run the
    Integrity Checker in repair mode.
    BMXAA9803I -- ALLINVTRANS.CURBAL, Maximo definition is
    DECIMAL(22.2), expected database definition is number (22, 2),
    actual definition is NUMBER(15.2)
    
    4) BMXAA0443E -- Error - BMXAA0494E -- The definition of this
    column does not match the actual column. The native column
    definition does not match the servers metadata. Run the
    Integrity Checker in repair mode.
    BMXAA9803I -- ALLINVTRANS.PHYSCNT, Maximo definition is
    DECIMAL(22.2), expected database definition is number (22, 2),
    actual definition is NUMBER(15.2)
    
    5) BMXAA0443E -- Error - BMXAA0494E -- The definition of this
    column does not match the actual column. The native column
    definition does not match the servers metadata. Run the
    Integrity Checker in repair mode.
    BMXAA9803I -- ALLINVTRANS.UNITCOST, Maximo definition is
    DECIMAL(22.4), expected database definition is number (22, 4),
    actual definition is NUMBER(12.4)
    

Local fix

  • The BMXAA8803E error encountered on CRONTASKHISTORYSEQ indicates
    that there is a sequence defined in MAXSEQUENCE on an attribute
    that does not exist in the MAXATTRIBUTE table. This can be found
    by using the following queries:
    select tbname,name from maxsequence where
    sequencename='CRONTASKHISTORYSEQ ';
    select objectname,attributename from maxattribute where
    objectname=<tbname from maxsequence SQL above> and
    attributename=<name from maxsequence SQL above>;
    
    The other 4 errors indicate that the lengths of the 4 attributes
    in the Oracle database don't match the lengths defined in
    Maximo.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Oracle Maximo users running Integrity Checker                *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * On Oracle, Integrity Checker encounters a null pointer       *
    * exception if MAXATTRIBUTE.SCALE non-null and corresponding   *
    * Oracle column's ALL_TAB_COLUMNS.DATA_SCALE value is null.    *
    ****************************************************************
    When the Integrity Checker is analyzing Maximo attributes
    against the Oracle definitions, a null pointer exception is
    encountered if there are attributes defined in the MAXATTRIBUTE
    table with non-null MAXATTRIBUTE.SCALE values that correspond to
    columns in Oracle with a null ALL_TAB_COLUMNS.DATA_SCALE
    values.
    

Problem conclusion

  • The fix for this APAR will be contained in a future release.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ44169

  • 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

    2022-11-07

  • Closed date

    2022-11-07

  • Last modified date

    2022-11-07

  • 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:
08 November 2022