DB2 - Problem description
Problem IC71206 | Status: Closed |
THE UPGRADE OF THE INSTANCE "DB2" HAS FAILED,DURING DB2 UPGRADE FROM PRIOR V97 VERSION TO V97 | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
This problem only occur when GUI install is used. If you have database in your system and install "V9.7 work with existing", install will fail the following 2 messages. THE UPGRADE OF THE INSTANCE "DB2" HAS FAILED. THE RETURN VALUE IS "2". SQL5055C The content of the database configuration file is not valid | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * WINDOWS * **************************************************************** * PROBLEM DESCRIPTION: * * The fact that this problem only occur when GUI install is * * used. * * * * If you have database in your system and install V9.7 work * * with existing, install will be failed the following 2 * * messages. * * * * THE UPGRADE OF THE INSTANCE "DB2" HAS FAILED. THE RETURN * * VALUE IS "2". * * * * SQL5005C The content of the database configuration file is * * not valid. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 UDB version 9.7 fix pack 4. * **************************************************************** | |
Local Fix: | |
You can choose one of the following step. 1) After failed, execute db2iupgrade.exe manually. For example: "C:\Program Files\IBM\SQLLIB\bin\db2iupgrade.exe" -install /u <username>,<password> DB2 -p "C:\ProgramData\IBM\DB2\DB2COPY1" 2) use silent install and specify KILL_PROCESSES to YES in the response file. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in DB2 UDB Version 9.7 Fix Pack 4 | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC72789 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 15.09.2010 10.05.2011 13.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 |