home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT05043 Status: Geschlossen

db2iupgrade failed in upgrade a pureScale instance a special build based on
DB2 10.5 FP4 - DBI20164E

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
Symptom 
======= 
 
The db2iupgrade tool fails with the error (db2iupgrade log): 
 
DBI20164E  The db2iupgrade command failed because of a problem 
with the DB2 product installation on a host machine in the DB2 
cluster. 
 
In the /tmp/db2log/DB2Validation.trc of any of the remote hosts, 
there is an error, "Version mismatch", in the step 
INSTALLED_DB2_VERSION_REMOTE: 
 
2491  |||\ 1 db2iHostInfo::WriteReturnKey EXIT Fri Sep 26 
04:36:09 2014 --  , INT = 0 
12492  |||/ 1 db2iHostInfo::WriteInputKey ENTRY Fri Sep 26 
04:36:09 2014 --  , 
12493  |||| 1 db2iHostInfo::WriteInputKey 10 -DATA-  , STRING = 
INSTALLED_DB2_VERSION_REMOTE   <--- 
12494  |||| 1 db2iHostInfo::WriteInputKey 890 -DATA-  , STRING = 
10.5.0.4 
12495  |||\ 1 db2iHostInfo::WriteInputKey EXIT Fri Sep 26 
04:36:09 2014 --  , INT = 0 
12496  ||| 1 IValidatorInstallLocation::isValidRHLoc 50 -DATA- 
, STRING = Version mismatch     <--- 
 
Reason and Prerequisites 
================== 
 
Before DB2 10.5 FP4, during a DB2 version upgrade of a DB2 
pureScale instance, the db2iupgrade tool only upgraded the local 
host and thus had to be run on each of the participating cluster 
hosts individually. 
 
In DB2 10.5 FP4, the default behaviour has been changed to use 
the "-g" parameter, that upgrades all the members and CFs 
(globally) in the DB2 pureScale cluster. During this process, 
the db2iupgrade tool checks the validity of the remotely 
installed DB2 software. There is a programming error on this 
validating process against a special build resulting in the 
mentioned failure. 
 
This problem affects all platforms supported for pureScale (AIX 
and LinuxAMD64); and it covers both the DB2 9.8 (pureScale) to 
10.5 FP4 (pureScale) upgrade and the DB2 10.1 (pureScale) to 
10.5 FP4 (pureScale) upgrade. 
 
This problem is planned to be addressed in a future 10.5 Fix 
Pack.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* It only affects special build made on top of DB2 10.5 FP4    * 
* with the command db2iupgrade against a pureScale enabled     * 
* system during a version upgrade.                             * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* In the db2iupgrade.log, there is DBI20164E  The db2iupgrade  * 
* command failed because of a problem with the DB2 product     * 
* installation on a host machine in the DB2 cluster.           * 
*                                                              * 
*                                                              * 
*                                                              * 
* In one of the host:                                          * 
* db6c3lp07 (2nd member): /tmp/db2log/DB2Validation.trc:       * 
* 12491  |||\ 1 db2iHostInfo::WriteReturnKey EXIT Fri Sep 26   * 
* 04:36:09 2014 --  , INT = 0                                  * 
* 12492  |||/ 1 db2iHostInfo::WriteInputKey ENTRY Fri Sep 26   * 
* 04:36:09 2014 --  ,                                          * 
* 12493  |||| 1 db2iHostInfo::WriteInputKey 10 -DATA-  ,       * 
* STRING = INSTALLED_DB2_VERSION_REMOTE   <-- could this be    * 
* the problem?  But I've installed same version of FP4SB       * 
* 12494  |||| 1 db2iHostInfo::WriteInputKey 890 -DATA-  ,      * 
* STRING = 10.5.0.4                                            * 
* 12495  |||\ 1 db2iHostInfo::WriteInputKey EXIT Fri Sep 26    * 
* 04:36:09 2014 --  , INT = 0                                  * 
* 12496  ||| 1 IValidatorInstallLocation::isValidRHLoc 50      * 
* -DATA-  , STRING = Version mismatch                          * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* This problem is fixed in DB210.5 FP5.                        * 
****************************************************************
Local-Fix:
The workaround is to revert back to the pre-FP4 db2iugprade 
behaviour in upgrading the pureScale instance on each host one 
by one adding the -L parameter (local).
Lösung
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
20.10.2014
02.02.2015
02.02.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.5 FixList