DB2 - Problem description
Problem IT34913 | Status: Closed |
SQL1227N ERROR WITH RC 11 WHEN RESETTING AVGPARTITION_CLUSTERRATIO COLUMN VALUE DURING INDEX STATS RESET. | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
SQL1227n error with RC 11 when resetting AVGPARTITION_CLUSTERRATIO column value during index stats reset. The following error message can be seen as a result of the update: B21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command. During SQL processing it returned: SQL1227N The catalog statistic "100" for column "AVGPARTITION_CLUSTERRATIO" is out of range for its target column, has an invalid format, or is inconsistent in relation to some other statistic. Reason Code = "11". SQLSTATE=23521 There are case when we just update AVGPARTITION_CLUSTERRATIO and not AVGPARTITION_CLUSTERFACTOR causing this error. The APAR fix will address this issue. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All Users on DB2 v111m4FP5 and earlier * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 v111m4FP6 * **************************************************************** | |
Local Fix: | |
N/A | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * All Users on DB2 v111m4FP5 and earlier * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 v111m4FP6 * **************************************************************** | |
Comment | |
First Fixed in DB2 v111m4FP6 | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 12.11.2020 15.03.2021 15.03.2021 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |