Gurus:

DB2 UDB V8.2, Solaris SunOS 5.9 . Actually the full message is:

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

Followed by:

ZRC=0x85100009=-2062548983=SQLP_NOSPACE
"Log File has reached its saturation point"
DIA8309C Log file was full.

User is trying to do a massive number of deletes, but not emptying the
table. Doesn't seem interested in or doesn't know how to code ALTER
TABLE tablename ACTIVATE NOT LOGGED INITIALLY.

It's a training system which is treated like production. We have
increased the size of the LOGFILSZ to 2048, increased LOGPRIMARY to 15
and increased LOGSECOND to 100, and he still gets the message. Will
changing BLK_LOG_DSK_FUL to yes or increasing MAX_LOG from zero to some
higher value help?

Ken Cofield
Group Health Cooperative
Database Consultant, ISD - EDM

>CONFIDENTIALITY NOTICE:
>This message and any attached files might contain confidential
information protected by federal and state law. The information is
intended only for the use of the individual(s) or entities originally
named as addressees. The improper disclosure of such information may be
subject to civil or criminal penalties. If this message reached you in
error, please contact the sender and destroy this message. Disclosing,
copying, forwarding, or distributing the information by unauthorized
individuals or entities is strictly prohibited by law.
>



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