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.

how ADM1822W could happen?

P: n/a
I noticed this in db2diag.log. Cou ld somebody expl in how this coul  happen?
ADM1822W The active log is being held by dirty pages. This is not an
error, but database performance may be impacted. If possible, reduce
the database work load. If this problem persists, either decrease the
SOFTMAX and/or increase the NUM_IOCLEANERS DB configuration parameters.
Thanks.
Mar 1 '06 #1
Share this Question
Share on Google+
1 Reply


P: n/a
This is a warning message. It means that:
The active logs has transactions in it that are committed but not
externalized. That's what a dirty page is: a change has been processed in
it, the change has been committed but the page has not been externalized
back in its physical location on disk.

The transaction is in the log file but the log file has to remain active
until all trans. have been either rolled back or committed AND externalized.

SOFTMAX causes some externalization to happen when it is hit. Default value
100% of a log file size.
NUM_IOCLEANERS is a parm, default value 1, that determines the number of
processes that can be dispatched to clean, meaning externalize, data pages
to their location. They're like janitors; if you don't have enough of them
in the school, the classroom stay dirty too long and you can't use them.
SOFTMAX is one of the foremen who dispatches the janitors.

HTH, Pierre.

--
Pierre Saint-Jacques
SES Consultants Inc.
514-737-4515
<sh*******@gmail.com> a écrit dans le message de news:
11**********************@u72g2000cwu.googlegroups. com...
I noticed this in db2diag.log. Cou ld somebody expl in how this coul  happen?
ADM1822W The active log is being held by dirty pages. This is not an
error, but database performance may be impacted. If possible, reduce
the database work load. If this problem persists, either decrease the
SOFTMAX and/or increase the NUM_IOCLEANERS DB configuration parameters.
Thanks.


Mar 1 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.