DB2 - Problem description
Problem IT22610 | Status: Closed |
UNDER RARE CIRCUMSTANCES WHEN HISTORY FILE GROWS MORE THAN 4 GB BACKUP CAN HANG | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
Symptoms would be 1)Backup size grows more than the actual size of database. 2)Traces will show the code path.sqluhFillBackupBuffer being called in a loop 12760 entry DB2 UDB Recovery History File sqluhFillBackupBuffer cei (1.3.231.46.2) pid 65929404 tid 105524 cpid 21430378 node 0 sec 3 nsec 456901658 eduid 105524 eduname db2agent 12761 entry DB2 UDB oper system services sqlochgfileptr cei (1.3.15.682.2) pid 65929404 tid 105524 cpid 21430378 node 0 sec 3 nsec 456902931 eduid 105524 eduname db2agent bytes 44 Data1 (PD_TYPE_SQO_FILE_HDL,8) File handle: File Handle = 1095 File System Block Size = 0 bytes File System Type = UNKNOWN File Handle Flags : Require Sector Align = No DIO/CIO Mode = No Raw Block Device = No Reserved Handle = No Flush On Close = No Thread-Level Lock = No Write-through Mode = No File Not Tracked = No Data2 (PD_TYPE_UINT,4) unsigned integer: 0 Data3 (PD_TYPE_FILE_OFFSET,8) File Offset: 4292852484 ........................ 12914 entry DB2 UDB Recovery History File sqluhFillBackupBuffer cei (1.3.231.46.2) pid 65929404 tid 105524 cpid 21430378 node 0 sec 3 nsec 497873410 eduid 105524 eduname db2agent | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.1 Mod 2 Fix Pack 2 or higher * **************************************************************** | |
Local Fix: | |
Purge history file to have size less than 4 Gb | |
Solution | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : IT16666 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 02.10.2017 24.10.2017 24.10.2017 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |