DB2 - Problembeschreibung
Problem IC90132 | Status: Geschlossen |
DBI1264E ERROR DURING CLIENT INSTANCE UPGRADE USING DB2IUPGRADE COMMAND | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
When the instance that is to be upgraded to v10.1 using db2iupgrade command is of node type CLIENT, customer will experience the following errors: DBI1264E: Errors were encountered in running db2iupgrade. Please refer to the installation log file /tmp/db2iupgrade.log.PID for more information. DBI1205E One or more local databases cannot be upgraded to the version from which you are running this command. Check the log file /home/<instance>/upgrade.log for the list of errors. The reason behind the errors is that db2iupgrade makes call to the db2iupgrade_local script which includes the following lines of code. They should be commented out as follows: # if [ ${IS_FIRST_HOST?} -eq ${TRUE?} ]; then # chk_databases # fi The chk_databases function calls to db2ckupgrade which validates the existence of local databases. Since this is CLIENT node and no such databases would exist, call to chk_databases should not be made. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 v10.1 FP3. * **************************************************************** | |
Local-Fix: | |
Upgrade to DB2 v10.1 FP3. | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
Lösung | |
db2iupgrade_local script updated with correction in DB2 v10.1 FP3. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC90161 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 11.02.2013 02.10.2013 02.10.2013 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.3 | |
10.1.0.3 |