sql error 964: transaction log is full

[xixi]

hello, we are using db2 udb v8.1 on windows 64 bit, i am trying to
understand the error message , what does the full meaning? i know we
can increase the logfilsiz , logprimary, logseconday to help, but i
need to understand what is the right number to change. currently we
have three primary log file, each one has file size 16392k, so when
the database created, i see this three files be there, under directory
\DB2\NODE0000\SQL00002\SQLOGDIR, so does full means all three files
has data in it ? our application is auto commit type, so suppose any
update, delete, or write should commit right away, so commit is taking
as often as possible, also since our write use prepare statement, so i
can't evaulate how much data is writing each time, but i don't think
it will over the limit of 3 x 16392 k, does this log fil is for each
write? will the log file get cleaned up? thanks for your quick reply

[Mark A]

"xixi" <da****@yahoo.com> wrote in message
news:c0**************************@posting.google.c om...

hello, we are using db2 udb v8.1 on windows 64 bit, i am trying to
understand the error message , what does the full meaning? i know we
can increase the logfilsiz , logprimary, logseconday to help, but i
need to understand what is the right number to change. currently we
have three primary log file, each one has file size 16392k, so when
the database created, i see this three files be there, under directory
\DB2\NODE0000\SQL00002\SQLOGDIR, so does full means all three files
has data in it ? our application is auto commit type, so suppose any
update, delete, or write should commit right away, so commit is taking
as often as possible, also since our write use prepare statement, so i
can't evaulate how much data is writing each time, but i don't think
it will over the limit of 3 x 16392 k, does this log fil is for each
write? will the log file get cleaned up? thanks for your quick reply

If you have circular logging (logretain = no, and no logexit program
defined) then the logs can be reused in a circular fashion when all
applications have committed their work.

If you have an update or delete statement that affects multiple rows, the
autocommit does not take effect until the SQL statement has updated or
deleted all rows.

[Mark A]

"xixi" <da****@yahoo.com> wrote in message
news:c0**************************@posting.google.c om...

hello, we are using db2 udb v8.1 on windows 64 bit, i am trying to
understand the error message , what does the full meaning? i know we
can increase the logfilsiz , logprimary, logseconday to help, but i
need to understand what is the right number to change. currently we
have three primary log file, each one has file size 16392k, so when
the database created, i see this three files be there, under directory
\DB2\NODE0000\SQL00002\SQLOGDIR, so does full means all three files
has data in it ? our application is auto commit type, so suppose any
update, delete, or write should commit right away, so commit is taking
as often as possible, also since our write use prepare statement, so i
can't evaulate how much data is writing each time, but i don't think
it will over the limit of 3 x 16392 k, does this log fil is for each
write? will the log file get cleaned up? thanks for your quick reply

If you have circular logging (logretain = no, and no logexit program
defined) then the logs can be reused in a circular fashion when all
applications have committed their work.

If you have an update or delete statement that affects multiple rows, the
autocommit does not take effect until the SQL statement has updated or
deleted all rows.

[aka]

if logretain is on you might want to backup some of your logs?...

aka
"xixi" <da****@yahoo.com> schrieb im Newsbeitrag
news:c0**************************@posting.google.c om...

hello, we are using db2 udb v8.1 on windows 64 bit, i am trying to
understand the error message , what does the full meaning? i know we
can increase the logfilsiz , logprimary, logseconday to help, but i
need to understand what is the right number to change. currently we
have three primary log file, each one has file size 16392k, so when
the database created, i see this three files be there, under directory
\DB2\NODE0000\SQL00002\SQLOGDIR, so does full means all three files
has data in it ? our application is auto commit type, so suppose any
update, delete, or write should commit right away, so commit is taking
as often as possible, also since our write use prepare statement, so i
can't evaulate how much data is writing each time, but i don't think
it will over the limit of 3 x 16392 k, does this log fil is for each
write? will the log file get cleaned up? thanks for your quick reply

[aka]

if logretain is on you might want to backup some of your logs?...

aka
"xixi" <da****@yahoo.com> schrieb im Newsbeitrag
news:c0**************************@posting.google.c om...

hello, we are using db2 udb v8.1 on windows 64 bit, i am trying to
understand the error message , what does the full meaning? i know we
can increase the logfilsiz , logprimary, logseconday to help, but i
need to understand what is the right number to change. currently we
have three primary log file, each one has file size 16392k, so when
the database created, i see this three files be there, under directory
\DB2\NODE0000\SQL00002\SQLOGDIR, so does full means all three files
has data in it ? our application is auto commit type, so suppose any
update, delete, or write should commit right away, so commit is taking
as often as possible, also since our write use prepare statement, so i
can't evaulate how much data is writing each time, but i don't think
it will over the limit of 3 x 16392 k, does this log fil is for each
write? will the log file get cleaned up? thanks for your quick reply