The log fills up when an application (or utility) that updates DB2 has processed more transactions in a single unit of work (without any commits) than can be stored in the circular log files.
First you will need to complete the disposition of application handle 27 (COMMIT, ROLLBACK or FORCE APPLICATION), which I assume is the application that caused the problem.
To increase the logs size you need to change one or more (preferably all) of the following parameters:
Logprimary (the number of primary log files – default is 3)
Logsecond (the number of secondary log files – default is 2)
Logfilsiz (the number of 4K pages of each logfile – default is 1000 on Unix, 250 on Windows)
You can increase these with the following syntax (example values are given):
db2 connect to testkala
db2 update db cfg using logprimary 5
db2 update db cfg using logsecond 10
db2 update db cfg using logfilsiz 10000
db2 connect reset
You can also use the Control Center database configuration to change these values. These parameters will take affect after all applications have disconnected from the database.
To help alleviate this problem in the future, make sure your application or utility (such as import) does frequent commits every 100 – 1000 updates. For the import utility, you can specify the COMMITCOUNT n parameter.
M. A. Feldman
IBM Certified DBA on DB2 for Linux, UNIX, and Windows
IBM Certified DBA on DB2 for z/OS and OS/390