Does anybody know if these four APARs identified in FixPak 10a address only
problems introduced by FixPak 10, or do these also apply to previous
FixPaks? We're currently running fp7 on our DB2 UDB Servers (AIX).
-------------------------------------------------------
Bill Gallagher
Database Administrator
Information Technology
Infrastructure / Operations
Phoenix Life Insurance Company
860-403-1773
[EMAIL PROTECTED]
----- Forwarded by BILL GALLAGHER/PLI/PNX on 09/17/2003 08:24 PM -----
DB2ecare
<[EMAIL PROTECTED] To: undisclosed-recipients: ;
ibm.com> cc:
Subject: DB2 Alert: Version 7 FixPak 10a
now available
09/17/2003
07:20 PM
Dear DB2 Alert subscriber:
DB2 Service announces the release of DB2 Universal Database Version 7.2
FixPak 10a.
Download this FixPak and its associated documentation from the DB2
Technical Support site:
http://www-3.ibm.com/cgi-bin/db2www/data/db2/udb/winos2unix/support/download.d2w/report
Please note that FixPak 10a is not yet available for non-English versions
of DB2 for Windows and OS/2. A separate notification will be sent out once
these become available.
This FixPak contains fixes for the following four APARs:
IY44816: Longer than normal database activations or first connects
If you have recoverable logging configured (LOGRETAIN=ON or USEREXIT=ON)
and more than 4 GB of log space configured ( (LOGPRIMARY+LOGSECOND) *
LOGFILSIZ * 4K ), you may experience longer than normal database
activations or first connects. If the database is consistent at the time
of activation, DB2 will unnecessarily reallocate log files, which is the
reason for slow activation. This behavior may lead to rollforward or crash
recovery failures. If these reallocated log files are used during a
rollforward, the rollforward will fail with SQL1265 - archive log file is
not associated with the current log sequence. A previous log file
reallocation may result in the recreated log file not chained correctly
with the previous log file. Rollforward fails when trying to process this
log file. Crash recovery may fail when running a very large transaction
requiring log space that spans across greater than 4 GB of active log
space. This causes a wrong log sequence number to be written to the
transaction logs on disk, which will cause DB2 crash recovery to fail.
IY47686: Search Discovery Listener Denial of Service Vulnerability
A vulnerability exists in the DB2 "Discovery" service that allows a skilled
remote user to cause the Discovery service to stop responding by sending a
malicious network packet. This creates a denial of service situation for
the Discovery service only. If search discovery was being relied on to find
DB2 servers on a local subnet, these would not be found after the listener
was disabled.
IY47987: db2job security exposure
An exposure exists in the db2job and db2job2 programs that could allow a
skilled user with local login access to a UNIX system where DB2 is
installed to obtain system administrator ("root") privileges.
IY47653: db2licm buffer overflow
A buffer overflow vulnerability exists in the db2licm program that would
allow a skilled user with local login access to a UNIX system where DB2 is
installed to obtain system administrator ("root") privileges.
About DB2 Alert
DB2 Alert provides e-mail notification of critical or pervasive DB2
customer support issues. You have received this e-mail because someone
(likely you) has asked to receive DB2 Alert announcements. If you wish to
unsubscribe or change your e-mail address, please visit the DB2 Alert page
at the DB2 Technical Support site:
http://www.ibm.com/cgi-bin/db2www/data/db2/udb/winos2unix/support/db2alert.d2w/report
Thank you for subscribing to DB2 Alert.
DB2 Universal Database web-based technical support team
[EMAIL PROTECTED]
***********************************************************************************
CONFIDENTIAL: This communication, including attachments, is intended only for the
exclusive use of addressee and may contain proprietary, confidential and/or privileged
information. If you are not the intended recipient, you are hereby notified that you
have received this document in error, and any use, review, copying, disclosure,
dissemination or distribution is strictly prohibited. If you are not the intended
recipient, please notify the sender immediately by return e-mail, delete this
communication and destroy any and all copies of this communication.
***********************************************************************************
-
::: When replying to the list, please use 'Reply-All' and make sure
::: a copy goes to the list ([EMAIL PROTECTED]).
*** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
*** For more information, check http://www.db2eug.uni.cc
