DB2 - Problem description
Problem IC76689 | Status: Closed |
SQL1224N WHILE CREATING AN EXTENDED INDEX WHEN DB2_MEMORY_PROTEC T IS ENABLED AND DB CFG PARAMETER INDEXSORT IS SET TO NO | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
CREATE INDEX IKT_P_01_IDX ON IKT_P_01 (Data) EXTEND USING SingleExt DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command. During SQL processing it returned: SQL1224N The database manager is not able to accept new requests, has terminated all requests in progress, or has terminated the specified request because of an error or a forced interrupt. SQLSTATE=55032 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users who have enabled DB2_MEMORY_PROTECT on AIX with * * storage key support and db cfg parameter INDEXSORT is set to * * NO * **************************************************************** * PROBLEM DESCRIPTION: * * CREATE INDEX IKT_P_01_IDX ON IKT_P_01 (Data) EXTEND USING * * * * SingleExt * * * * * * * * DB21034E The command was processed as an SQL statement * * because * * it was not a * * * * valid Command Line Processor command. During SQL processing * * it * * returned: * * * * SQL1224N The database manager is not able to accept new * * * * requests, has * * * * terminated all requests in progress, or has terminated the * * * * specified request * * * * because of an error or a forced interrupt. SQLSTATE=55032 * **************************************************************** * RECOMMENDATION: * * Upgrade to V97 FP5 * **************************************************************** | |
Local Fix: | |
Disable DB2_MEMORY_PROTECT. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
Solution | |
Problem first fixed in V97FP5 | |
Workaround | |
Disable DB2_MEMORY_PROTECT | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 31.05.2011 07.12.2011 07.12.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP5 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.5 |