IBM Support

IJ46759: UNABLE TO OPEN OR UPDATE KPI AFTER 7612 TO 7613 UPGRADE

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

  • KPI errors if it contains Order By after upgrade to 7613
    
    STEPS TO REPRODUCE:
    
    
    1. In KPI Manager enter new KPI RKTEST
    2. In Select box copy
    select -(trunc(sysdate) - 1 - max(next_count_date))
    from(
    select trunc(b.physcntdate) + v.ccf as next_count_date
    from invbalances b, inventory v
    3. In Where
    
    where b.itemnum = v.itemnum
    and b.location = v.location
    and b.location = 'SRMMTABUSH'
    and v.ccf < '999'
    order by trunc(b.physcntdate) + v.ccf)
    where rownum < (select round(sum(counts_year)/count_days,1) as
    counts_day
    from(
    select i.itemnum, b.binnum, b.physcntdate,
    (trunc(b.physcntdate)+i.ccf) as nextdate,
    (trunc(b.physcntdate)+2*i.ccf) as nextnextdate, i.abctype,
    i.ccf,
    case when i.ccf = '90' then 4.0
        when i.ccf = '180' then 2
        when i.ccf = '270' then 1.33
        when i.ccf = '360' then 1
        end as counts_year,
        (((add_months(trunc(sysdate, 'YEAR'), 12) - 1) -
    trunc(sysdate))/7)*3 as count_days
    
    from inventory i, invbalances b
    where i.itemnum = b.itemnum
    and i.location = b.location
    and i.ccf in('90','180','270','360')
    and i.location = 'SRMMTABUSH'
    and i.status <> 'OBSOLETE'
    and (trunc(b.physcntdate)+i.ccf) <= (add_months(trunc(sysdate,
    'YEAR'), 12) - 1)))
    
    
    4. Enter
    Target: 80.00
    Caution At: 90.00
    Alert At: 95.00
    5. Save
    Can't save it
    The KPI could not be run successfully. Check the SELECT
    Statement and WHERE Clause for KPI. Invalid SQL queries are
    logged in the log file.
    
    For customer since they already have the KPI entered just
    trying to open it cause the error.
    
    RESULT:
    
    The KPI could not be run successfully. Check the SELECT
    Statement and WHERE Clause for KPI. Invalid SQL queries are
    logged in the log file.
    
    
    EXPECTED RESULT:
    KPI opens and works as normal
    
    PRODUCT VERSION:
    Tivoli's process automation engine 7.6.1.3-IFIX20230324-1804
    Build 20220823-0909 DB Build V7613-344 HFDB Build HF7613-67
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * MAXIMO                                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * UNABLE TO OPEN OR UPDATE KPI AFTER 7612 TO 7613 UPGRADE      *
    ****************************************************************
    

Problem conclusion

  • The fix for this APAR is contained in the following maintenance
    package: release\fix pack for Release 8.x Product
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ46759

  • 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-05-11

  • Closed date

    2023-05-22

  • Last modified date

    2023-05-22

  • 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:
22 May 2023