IJ20145: ERROR WHEN SORTING COMMUNICATION LOG TO FIELD IN ESCALATION APP

APAR status

• Closed as program error.

Error description

• Problem Description:
  Error when sorting Communication Log To field in Escalation app
  STEPS TO REPRODUCE:
  1. In Escalation application create an Escalation with a
  Communication Template
  2. Make sure Create Successful Execution Entry? is checked
  3. On Commtemplate make sure COMM Log Entry is checked.
  4. Activate Escalation and Communication Template
  5. After the escalation runs and send out several emails check
  the Communication Log tab in Escalation app
  6. Sort the To column and you will receive
  BMXAA6713E - The MBO fetch operation failed in the mboset with
  the SQL error code 932. The record could not be retrieved from
  the database. See the log file for more details about the error.
  Results:
  BMXAA6713E - The MBO fetch operation failed in the mboset with
  the SQL error code 932. The record could not be retrieved from
  the database. See the log file for more details about the error.
  PROBLEM:
  7609 - Error when sorting Communication Log To field in
  Escalation app
  Log error
  BMXAA6714E - The data for the next record in the mboset could
  not be retrieved for the SQL query select * from esccommlog
  where exists ( select 1 from escalation where escalation =
  '1040' and uniqueid = escalationid and ownertable= 'WORKORDER'
  ) or exists ( select 1 from escalation where escalation =
  '1040' and uniqueid = escalationid and (ownertable in (select
  value from synonymdomain where domainid in ('TKCLASS',
  'WOCLASS') and maxvalue= 'WORKORDER' ))) or exists ( select 1
  from escalation where escalation = '1040' and uniqueid =
  escalationid and objectname = 'WOACTIVITY') order by sendto
  asc. See the log file for more details about the error.
  java.sql.SQLSyntaxErrorException: ORA-00932: inconsistent
  datatypes: expected - got CLOB
  Expected Results:
  No Oracle error. If field is not sortable by design do not
  allow sorting.
  Product Version:
  Tivoli's process automation engine 7.6.1.1 Build 20190514-1348
  DB Build V7611-365
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Maximo users                                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * ERROR WHEN SORTING COMMUNICATION LOG ON SENDTO COLUMN IN     *
  * ESCALATION APP                                               *
  ****************************************************************
  STEPS TO REPRODUCE:
  1. In Escalation application create an Escalation with a
  Communication Template
  2. Make sure Create Successful Execution Entry? is checked
  3. On Commtemplate make sure COMM Log Entry is checked.
  4. Activate Escalation and Communication Template
  5. After the escalation runs and send out several emails check
  the Communication Log tab in Escalation app
  6. Sort the To column and you will receive
  BMXAA6713E - The MBO fetch operation failed in the mboset with
  the SQL error code 932. The record could not be retrieved from
  the database. See the log file for more details about the
  error.
  Results:
  BMXAA6713E - The MBO fetch operation failed in the mboset with
  the SQL error code 932. The record could not be retrieved from
  the database. See the log file for more details about the
  error.
  ESCCOMMLOG.SENDTO datatype is CLOB and cannot be used to sort.
  Fix is to make this column not sortable.
  

Problem conclusion

• The fix for this APAR will be contained 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