2012-11-26 117 views
3

我试过DB2中的一个巨大的插入查询。 INSERT INTO MY_TABLE_COPY(SELECT * FROM MY_TABLE);DB2日志文件限制,SQLCODE:-964

在此之前,我设置如下:

UPDATE DATABASE CONFIGURATION FOR MY_DB USING LOGFILSIZ 70000; 
UPDATE DATABASE CONFIGURATION FOR MY_DB USING LOGPRIMARY 50; 
UPDATE DATABASE CONFIGURATION FOR MY_DB USING LOGSECOND 2; 
db2stop force; 
db2start; 

,我得到这个错误:

DB21034E The command was processed as an SQL statement because it was not a 
valid Command Line Processor command. During SQL processing it returned: 
SQL0964C The transaction log for the database is full. SQLSTATE=57011 

SQL0964C The transaction log for the database is full. 

Explanation: 

All space in the transaction log is being used. 

If a circular log with secondary log files is being used, an 
attempt has been made to allocate and use them. When the file 
system has no more space, secondary logs cannot be used. 

If an archive log is used, then the file system has not provided 
space to contain a new log file. 

The statement cannot be processed. 

User Response: 

Execute a COMMIT or ROLLBACK on receipt of this message (SQLCODE) 
or retry the operation. 

If the database is being updated by concurrent applications, 
retry the operation. Log space may be freed up when another 
application finishes a transaction. 

Issue more frequent commit operations. If your transactions are 
not committed, log space may be freed up when the transactions 
are committed. When designing an application, consider when to 
commit the update transactions to prevent a log full condition. 

If deadlocks are occurring, check for them more frequently. 
This can be done by decreasing the database configuration 
parameter DLCHKTIME. This will cause deadlocks to be detected 
and resolved sooner (by ROLLBACK) which will then free log 
space. 

If the condition occurs often, increase the database 
configuration parameter to allow a larger log file. A larger log 
file requires more space but reduces the need for applications to 
retry the operation. 

If installing the sample database, drop it and install the 
sample database again. 

sqlcode : -964 

sqlstate : 57011 

有什么建议?

+1

你为什么不使用DB/2实用程序来卸载/加载你的桌子吗?实用程序不像使用简单的INSERT语句那样使用日志。 UNLOAD/LOAD对于这类事情来说效率更高。请记住,在INSERT/SELECT操作过程中不能发出COMMITS - 这一切都必须作为单个工作单元进行 - 对于大型表格,这可能会使日志负荷过重。 – NealB

回答

2

我使用了LOGFILSIZ,LOGPRIMARY和LOGSECOND的最大值; 对于Windows,Linux等,LOGFILSIZ的最大值可能不同。但是,您可以尝试一个非常大的数字,并且DB会告诉您最大值是多少。在我的情况下,它是262144.

此外,LOGPRIMARY + LOGSECOND < = 256.我试着每个128,它适用于我的巨大查询。