IJ35755: ERROR WHEN ENTERING "ORDER BY" IN THE KPI WHERE CLAUSE

APAR status

• Closed as program error.

Error description

• PROBLEM:
  After upgrading from v 7606 to 7612, existing KPI's  having
  "Order by" in the where clause fail to run/validate. It was
  working in Maximo 7606.
  
  
  This used to work in version 7606 and now many user KPI's are
  not getting validated after the upgrade.
  
  PERFORMANCE ISSUE:
  No
  
  STEPS TO REPRODUCE:
  1- Go to KPI Manager application;
  2- Enter a KPI Name;
  3- Calculation Type: Decimal;
  4- Calculate Trend? Check;
  5- In Select field enter: select (wonum) from workorder
  6- In Where: where status not in ('COMP', 'CLOSE') and istask=0
  and worktype ='PM'
  7- Enter a value in Target:, Caution At: and Alert At:
  8- Is Active? Check;
  9- Save the record;
  10 Back to the In Where field and change to where clause to:
  status not in ('COMP', 'CLOSE') and istask=0 and worktype ='PM'
  order by wonum
  11- Try to save.
  
  CURRENT ERRONEOUS RESULT:
  Unable to save the new KPI Manager where caluse
  
  
  EXPECTED RESULT:
  Save the new KPI Manager where caluse
  
  
  ENVIRONMENT (SYSTEM INFO):
  System Information
  App Server IBM WebSphere Application Server 9.0.0.7
  Tivoli's process automation engine 7.6.1.2-IFIX20210504-1949
  Build 20200715-0100 DB Build V7612-284 HFDB Build HF7612-31
  IBM Maximo Asset Management Work Centers 7.6.0.4 Build
  20200715-0100 DB Build V7604-119 HFDB Build HF7680-10
  IBM Maximo Calibration 7.6.1.0 Build 20200715-0100 DB Build
  V7600-08
  IBM Maximo Asset Management Scheduler 7.6.8.0 Build
  20200715-0100 DB Build V7680-148 HFDB Build HF7680-17
  IBM Tpae Integration Framework 7.6.1.2 Build 20200615-2330 DB
  Build V7612-11
  IBM Maximo Asset Management 7.6.1.2 Build 20200715-0100 DB Build
  V7611-01
  IT Connection Utility 7.6.0.3 Build 20200701-1409 DB Build
  V7603-32
  Server OS
  
  Windows Server 2016 10.0
  Server DB
  Oracle 19.0 (Oracle Database 19c Enterprise Edition Release
  19.0.0.0.0 - Production)
  (c) Copyright IBM Corp. 2020
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Maximo users                                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Users cannot save a new KPI Manager due to an exception when *
  * the where clause contains "order by" and the database is the *
  * Oracle database.                                             *
  ****************************************************************
  

Problem conclusion

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

Temporary fix

Comments

APAR Information

• 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 SYSTEMS

• Fixed component ID

  5724R46AV

Applicable component levels