BuildForge使用默认的DB2 Express运行时出现ERROR [IBM][CLI Driver][DB2/6000] SQL0964C The tr

sdxh0506

　　在BuildForge安装时使用默认的数据库DB2 express是常见的安装方式，这样可以省去创建数据等配置过程，并且安装运行比较便捷。 但是因为是使用的Express版以及默认的数据库创建过程设置了一些参数。当BuildForge运行一段时间后悔出现ERROR [IBM][CLI Driver][DB2/6000] SQL0964C The transaction log for the database is full. SQLSTATE=57011 问题。经查阅DB2和BuildForges实践，可以通过以下方式解决该问题。
　　ERROR [IBM][CLI Driver][DB2/6000] SQL0964C The transaction log for the database is full. SQLSTATE=57011

Update the database configuration for the project database with:

db2 update db cfg for <siteDBname> using logfilsiz 2000 logprimary 20 logsecond 20

http://publib.boulder.ibm.com/infocenter/cmgmt/v8r4m0/index.jsp?topic=/com.ibm.administeringcm.doc/trs20059.htm


Transaction log file for the database is full
Symptom
This error message displays:
[IBM][CLI Driver][DB2/NT] SQL0964C The transaction log for the
database is full. SQLSTATE=57011
Cause
This message is usually caused when the database log file is not large enough for the application or the application is not updating transactions often enough to prevent the transaction log from becoming full.
Action
1. To obtain the DB2® log file configuration, from a DB2 command prompt, run:
db2 get db cfg for database name
The output related to the log file is displayed. This sample output shows that the database uses five log files, three for primary and two for secondary, respectively. Each file is 1 MB (250 x 4 KB) in size:
Log file size (4KB) (LOGFILSIZ) = 250
Number of primary log files (LOGPRIMARY) = 3
Number of secondary log files (LOGSECOND) = 2
2. Increase LOGFILSIZ, LOGPRIMARY, and LOGSECOND. For example, enter:
db2 update db cfg for database name using
logfilsiz 1000 logprimary 20 logsecond 10
The DB2 command updates the log file size to 4 MB (1000 x 4 KB) in size with 20 primary log files and 10 secondary log files.
3. Restart DB2 using db2stop and db2start.