To solve the problem of full DB2 SQLCODE =-964 log files, use the following code in the program: www.2cto.com insert into a select * from B where ...... there are more than 6 million records inserted into Table a each time. Every time you execute this statement, DB2 returns an error code with the SQLCODE value of-964. Run the db2 sql0964 command to check the cause of the error, DB2 is interpreted as SQL0964C The transaction log for the database is full. then, expand the log file size and the number of log files according to the DB2 instructions. The command is as follows: SQL code db2 update db cfg for MY_DATABASE using LOGFILSIZ 7900 db2 update db cfg for MY_DATABASE using LOGPRIMARY 30 db2 update db cfg f Or MY_DATABASE using LOGSECOND 20 adds that the total log file of the circulating log www.2cto.com is expanded to about GB, and then runs the following command (release the program, close, and restart the data ): SQL code db2 "force application all" db2stop db2start db2 connect to MY_DATABASE user db2inst1 uing db2inst1 the last call contains insert... select... statement stored procedures, the program is executed this time, but the efficiency is too slow. When using cyclic logs, you can consider adjusting the database's commitcount parameter.