DB2 - Problembeschreibung
Problem IC93316 | Status: Geschlossen |
DB2IUPGRADE MAY RETURN MISLEADING "CTRL/.INSTUSE" ERRORS BECAUSE IT CHECKS OTHER UNRELATED INSTANCES | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL USERS ON UNIX PLATFORM * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.1 Fix Pack 3. * **************************************************************** | |
Local-Fix: | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
Lösung | |
First fixed in DB2 Version 10.1 Fix Pack 3. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC95455 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 24.06.2013 08.10.2013 08.10.2013 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.3 | |
10.1.0.3 |