DB2 - Problem description
Problem IC88632 | Status: Closed |
INCREMENTAL BACKUP FAILS WITH -2044: SQLUMCPROCESSREMAININGBUFFE RS, PROBE:1769. ZRC=0X870F00B9=-2029059911=SQLO_SEM_TIMEOUT | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
Incremental backup might fail with SQLN2044 (-2044) with the following messages in the db2diag.log 2012-06-18-10.09.19.433817+060 E2855440A450 LEVEL: Severe PID : 5898360 TID : 21634 PROC : db2sysc 2 INSTANCE: xxxxxxxxxx NODE : 002 EDUID : 21634 EDUNAME: db2med.20134.3 (xxxxxxxxxx ) 2 FUNCTION: DB2 UDB, database utilities, sqluMCProcessRemainingBuffers, probe:1769 MESSAGE : ZRC=0x870F00B9=-2029059911=SQLO_SEM_TIMEOUT "Return code from sqlowait when time out value has been reached" 2012-06-18-10.09.19.434138+060 E2855891A375 LEVEL: Error PID : 5898360 TID : 21634 PROC : db2sysc 2 INSTANCE: xxxxxxxxxx NODE : 002 EDUID : 21634 EDUNAME: db2med.20134.3 (xxxxxxxxxx ) 2 FUNCTION: DB2 UDB, database utilities, sqluMCProcessRemainingBuffers, probe:1772 MESSAGE : Media controller -- Bad buffer queue handle. 2012-06-18-10.09.19.434233+060 E2856267A420 LEVEL: Error PID : 5898360 TID : 21634 PROC : db2sysc 2 INSTANCE: xxxxxxxxxx NODE : 002 EDUID : 21634 EDUNAME: db2med.20134.3 (xxxxxxxxxx ) 2 FUNCTION: DB2 UDB, database utilities, sqluMCProcessRemainingBuffers, probe:1772 MESSAGE : SQL2044N An error occurred while accessing a message queue. Reason code: "". 2012-06-18-10.09.19.434446+060 E2856688A348 LEVEL: Error PID : 5898360 TID : 21634 PROC : db2sysc 2 INSTANCE: xxxxxxxxxx NODE : 002 EDUID : 21634 EDUNAME: db2med.20134.3 (xxxxxxxxxx ) 2 FUNCTION: DB2 UDB, database utilities, sqluMCProcessRemainingBuffers, probe:1772 DATA #1 : String, 1 bytes 2 2012-06-18-10.09.19.434621+060 E2857037A553 LEVEL: Severe PID : 5898360 TID : 20134 PROC : db2sysc 2 INSTANCE: xxxxxxxxxx NODE : 002 DB : xxxxxxxxxx APPHDL : 2-31105 APPID: xxxxxxxxxx AUTHID : xxxxxxxxxx EDUID : 20134 EDUNAME: db2agent (DLINF01) 2 FUNCTION: DB2 UDB, database utilities, sqlubMWResponse, probe:968 DATA #1 : Sqlcode, PD_TYPE_SQLCODE, 4 bytes -2044 DATA #2 : Hexdump, 6 bytes 0x0A000703E7DD3B30 : FFFF F804 3200 ....2. This error is more likely to happen using the DEDUP_DEVICE option on the backup and in certain circumstances due to not having any data to backup in the tablespace. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.1 and Fix Pack 2 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in DB2 Version 10.1 and Fix Pack 2 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 28.11.2012 17.12.2012 17.12.2012 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.2 | |
10.5.0.2 |