|
Problem IT04820
|
Status: Closed |
AUTOMATIC REORG FAILS WITH SQL0270N FUNCTION NOT SUPPORTED (REASON CODE = "57") FOR MDC TABLE |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
Automatic Reorg might fail for MDC tables and show the following
messages in the db2diag.log
FUNCTION: DB2 UDB, Health Monitor, db2AutoReorgExec, probe:190
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -270 sqlerrml: 2
sqlerrmc: 57
sqlerrp : db2Reorg
sqlerrd : (1) 0x801A006D (2) 0x00000000 (3)
0x00000000
(4) 0x00000000 (5) 0xFFFFF9F2 (6)
0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate: 42997
SQL0270N Function not supported (Reason code = "57").
SQLSTATE=42997
The command issued will show in "db2 reorgchk current statistics
on table" output:
Indicator Name = db.tb_reorg_req
Value = 1
Evaluation timestamp = xxxx
Alert state = Attention
Collection:
Name =
"TESTS"."TESTMDC"
Detail = REORG INDEXES
ALLOW WRITE REBUILD ON DATA PARTITION; TOK1:PARTN; END; SQL270
State = Automation
failed
Evaluation timestamp = xxx
In this case the reorg command is missing either Cleanup or
Reclaim Extents clause to be running online.
57 Online index reorganization is supported on multi-
dimensionally clustered (MDC) or insert time clustering
(ITC)
tables in ALLOW WRITE mode only when the CLEANUP option
or
RECLAIM EXTENTS option is specified. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.1 and Fix Pack 5 *
**************************************************************** |
| Local Fix: |
|
| Solution |
Problem was first fixed in DB2 Version 10.1 and Fix Pack 5 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 08.10.2014
13.07.2015
13.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
|
 |
