DB2 - Problem description
Problem IT06588 | Status: Closed |
Converting instances from one DB2 database product to another may fail with error SQL6031N in V10.1 and V10.5 | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
If you try to upgrade your DB2 instance from DB2 10.1 WSE to 10.1 ESE, it may fail with the following error : SQL6031N Error in the db2nodes.cfg file at line number "0" Reason code "11". Your DB2 instance will become unusable : all db2 commands return the same error and db2set -all is empty | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * DB2 on Windows * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 10.1 FP5 or later * **************************************************************** | |
Local Fix: | |
DROP and RECREATE your DB2 instance | |
Solution | |
The problem was first fixed in DB2 10.1 FP5 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 19.01.2015 27.07.2015 27.07.2015 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.5 |