JR42133: ON ORACLE, CHANGING CASE OF A VARIABLE NAME IN A TRACKING GROUP DEFINITION CAUSES SQL ERRORS

Version 7.5.1 Fix Pack 1 for the IBM Business Process Manager products

APAR status

• Closed as program error.

Error description

• With Oracle as the database for the Performance Data Warehouse,
  if a tracked variable name is changed, using the same name but
  different case in the Business Process Designer (e. g. "Var1"
  to "var1"), an error similar to the following occurs when the
  tracking definition is updated:
  
  Caused by:
  java.sql.SQLSyntaxErrorException: ORA-00957:
  duplicate column name
  ORA-06512: at line 4
  
  Subsquently during process runtime the following error will be
  logged (during a recreation of the tracking group table
  triggered by the update failure above):
  
  Caused by: java.sql.SQLSyntaxErrorException: ORA-00955: name is
  already used by an existing object
  ORA-06512: at line 4
  
  at
  oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:439)
  at
  oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:395)
  at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:802)
  at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:436)
  at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:186)
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of BPM Express, BPM Standard and BPM  *
  *                  Advanced.                                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: With Oracle as the database for the     *
  *                      Performance Data Warehouse, changing    *
  *                      only the case of a tracked variable     *
  *                      name causes SQL errors when the         *
  *                      tracking definition is updated.         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  With Oracle as the database for the Performance Data Warehouse,
  if a tracked variable name is changed, using the same name but
  different case in the Business Process Designer (e. g. "Var1"
  to "var1"), an error similar to the following occurs when the
  tracking definition is updated:
  Caused by:
  java.sql.SQLSyntaxErrorException: ORA-00957:
  duplicate column name
  ORA-06512: at line 4
  Subsquently during process runtime the following error will be
  logged (during a recreation of the tracking group table
  triggered by the update failure above):
  Caused by: java.sql.SQLSyntaxErrorException: ORA-00955: name is
  already used by an existing object
  ORA-06512: at line 4
  at
  oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:439)
  at
  oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:395)
  at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:802)
  at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:436)
  at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:186)
  

Problem conclusion

• The fix was to modify
  RepresentationManager.createUpdateViewsAction() to upper case
  all the column names it is checking against.  The SQL
  statement still uses mixed case values, but the column names
  are unique even if all names are upper cased.
  
  The column names are sorted by last modification, so for
  mixed case names, the last change by the customer will be used
  for the column name (if the database supports mixed case
  column names).
  
  An interim fix for Version 7.5.1 is published in Fix Central.
  

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

  BPM ADVANCED

• Fixed component ID

  5725C9400

Applicable component levels

• R750 PSY

     UP