|
Problem IC93316
|
Status: Closed |
DB2IUPGRADE MAY RETURN MISLEADING "CTRL/.INSTUSE" ERRORS BECAUSE IT CHECKS OTHER UNRELATED INSTANCES |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
When you upgrade a DB2 V.9.7 instance to V.10.1 you might see
error messages related to sqllib/ctrl/.instuse:
E.g.: db2iupgrade -k -u db2inst1 db2inst1
Task #2 start
Description: Initializing instance list
Estimated time 5 second(s)
cat: cannot open /home/db2inst2/sqllib/ctrl/.instuse
cat: cannot open /home/db2inst2/sqllib/ctrl/.instuse
cat: cannot open /home/db2inst2/sqllib/ctrl/.instuse
cat: cannot open /home/db2inst2/sqllib/ctrl/.instuse
Task #2 end
...
Upgrade itself completes successfully, though.
This problem can occur if there are multiple instances created
on this machine, but at the time of upgrading the filesystem of
instance db2inst2 might not available, so that
sqllib/ctrl/.instuse of that other instance is not accessible.
This issue happens because db2iupgrade internally attempts to
access .instuse file of other unrelated instances. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL USERS ON UNIX PLATFORM *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.1 Fix Pack 3. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 Version 10.1 Fix Pack 3. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC95455
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 24.06.2013
08.10.2013
08.10.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
