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 IC83427 Status: Closed

UNWANTED MESSAGES DISPLAYED ON CONSOLE WHEN DB2IUPDT IS RUN

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
When an instance is updated to new fixpack level using db2iupdt 
results in unwanted messages being displayed on screen. 
 
# ./db2iupdt reginst 
Sun Microsystems Inc.   SunOS 5.10      Generic January 2005 
Sun Microsystems Inc.   SunOS 5.10      Generic January 2005 
/opt/IBM/db2/V9.5/instance/db2ickts: /tmp/db2ickts.tmp.12338: 
bad number 
cat: cannot open /tmp/db2ickts.tmp.12338 
/opt/IBM/db2/V9.5/instance/db2ickts: token: parameter null or 
not set 
DBI1070I  Program db2iupdt completed successfully.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL LU Platform                                              * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to new fixpack                                       * 
****************************************************************
Local Fix:
Solution
v95 fp10, v97 fp6 and v101fp1. db2iupdt will work fine.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC83468 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.05.2012
28.08.2012
28.08.2012
Problem solved at the following versions (IBM BugInfos)
9.5.FP10
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.10 FixList