suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT29768 Status: Closed

DB2 PURESCALE MEMBER MAY HIT FODC_PANIC DUE TO XI FAILURES IN RUSCENARIO.

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
After updating the CF's to V11.1.4.4, members on V11.1.4.4 may
begin to experience XI failures if there are any members
remaining on the previous Db2 level. Eventually, these errors
may cause the member to FODC.

This is due to the primary CF on the V11.1.4.4 level being
unable to invalidate pages on down level members on behalf of
V11.1.4.4 members. This will often result in the V11.1.4.4
members reaching the communication timeout and causing a FODC 6
minutes after the initial XI failures.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher                *
****************************************************************
Local Fix:
This issue can be avoided by updating all members to a higher
level before updating the CFs. If the cluster is already in a
state with mixed level members, shutdown the lower level members
and update them to V11.1.4.4 before bringing them back online.
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
18.07.2019
16.01.2020
16.01.2020
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)