The IBM DB2 database can display the CWLLG2068E error message when it is under heavy process load.
The following information displays with this error message:
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 ; 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
Resolving The Problem
Use one of the following solutions to resolve the problem based on your environment:
- Business Process Manager databases are maintained by an administrator.
If your Business Process Manager 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.
- Running a standalone environment
If you are running a standalone Business Process Manager 7.5 environment and are maintaining your own databases, consult the database documentation. For IBM DB2, you might need to adjust the LOGFILSIZ, LOGPRIMARY, and LOGSECOND parameters. To find the current values of these parameters on IBM DB2, issue the following commands from a command prompt:
- db2 get database config for BPMDB
- db2 get database config for PDWDB
Note: BPMDB and PDWDB are the default database names. If you used different database names during the installation, substitute the correct database name.
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:
- db2 update database config for BPMDB using LOGPRIMARY yy
- db2 update database config for BPMDB using LOGSECOND zz
You must update these settings for both the BPMDB and the PDWDB.
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.
Was this topic helpful?
15 June 2018