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 IC66939 Status: Geschlossen

INSTALLFIXPACK MAY NOT INFORM CORRECT ERRORS

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
The installFixPack command calls the db2prechk command to do 
some pre-checking. However, any error that occurs in db2prechk 
is reported as the same in the DB2 installer. For example, if 
the instance user's home directory is not mounted, you would get 
the following misleading message in the terminal. 
 
 
"The DB2 installer detects that one or more DB2 instances 
"<Instance Name>" are still active. Stop the active instances 
and rerun the command again." 
 
The fixpack calls the db2prechk command located in the install 
path to check if the instance can be updated. Therefore, 
applying the fixpack will update the install path with the new 
script and any follow on fixpack installations will show the 
correct message when the instance user's home directory is not 
mounted or 
inaccessible: 
 
DBI1165E Instance <Instance Name> is not accessible on the 
following nodes: 
<hostname>
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* installFixPack command users                                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The installFixPack command calls the db2prechk command to    * 
* dosome pre-checking. However, any error that occurs          * 
* indb2prechkis reported as the same in the DB2 installer. For * 
* example,ifthe instance user's home directory is not mounted, * 
* you wouldgetthe following misleading message in the          * 
* terminal."The DB2 installer detects that one or more DB2     * 
* instances"<Instance Name>" are still active. Stop the        * 
* activeinstancesand rerun the command again."The fixpack      * 
* calls the db2prechk command located in theinstallpath to     * 
* check if the instance can be updated. Therefore,applying the * 
* fixpack will update the install path with thenewscript and   * 
* any follow on fixpack installations will show thecorrect     * 
* message when the instance user's home directory isnotmounted * 
* orinaccessible:DBI1165E Instance <Instance Name> is not      * 
* accessible on thefollowing nodes:<hostname>                  * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V9.7 FP2                                          * 
****************************************************************
Local-Fix:
Prior to applying the fix pack, check the prerequisites via the 
command, <DB2 Install Path>/instance/db2prechk -i. 
This will show you the correct error message if the prerequisite 
checking had failed.
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Problem was first fixed in V9.7 FP2
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
05.03.2010
10.06.2010
10.06.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP2
Problem behoben lt. FixList in der Version
9.7.0.2 FixList