There are basically two types of logging -- archive logging and circular
logging. The LOGBUFSIZ parameter is used to control the size of the log
buffer, not the size of the log file. Basically, the log buffer is flushed
to the active log when it becomes full or when a transaction commits (or
group of transactions based on the mincommit parameter). Increasing the
logbufsiz will probably not correct your problem.

If you are running circular logging (logretain off), the problem can be
caused in two different ways. One, the number of logs in the primary and
secondary have filled up or Two, you have a "lazy" transaction out there. In
ciruclar logging, log files wrap, meaning that once it goes to the last log,
it will wrap back to the first one, then go to the second, etc. If ones of
those log files still have an uncommitted transaction on it, (held back any
application), you can get a log full error, even though all the other logs
after that one have been processed. To find the culprit in this case, issue
a "db2 get snapshot for all databases | grep oldest" and that will identify
the application that is holding onto the log space. Increasing the size and
number of logs (via LOGFILSIZ, LOGPRIMARY, LOGSECOND) can help resolve these
issues, but if you have a lazy transaction, it will just prolong the time
between log full.



-----Original Message-----
From: Parthasarathy [Partha]
[mailto:db2udbdba-ezmlmshield-x34213294.[Email address protected]
Sent: Tuesday, June 15, 2004 12:15 AM
To: LazyDBA Discussion
Subject: Log full error message- need some help


Hi,
I am getting the error as 'Log full' in diaglog and nfy files.
The error message is as below. What should be done in order NOT
to see this message again. I have increased the LOGBUFFSZ to 8MB
from 2MB. I feel that this will help in resolving this issue.
Any suggestions..... For a 3rd party application where you don't
know waht SQLs they run, any advice in fixing the log size.
Pls help..
Thanks in advance.
Parthahs

ADM1823E The log is full. The active log is held by
application handle "636".
Terminate this application by COMMIT, ROLLBACK or FORCE
APPLICATION.
^^
2004-06-13-22.13.18.623811 Instance:pksdb2 Node:000
PID:126168(db2agent (PKSPRODL) 0) TID:1
Appid:NF000001.B0E8.040613165033
data protection sqlpgResSpace Probe:2860 Database:PKSPROD

ADM1823E The log is full. The active log is held by
application handle "636".
Terminate this application by COMMIT, ROLLBACK or FORCE APPLICATION.




__________________________________
Do you Yahoo!?
Friends. Fun. Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/


---------------------------------------------------------------------
PLEASE CLICK REPLY-ALL TO SEND A REPLY TO EVERYONE
website: http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
For additional commands, e-mail: db2udbdba-[Email address protected]

*************************************************************
This message, including any attachments, may contain
confidential information intended for a specific individual
and purpose, and may be protected by law. If you are not
the intended recipient, please notify the sender by e-mail
or telephone immediately, and then immediately delete this
message. Any disclosure, copying or distribution of this
message, or the taking of any action based on it, by any
unintended recipient is strictly prohibited.

DB2 & UDB email list listserv db2-l LazyDBA home page