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

DB2IPRUNE.EXE DOES NOT WORK CORRECTLY WHEN IT IS USED TO PRUNE THE MERGED
DB2 INSTALL IMAGES: SERVER, UNIVERSAL

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
DB2IPRUNE.EXE fails to prune the merged db2 install images that 
released in fixpak releases, such as SERVER and UNIVERSAL. 
 
The following are the scenarios where you can see this problem: 
 
  (1). To prune some db2 products from the SERVER image, such as 
ESE, WSE; 
 
  (2). To prune some db2 components, such as ITMA and/or others, 
from the SERVER image. 
 
The same problem do not happen when the db2ipune.exe tool is 
used to prune an non-merged DB2 install image, such as ESE, EXP, 
etc.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Windows                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* DB2IPRUNE.EXE fails to prune the merged db2 install images   * 
* that released in fixpak releases, such as SERVER and         * 
* UNIVERSAL.The following are the scenarios where you can see  * 
* thisproblem:(1). To prune some db2 products from the SERVER  * 
* image,such asESE, WSE;(2). To prune some db2 components,     * 
* such as ITMA and/orothers,from the SERVER image.The same     * 
* problem do not happen when the db2ipune.exe tool isused to   * 
* prune an non-merged DB2 install image, such as ESE,EXP,etc.  * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB version 9.7 fix pack 3.                   * 
****************************************************************
Local-Fix:
If you have purchased license for the DB2 product, you can 
contact DB2 Support to get the non-merged install image for that 
DB2 product at the fixpak level you want.
verfügbare FixPacks:
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 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Problem was first fixed in DB2 UDB Version 9.7 Fix Pack 3.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC69898 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
03.06.2010
27.09.2010
27.09.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP3
Problem behoben lt. FixList in der Version
9.7.0.3 FixList
9.7.0.3 FixList