The destruction of the DB2-964 issue is simple!

This article describes the correct solution to the DB2-964 issue. If you are curious about the correct solution to the DB2-964 issue, the following articles will unveil its mysteries. The following is a detailed description of the relevant content, hoping to help you in this regard.

 
 

  
  
SQLState '57011' and errorCode '-964' 
 
 

Find the reason DB2 "? SQL = 0964"

Cause: the database log file is full.

Solution: Increase the log file size), increase the number of log files, and increase the number of auxiliary log files. You can select any of the three modification parameters)

View database configuration parameters: db2 "get db cfg | Grep LOG"

Log File size 4 kb) (LOGFILSIZ) = 1024 the size of each log file is 1024*4 kb = 4 MB)

Number of Primary log files (LOGPRIMARY) = 3

Number of auxiliary log files (LOGSECOND) = 1

Modify database configuration parameters: db2 "update db cfg Using

"

Modify the log file size: db2 "update db cfg Using LOGFILSIZ 4096"

Modify the number of master log files: db2 "update db cfg Using LOGPRIMARY 6"

Modify the number of auxiliary log files: db2 "update db cfg Using LOGSECOND 10"

The above content is an introduction to the solution to the db2-964 problem. I hope you will have some gains.