A fix is available
APAR status
Closed as program error.
Error description
Primary key generation with auto-tracking enabled can cause the Performance Data Warehouse server to stop processing during report generation. Symptoms in the logs are repeated lock wait timeouts such as the following (example is for Oracle, where this has been observed): org.springframework.jdbc.BadSqlGrammarException: ConnectionCallback; bad SQL grammar []; nested exception is java.sql.SQLSyntaxErrorException: ORA-02049: timeout: distributed transaction waiting for lock ORA-06512: at "SYS.DBMS_LOCK", line 82 ORA-06512: at "SYS.DBMS_LOCK", line 110 ORA-06512: at line 1 COMMENTS: It is a replacement of JR43231.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of BPM Express, BPM Standard and BPM * * Advanced. * **************************************************************** * PROBLEM DESCRIPTION: Lock Timeouts can occur on the * * Performance Data Warehouse database. * **************************************************************** * RECOMMENDATION: * **************************************************************** Primary key generation with auto-tracking enabled can cause the Performance Data Warehouse server to stop processing during report generation. Symptoms in the logs are repeated lock wait timeouts such as the following (example is for Oracle, where this has been observed): org.springframework.jdbc.BadSqlGrammarException: ConnectionCallback; bad SQL grammar []; nested exception is java.sql.SQLSyntaxErrorException: ORA-02049: timeout: distributed transaction waiting for lock ORA-06512: at "SYS.DBMS_LOCK", line 82 ORA-06512: at "SYS.DBMS_LOCK", line 110 ORA-06512: at line 1
Problem conclusion
The fix for this APAR makes the primary key block size value configurable. The lower the primary key block size, the more often the server needs to request new blocks from the database; each time a block is acquired, the transaction acquires a table lock. This increases the probability of a deadlock (or lock timeout), as one transaction must wait on another to complete and release the table lock. Increasing the primary key block size reduces the number of requests for blocks and hence the probability of deadlocks. Fix is available on Fix Central: http://www.ibm.com/support/fixcentral. Search for JR45327. After you select the product group, product, installed version, and platform, click Continue and then select APAR or SPR, enter JR45327, and click Continue. When downloading 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. Note that this interim fix is a replacement of the JR43231 interim fix.
Temporary fix
Comments
APAR Information
APAR number
JR45327
Reported component name
BPM ADVANCED
Reported component ID
5725C9400
Reported release
751
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-01-09
Closed date
2013-02-05
Last modified date
2013-12-16
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
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5.1","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
12 October 2021