DB2 FOR LUW / DB2FORLUW / A10 - DB2

The packed descriptor of a Range Partition Table can get 
corrupted when attaching a partition, if the target table 
column(s) have statistics collected, and does not have default 
values defined on its column(s); but the source column(s) 
has/had default values. (The corruption is confined to a wrong 
stats_offset for the column packed descriptor) 
 
In DPF environment, the -901 trap happens during the attach: 
 
alter table t2 attach partition t1p0 starting from (0) ending at 
(9) from table t1p0 
DB21034E  The command was processed as an SQL statement because 
it was not a 
valid Command Line Processor command.  During SQL processing it 
returned: 
SQL0901N  The SQL statement failed because of a non-severe 
system error. 
Subsequent SQL statements can be processed.  (Reason "Packed 
descriptor 
corruption found. Please run RUNSTATS on this table".) 
SQLSTATE=58004 
 
In non-DPF environment, the -901 trap happens during set 
integrity: 
 
set integrity for t2 immediate checked 
DB21034E  The command was processed as an SQL statement because 
it was not a 
valid Command Line Processor command.  During SQL processing it 
returned: 
SQL0901N  The SQL statement failed because of a non-severe 
system error. 
Subsequent SQL statements can be processed.  (Reason "Packed 
descriptor 
corruption found. Please run RUNSTATS on this table".) 
SQLSTATE=58004 
 
The top of stack looks like this: 
Stack #1             Signal #12        Timestamp 
2014-04-28-05.22.20.930414 
0        ossDumpStackTraceEx 
1        OSSTrapFile::dumpEx 
2        sqlo_trce 
3        sqloDumpDiagInfoHandler 
4        __restore_rt 
5        pthread_kill 
6        sqloDumpEDU 
7        sqldDumpContext 
8        sqlrr_dump_ffdc 
9        sqlzeDumpFFDC 
10       sqlzeSqlCode 
11       sqlrrSqlCode 
12       sqlrlc_systables_fetch_from_disk 
13       sqlrlc_systables_load_entry 
14       sqlrlc_load_entry 
15       sqlrlc_request_ulock 
16       sqlrlc_find_request_usage_lock 
17       sqlrlc_systables_fetch

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 5                       * 
****************************************************************

First fixed in Version 10.1 Fix Pack 5

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

27.08.2014
16.07.2015
16.07.2015