When you're carrying out an database-intensive operations, like trying to insert a lot of records in one transaction or opening a bunch of connections at the same time, you run the risk of encountering various database configuration-related issues. Below are some of the frequent problems/exceptions that can occur, and their solutions.
- Problem: The error message is SQL0912N. This tell you that the maximum number of lock requests has been reached for the database.
Solution Increase the locklist using the following DB2 command:
<new_value> is the value you are assigning to the parameter. The default value for LOCKLIST is 100.
db2 update db cfg for <database_name> using LOCKLIST <new_value>
- Problem: The error message is SQL0964C. This means the transaction log for the database is full.
Solution: Increase the primary and secondary DB2 logs using the following commands:
You might also need to increase the log file size using the following command:
DB2 update db cfg for <database_name> using LOGPRIMARY <new_value>
DB2 update db cfg for <database_name> using LOGSECOND <new_value>
DB2 update db cfg for <database_name> using LOGFILSIZ <new_value>