JR61954: RUNNING THE PROCESSSERVERDB COMMAND DOESN'T CREATE BPM_HISTORICAL_DATA_PLAYBACK OR BPM_REF_PO TABLES ON Z/OS

workflow.20002.delta.repository
8.6.20020001-WS-BPM-IFJR62842
8.6.10019003-WS-BPM-IFJR61954

APAR status

• Closed as program error.

Error description

• When you run the ProcessServerDb command during an upgrade, the
  command fails when running the createTable_ProcessServer.sql
  file on IBM Db2 for z/OS and you see an error similar to
  following error:
  
  ALTER TABLE ZPSV04E.BPM_HISTORICAL_DATA_PLAYBACK ADD CONSTRAINT
  LSWC_PLAYBACK_INSTANCE_FK FOREIGN KEY("BPD_INSTANCE_ID")
  
  REFERENCES ZPSV04E.LSW_BPD_INSTANCE("BPD_INSTANCE_ID") ON DELETE
  CASCADE;
  com.ibm.db2.jcc.am.SqlSyntaxErrorException: DB2 SQL Error:
  SQLCODE=-538, SQLSTATE=42830,
  SQLERRMC=LSWC_PLAYBACK_INSTANCE_FK;ZPSV04E.LSW_BPD_INSTANCE,
  DRIVER=4.25.17
  

Local fix

Problem summary

• A constraint on the foreign key occurs when you create a
  database or run the DBUpgrade command on z/OS. This foreign key
  is used in the BPM_HISTORICAL_DATA_PLAYBACK table and must be
  the same length as the corresponding key in the LSW_BPD_INSTANCE
   table.
  
  When you re-create the BPM_REF_PO table with different
  constraints, it is mandatory in z/OS to also drop the index.
  
  PRODUCT AFFECTED:
  IBM Business Automation Workflow on z/OS.
  

Problem conclusion

• A fix is available or will be available that fixes the foreign
  key length in BPM_HISTORICAL_DATA_PLAYBACK table and drops the
  BPM_REF_PO table's index when running on z/OS.
  

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

  BUS AUTO WORKFL

• Fixed component ID

  5737H4100

Applicable component levels