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

INSTALLFIXPACK MAY NOT INFORM CORRECT ERRORS

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - 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          * 
* indb2prechk is reported as the same in the DB2 installer.For * 
* example, if the instance user's home directory is            * 
* notmounted, you would get the following misleading message   * 
* inthe terminal."The DB2 installer detects that one or more   * 
* DB2instances"<Instance Name>" are still active. Stop the     * 
* activeinstances and rerun the command again."The fixpack     * 
* calls the db2prechk command located in theinstall path to    * 
* check if the instance can be updated.Therefore, applying the * 
* fixpack will update the install pathwith the new script and  * 
* any follow on fixpack installationswill show the correct     * 
* message when the instance user's homedirectory is not        * 
* mounted or inaccessible:DBI1165E Instance<Instance Name> is  * 
* not accessible on thefollowing nodes:<hostname>              * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V9.5 FP6                                          * 
****************************************************************
Local-Fix:
You will not see the new error message by running the old 
script. 
 
The only way to see the new error message would be to install 
the FixPack 6. 
 
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. 
 
Note: db2prechk -i command will create sqllib directory if it 
does not exist.
verfügbare FixPacks:
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Problem was first fixed in V9.5 FP6
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC66939 IC67943 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
02.03.2010
19.07.2010
19.07.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP6
Problem behoben lt. FixList in der Version