home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC84549 Status: Closed

TIMING CONDITIONS LEAD TO SQL0901N ENCOUNTERED BY APD CLEANUP PROCESSING
DURING RANGE PARTITION DETACH

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
There are timing conditions which could lead to SQL0901N 
ENCOUNTERED BY APD CLEANUP PROCESSING DURING RANGE PARTITION 
DETACH. This symptom is similar to APAR IC71664. But it is 
caused by timing conditions not yet addressed by that APAR fix. 
 
Both db2pd and db2 list utilities show ASYNCHRONOUS PARTITION 
DETACH is performing "Finalize detach for partition ...". In the 
db2diag.log, the -901 reported for the asynchronous detach 
process may appear similar to the entry below. 
 
2012-02-13-09.17.05.210933-480 I4180806A876       LEVEL: Severe 
PID     : 4456546              TID  : 14281       PROC : db2sysc 
0 
INSTANCE: dwd01                NODE : 000         DB   : DWD01 
APPHDL  : 0-22322              APPID: *N0.DB2.120311163320 
AUTHID  : DWD01 
EDUID   : 14281                EDUNAME: db2taskp (DWD01) 0 
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, 
probe:300 
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -901   sqlerrml: 60 
 sqlerrmc: A hard invalidation is already taking place for this 
object! 
 sqlerrp : SQLRA0B5 
 sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 
0x00000000 
           (4) 0x00000000      (5) 0xFFFFFFEC      (6) 
0x00000000 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate:
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 1                       * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
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
First fixed in Version 10.1 Fix Pack 1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.06.2012
06.08.2013
06.08.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList