SEO

#1 (**permalink**) 02-27-2008, 06:31 AM

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

#2 (**permalink**) 02-27-2008, 06:31 AM

<bikkaran@in.ibm.com> wrote in message
news:1143351909.835247.320350@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..

#3 (**permalink**) 02-27-2008, 06:31 AM

Mark A wrote:
> <bikkaran@in.ibm.com> wrote in message
> news:1143351909.835247.320350@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

#4 (**permalink**) 02-27-2008, 06:35 AM

bikkaran@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

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

Transaction Log full.