DB2 - Problembeschreibung
Problem IC84571 | Status: Geschlossen |
IN DPF ENVIRONMENT, DURING CONCURRENT XA TRANSACTIONS DECLARE GLOBAL TEMP TABLE MAY FAIL WITH SQL0901 | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
Due to a timing issue, in DPF environment, during concurrent XA transactions Declare Global Temp Table may fail with sql0901. The db2diag.log reports severe error that the table ID already exists and FODC_AppErr report is generated as well: 2011-09-09-10.16.54.685400-420 I338342A680 LEVEL: Severe PID : 758298 TID : 26786 PROC : db2sysc 0 INSTANCE: db2inst NODE : 000 DB :SAMPLE APPHDL : 0-9953 APPID: REMOTE01.INA400.C858FC1BA635 AUTHID : DB2USER EDUID : 26786 EDUNAME: db2agntp (DWP01) 0 FUNCTION: DB2 UDB, buffer pool services, sqlbReserveFileToken, probe:10 DATA #1 : String, 80 bytes Error: ReserveFileToken was called to reserve a token that was already allocated DATA #2 : String, 9 bytes PoolID = DATA #3 : Pool ID, PD_TYPE_SQLB_POOL_ID, 2 bytes 29 DATA #4 : String, 8 bytes Token = DATA #5 : unsigned integer, 2 bytes 3 | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.1 Fix Pack 1 * **************************************************************** | |
Local-Fix: | |
As a workaround, follow the steps below: 1. Stop db2 instance db2stop or hastopdb2 2. Set the registry: db2set APM_THROTTLE=30 3. Start db2 instance db2start or hastartdb2 | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows | |
Lösung | |
First fixed in Version 10.1 Fix Pack 1 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 14.06.2012 10.12.2012 10.12.2012 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.1 | |
10.5.0.1 |