IBM BPM, V8.0.1, All platforms > Troubleshooting and support > Troubleshooting installation and configuration

Resolving a DB2 process load issue

You can encounter unexpected process load issues when running DB2

The following error message displays when DB2 encounters a process load issue: 

CWLLG2068E: An unexpected exception occurred during an attempt to generate the next primary key.   
Error: org.springframework.jdbc.UncategorizedSQLException: PreparedStatementCallback; uncategorized SQLException for SQL [update lsw_pri_key set high_key = ? where table_id = ?]; SQL state [57011]; error code [-964]; DB2 SQL Error: SQLCODE=-964, SQLSTATE=57011, SQLERRMC=null, DRIVER=3.61.65; nested exception is com.ibm.db2.jcc.am.SqlException: DB2 SQL Error: SQLCODE=-964, SQLSTATE=57011, SQLERRMC=null, DRIVER=3.61.65
BPM databases are maintained by an administrator. If your BPM databases are maintained by a database administrator, gather the server log files and FFDC entries, and then consult the database administrator. For IBM DB2, the database administrator must adjust the settings for LOGFILSIZ, LOGPRIMARY and LOGSECOND based on your environment.

Tip: BPMDB and PDWDB are the default database names.

If you used different database names during the installation, substitute the correct database name.

To increase the LOGFILSIZ, use the following command, where xxxx is the new value for the LOGFILSIZ: db2 update database config for BPMDB using LOGFILSIZ xxxx

Increasing the number of primary and secondary logs is done with a similar command, where yy and zz are the new values:

You must update these settings for both the BPMDB and the PDWDB.

Increasing the LOGPRIMARY value also increases the disk requirements for the log files because the primary log files are preallocated during the very first connection to the database. Each log file has a size that is equal to LOGFILSIZ. You can use the database system monitor to help size the primary log files. See the IBM DB2 documentation for more information about these values and how to monitor them. The correct value for these parameters is specific to your environment. When you increase these values, increase them in small increments from their current settings until the problem is resolved.

: Troubleshooting installation and configuration