Direct links to fixes
APAR status
Closed as program error.
Error description
Running the DBUpgrade command fails with the following exception when the customized permission of the system toolkit conflicts with the configuration of new IBM Business Process Manager (BPM) version: SEVERE: Error executing SQL statement: DB2 SQL Error: SQLCODE=-803, SQLSTATE=23505, SQLERRMC=2;BPMADMIN.LSW_ACL_ENTRY, DRIVER=4.11.69 SEVERE: SQL statement that failed: BEGIN ATOMIC INSERT INTO bpmadmin.LSW_ACL_ENTRY (ACL_ENTRY_ID,GROUP_ID,PO_TYPE,PO_ID,MASK) VALUES(23, 3, 2066, '56a4e5e8-4da1-429c-8d9b-b5be67e881d2', 127); INSERT INTO bpmadmin.LSW_ACL_ENTRY (ACL_ENTRY_ID,GROUP_ID,PO_TYPE,PO_ID,MASK) VALUES(24, 4, 2066, '56a4e5e8-4da1-429c-8d9b-b5be67e881d2', 63); END
Local fix
Problem has been fixed in BPM 8.5.6 release Find the changes made to the ACL entry and delete the existing one .. Open ticket with IBM support to identify the row to be deleted Remove the groups from bpmadmin.LSW_ACL_ENTRY -- db2 delete from bpmadmin.LSW_ACL_ENTRY where ACL_ENTRY_ID=3705 db2 delete from bpmadmin.LSW_ACL_ENTRY where ACL_ENTRY_ID=3706 Where the 2 entries are ACL_ENTRY_ID USER_ID GROUP_ID PO_TYPE PO_ID MASK -------------- -------------- -------------- ---------- ------------------------------------ --------------------- 3705. - 4. 2066. 56a4e5e8-4da1-429c-8d9b-b5be67e881d2 63. 3706. - 3. 2066. 56a4e5e8-4da1-429c-8d9b-b5be67e881d2 63. 3. Rerun DBUpgrade
Problem summary
**************************************************************** * USERS AFFECTED: IBM BPM Advanced * * IBM BPM Standard * * IBM BPM Express * **************************************************************** * PROBLEM DESCRIPTION: Running the DBUpgrade command fails * * with the following exception when the * * customized permission of the system * * toolkit conflicts with the * * configuration of new IBM Business * * Process Manager (BPM) version: * * SEVERE: Error executing SQL * * statement: DB2 SQL Error: * * SQLCODE=-803, SQLSTATE=23505, * * SQLERRMC=2;BPMADMIN.LSW_ACL_ENTRY, * * DRIVER=4.11.69 * * SEVERE: SQL statement that failed: * * BEGIN ATOMIC * * INSERT INTO bpmadmin.LSW_ACL_ENTRY * * (ACL_ENTRY_ID,GROUP_ID,PO_TYPE,PO_ID,MA * * SK) * * VALUES(23, 3, 2066, * * '56a4e5e8-4da1-429c-8d9b- * * b5be67e881d2', * * 127); * * INSERT INTO bpmadmin.LSW_ACL_ENTRY * * (ACL_ENTRY_ID,GROUP_ID,PO_TYPE,PO_ID,MA * * SK) * * VALUES(24, 4, 2066, * * '56a4e5e8-4da1-429c-8d9b- * * b5be67e881d2', * * 63); * * END * **************************************************************** * RECOMMENDATION: * **************************************************************** No additional information is available
Problem conclusion
A fix is available for IBM BPM V8.5.5.0 that s allows you to not add a row to LSW_ACL_ENTRY if it already exists. On Fix Central (http://www.ibm.com/support/fixcentral), search for JR53031: 1. Select IBM Business Process Manager with your edition from the product selector, the installed version to the fix pack level, and your platform, and then click Continue 2. Select APAR or SPR, enter JR53031, and click Continue. When you download fix packages, ensure that you also download the readme file for each fix. Review each readme file for additional installation instructions and information about the fix
Temporary fix
Comments
APAR Information
APAR number
JR53031
Reported component name
BPM ADVANCED
Reported component ID
5725C9400
Reported release
855
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-04-06
Closed date
2015-04-22
Last modified date
2015-04-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
BPM ADVANCED
Fixed component ID
5725C9400
Applicable component levels
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"855","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
31 August 2023