DB2 transaction log full, or log disk space is full solution

Concept:

Transaction log full indicates that the current transaction could not be written to the active log (the primary log file and the secondary log file have all been exhausted or there is not enough space for the current transaction to write)

The log disk space is full, the secondary log file is not used, and the disk space is full.

The DB2 database transaction log files are divided into primary and secondary log files, the primary log files are allocated space, and secondary log files are redistributed when they are used.

To view the transaction log configuration (mid is the database name):

DB2 get DB CFG for mid

Run Result: Log file Size (4KB) (LOGFILSIZ) = 1024
Number of primary log files (LOGPRIMARY) = 13
Number of secondary log files (LOGSECOND) = 4
Changed path to log file (Newlogpath) =

Log file Path = D:\DB2\NODE0000\SQL00003\SQLOGDIR\

Total transaction log capacity size = (Logprimary+logsecond) *logfilsiz*4k

PS: (13+4) *1024*4KB=68MB

Transaction log Full resolution:
(1) Increase the log file size:
DB2 Udpate DB CFG for mid using LOGFILSIZ 8192
or increase the number of primary log files:
DB2 Update DB CFG for mid using LOGPRIMARY 15
or increase the number of secondary log files:

DB2 Update DB CFG for mid using LOGSECOND 10 (2) Stop the application that caused this error or stop all applications and restart the database
DB2 Force applications All
DB2 force application (application handle obtained through DB2 list applications)
Db2stop
Db2start