home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IC72509 Status: Closed

DB2IPRUNE -R <response FILE> -O <output DIRECTORY> PRUNES TSAMP
AND ITMA FROM SOURCE IMAGE IF DB2 COMPONENTS CAN NOT BE PRUNED.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
If DB2 products, features or languages cannot be pruned for some 
reason, but TSAMP or ITMA is selected to be pruned. These 
components will be pruned from the source image. 
 
For example, if there is insufficient space on the file system 
and TSAMP and ITMA are selected to be pruned, these 
components will be pruned from the source image instead. 
 
e.g. Prune to an output directory 
 
# ./db2iprune -r /tmp/db2server.rsp -o /db2temp/V9.7/server2 -l 
 
/tmp/db2iprune.log 
 
DBI1446I  The db2iprune command is running, please wait. 
 
 
   A minor error occurred during the execution. 
 
 
 
   For more information see the DB2 installation log at 
 
   "/tmp/db2iprune.log". 
 
# cat /tmp/db2iprune.log 
 
... 
ERROR: There is not enough free disk space in 
"/db2temp/V9.7/server2". Free 
space detected in "/db2temp/V9.7/server2" is "502800384", while 
space needed is 
"1345843200". Free up additional space and try again. 
 
Pruning DB2 file sets :.......Failure 
Pruning SA MP :.......Success 
Pruning IBM Tivoli Monitoring for Databases :.......Success 
... 
 
After applying the fix, the tasks following the failed task will 
not be executed and thus, TSAMP and ITMA will not be attempted 
to be pruned.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users prior to DB2 V97 FP4.                                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* DB2IPRUNE -R <response FILE> -O <output DIRECTORY> PRUNES    * 
* TSAMP                                                        * 
* AND ITMA FROM SOURCE IMAGE IF DB2 COMPONENTS CAN NOT BE      * 
* PRUNED.                                                      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade DB2 to V97 FP4.                                      * 
****************************************************************
Local Fix:
available fix packs:
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

Solution
Problem is first fixed in DB2 V97 FP4.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC72858 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
10.11.2010
12.05.2011
12.05.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP4
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.4 FixList