TGIF!!!!!!!!!!!!


Yesterday While I was out, process db2ckpwd was consuming resources like
a pig in heaven.
Anyone run into this proplem yet? What did you do to solve this?




I found on the internet Dogpile and Googole AIX authentication APARs
may impact DB2 password checking daemons (db2ckpwd processes) causing a
variety of symptoms, including authentication errors, hangs, and DB2
crashes.

Content

DB2's password checking daemons (db2ckpwd processes) are vulnerable to
various AIX 5.3 authentication APARs (IY71365, IY75151, IY78341,
IY84813, IY86265, IY86266, IY90020). These can result in authentication
errors, hangs/looping, and crashes, . It is therefore generally
recommended to disable the password checking daemons by issuing "db2set
DB2_NUM_CKPW_DAEMONS=0" and recycling the instance. A minimum of DB2
Version 8.1 Fixpak 11 is recommended for this setting due to DB2 APAR
IY82133. ( see
http://www.ibm.com/support/docview.wss?rs=71&uid=swg1IY82133 )

On systems with high authentication rates, disabling password checking
daemons may cause performance degradation as each authentication will
require forking a separate process (db2ckpw). In the case where password
checking daemons cannot be disabled, it is recommended to obtain the
applicable interim fixes from AIX support. See the following document
for information on the most current AIX APARs and recommended minimum
maintenance levels:
http://www.ibm.com/support/docview.wss?rs=71&uid=swg21165448



We're at DB2 Version 8.1 Fixpak 10. We always seem to be a day late and
a dollar short



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