By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,017 Members | 979 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,017 IT Pros & Developers. It's quick & easy.

Transaction Log full.

P: n/a
Hi ,
During some bulk loading of data .. I am frequently encountering the
"Transaction Log Full " error . I am using the " import " command with
"commitcount" being 1000.

Even with such a low commitcount I get this error . As suggested I
have increased the LOGFILSIZ, LOGSECOND,LOGPRIMARY values. The
LOGRETAIN, and USEREXIT value is OFF.

Still I get this error.
Is n't there any method to empty the log file. As i hhave read .
frequent commit does the same. But I am not successful.

Please suggest some way to solve this problem.

Thanks
Bikash

Mar 26 '06 #1
Share this Question
Share on Google+
3 Replies


P: n/a
<bi******@in.ibm.com> wrote in message
news:11**********************@z34g2000cwc.googlegr oups.com...
Hi ,
During some bulk loading of data .. I am frequently encountering the
"Transaction Log Full " error . I am using the " import " command with
"commitcount" being 1000.

Even with such a low commitcount I get this error . As suggested I
have increased the LOGFILSIZ, LOGSECOND,LOGPRIMARY values. The
LOGRETAIN, and USEREXIT value is OFF.

Still I get this error.
Is n't there any method to empty the log file. As i hhave read .
frequent commit does the same. But I am not successful.

Please suggest some way to solve this problem.

Thanks
Bikash


Make sure that the directory where your logs are located has enough free
space. You can also try lowering the commitcount..
Mar 26 '06 #2

P: n/a
Mark A wrote:
<bi******@in.ibm.com> wrote in message
news:11**********************@z34g2000cwc.googlegr oups.com...
Hi ,
During some bulk loading of data .. I am frequently encountering the
"Transaction Log Full " error . I am using the " import " command with
"commitcount" being 1000.

Even with such a low commitcount I get this error . As suggested I
have increased the LOGFILSIZ, LOGSECOND,LOGPRIMARY values. The
LOGRETAIN, and USEREXIT value is OFF.

Still I get this error.
Is n't there any method to empty the log file. As i hhave read .
frequent commit does the same. But I am not successful.

Please suggest some way to solve this problem.

Thanks
Bikash


Make sure that the directory where your logs are located has enough free
space. You can also try lowering the commitcount..


Disk space is not the issue unless DB2 is giving the wrong error code.
If the Log Is Full, the options are to increase the log space or commit
more frequently as indicated.

Bob
Mar 26 '06 #3

P: n/a
bi******@in.ibm.com wrote:
Hi ,
During some bulk loading of data .. I am frequently encountering the
"Transaction Log Full " error . I am using the " import " command with
"commitcount" being 1000.

Even with such a low commitcount I get this error . As suggested I
have increased the LOGFILSIZ, LOGSECOND,LOGPRIMARY values. The
LOGRETAIN, and USEREXIT value is OFF.

Still I get this error.
Is n't there any method to empty the log file. As i hhave read .
frequent commit does the same. But I am not successful.


Maybe you have some triggers firing that cause additional data modifications
that need to be logged? Also, if you insert long records, say 4000 bytes
each, then 1000 inserts can already amount to 4 MB log space (unless
compression etc. comes into play). This is even more because log records
are written for page allocations (when the table grows).

--
Knut Stolze
DB2 Information Integration Development
IBM Germany
Apr 3 '06 #4

This discussion thread is closed

Replies have been disabled for this discussion.