Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC89100 Status: Closed

REORG FAILS WITH SQL2216N IN DPF ENVIRONMENT

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
REORG TABLE may fail in DPF environment after an 
alter table drop column statement has been issued. 
 
The reported error is SQL2216 with a reason code of -301 or 
-420.. 
example: 
SQL2216N  SQL error "-301" occurred while reorganizing a 
database table or its 
indexes. 
 
 
The db2diag.log msg may report as follows.. 
 
2012-11-06-19.51.32.409907-300 I2707103A598         LEVEL: 
Severe 
PID     : 28020                TID : 1324           PROC : 
db2sysc 763 
INSTANCE: regress2             NODE : 763           DB   : 
SCHEMADB 
APPHDL  : 19-1449              APPID: *N19.regress2.121107005008 
AUTHID  : REGRESS2             HOSTNAME: reghpiac7k06 
EDUID   : 1324                 EDUNAME: db2agntp (SCHEMADB) 763 
FUNCTION: DB2 UDB, data management, sqldMapAlteredZval, 
probe:1828 
RETCODE : ZRC=0x80160016=-2146041834=SQLRXICT3 "incompatible 
types" 
          DIA8022C Incompatible data type "" used with an 
EXECUTE or OPEN. 
 
2012-11-06-19.51.32.472267-300 I2707702A624         LEVEL: 
Warning 
PID     : 28020                TID : 1324           PROC : 
db2sysc 763 
INSTANCE: regress2             NODE : 763           DB   : 
SCHEMADB 
APPHDL  : 19-1449              APPID: *N19.regress2.121107005008 
AUTHID  : REGRESS2             HOSTNAME: reghpiac7k06 
EDUID   : 1324                 EDUNAME: db2agntp (SCHEMADB) 763 
FUNCTION: DB2 UDB, trace services, sqlt_logerr_string (secondary 
logging function), probe:30 
MESSAGE : Reorg table failed. 
DATA #1 : String, 84 bytes 
Table(2:4)=UNLIMALTPERUOW01.TAB1, Flags=x0111000000004091, 
IID=0, Temp=0, LongTemp=0 
 
2012-11-06-19.51.32.472789-300 I2708327A601         LEVEL: 
Warning 
PID     : 28020                TID : 1324           PROC : 
db2sysc 763 
INSTANCE: regress2             NODE : 763           DB   : 
SCHEMADB 
APPHDL  : 19-1449              APPID: *N19.regress2.121107005008 
AUTHID  : REGRESS2             HOSTNAME: reghpiac7k06 
EDUID   : 1324                 EDUNAME: db2agntp (SCHEMADB) 763 
FUNCTION: DB2 UDB, data management, sqldTableReorgObject, 
probe:4296 
RETCODE : ZRC=0x80160016=-2146041834=SQLRXICT3 "incompatible 
types" 
          DIA8022C Incompatible data type "" used with an 
EXECUTE or OPEN. 
 
2012-11-06-19.51.32.473229-300 I2708929A583         LEVEL: Error 
PID     : 28020                TID : 1324           PROC : 
db2sysc 763 
INSTANCE: regress2             NODE : 763           DB   : 
SCHEMADB 
APPHDL  : 19-1449              APPID: *N19.regress2.121107005008 
AUTHID  : REGRESS2             HOSTNAME: reghpiac7k06 
EDUID   : 1324                 EDUNAME: db2agntp (SCHEMADB) 763 
FUNCTION: DB2 UDB, relation data serv, sqlrreorg_table, 
probe:550 
MESSAGE : Reorg: DMS return rc = 
DATA #1 : Hexdump, 4 bytes 
0x87FFFFFFE6BFD5F8 : 8016 0016 
....
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* HP - DPF users                                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V10.1 version 10.01.003                           * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Fixed in V10.1 fp3.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.12.2012
27.09.2013
04.02.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList