|
Problem IC84207
|
Status: Closed |
UPGRADE OR RESTORE CAN HANG IF TABLE HAS COMPRESSION DICTIONARY |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
An UPGRADE operation involving a compressed table may hang.
Additionally if you attempt to RESTORE the downlevel database
backup image then this can hang as well since RESTORE will
invoke an UPGRADE under the covers.
If stacks are collected during the hang, one stack will show
function sqldMigrateDAT() hanging in sqlbfix(), like so:
0x00002AAAB07FBE9F ossDumpStackTraceEx + 0x01ef
0x00002AAAB07F6C5E _ZN11OSSTrapFile6dumpExEmiP7siginfoPvm +
0x00cc
0x00002AAAAD89C38A sqlo_trce + 0x040a
0x00002AAAAD8E16D5 sqloDumpDiagInfoHandler + 0x00ed
0x00002AAAAACD64C0 address: 0x00002AAAAACD64C0 ; dladdress:
0x00002AAAAACC8000 ;
0x00002AAAB14EF477 semop + 0x0007
0x00002AAAAC31ACD0
_ZN17SQLO_SLATCH_CAS6418getConflictComplexEm + 0x04aa
0x00002AAAAC31A7E6 _ZN17SQLO_SLATCH_CAS6411getConflictEm +
0x0068
0x00002AAAAE5961C3 _Z7sqlbfixP11SQLB_FIX_CB + 0x1bd1
0x00002AAAABDF1E9C _Z11sqlbFixPageP11SQLB_FIX_CBiji + 0x001a
0x00002AAAACBAFFC7
_Z14sqldMigrateDATP8sqeAgentP12SQLB_POOL_CBP16SQLB_OBJECT_DESC +
0x07bd
0x00002AAAACBB1316 address: 0x00002AAAACBB1316 ; dladdress:
0x00002AAAAAEE4000 ;
0x00002AAAACBB1979 _Z22sqldMigrateTablespacesP8sqeAgent +
0x016b
0x00002AAAAC50089C _Z8sqlrliniP8sqlrr_cbb + 0x0f06
0x00002AAAAC3DC899 _Z15sqlrr_appl_initP8sqeAgentP5sqlca +
0x3107
0x00002AAAABF4984E
_ZN14sqeApplication20InitEngineComponentsEcP8sqeAgentP8SQLE_BWAP
5sqlca
0x00002AAAABF4834A
_ZN14sqeApplication13AppStartUsingEP8SQLE_BWAP8sqeAgentccP5sqlca
Pc + 0x04fe
0x00002AAAACCA19C6 _Z8sqlemigrP8SQLE_BWAP14db2UCinterface +
0x0776
0x00002AAAABF4477E address: 0x00002AAAABF4477E ; dladdress:
0x00002AAAAAEE4000 ; |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users of table compression *
****************************************************************
* PROBLEM DESCRIPTION: *
* Upgrade may hang if a table uses compression. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to the latest fix pack. *
**************************************************************** |
| 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 |
Problem was first fixed in DB2 UDB version 10.1 fix pack 1 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 13.06.2012
01.11.2012
01.11.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
