DB2 - Problem description
Problem IT04660 | Status: Closed |
RESTORE DATABASE MIGHT INTRODUCE CORRUPTION IN OBJECTS THAT RESIDE IN SMS TABLESPACES AND ARE LARGER THAN 2GB (WINDOWS ONLY) | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
When using the Windows operating system, running the RESTORE DATABASE command on DB2 version 10.5 might introduce corruption in database objects (DATA or INDEXES) that are larger than 2GB in size and are located in SMS (system-managed space) tablespaces. The following db2diag.log errors may then be reported when accessing these tables: 2014-09-16-12.42.12.652000+120 I1741031F6776 LEVEL: Severe PID : 4088 TID : 3944 PROC : db2syscs.exe INSTANCE: DB2INST1 NODE : 000 DB : SAMPLE APPHDL : 0-40 APPID: *LOCAL.DB2INST1.140916104150 AUTHID : DB2INST1 HOSTNAME: HOST1 EDUID : 3944 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, Common Trace API, sqlbfix, probe:104 DATA #1 : String, 25 bytes bfix detected an error - DATA #2 : Boolean, 1 bytes true DATA #3 : Boolean, 1 bytes false DATA #4 : Boolean, 1 bytes false DATA #5 : String, 20 bytes Current Descriptor = DATA #6 : Buffer page descriptor, PD_TYPE_SQLB_BPD, 264 bytes Pagekey: {pool:3;obj:37;type:0} PPNum:6015 objectPageNum: 0 ... Current PageHead = DATA #8 : Page header, PD_TYPE_SQLB_PAGE_HEAD, 48 bytes pageHead: {tbspSeed:0;obj:0;type:0} bphPPNum:0 bphOPNum:0 begoff: 65535 --> this is invalid datlen: 65535 pagebinx: 492 ... When running db2dart the following error can be seen : Table inspection start: SCHEMA.TABLE Data inspection phase start. Data obj: X In pool: X Error: Unable to read pool page XXXXX, object page XXXXX, from pool X, due to rc 0x870F0009 Error: parent pool X, object ID X, object type Data. Error: This object page does not exist. Error: reading page: XXXXX from object: X Error: This phase encountered an error and did not complete. Data inspection phase end. The following select statement can help to identify if there are vulnerable objects inside the database : SELECT A.TABSCHEMA, A.TABNAME FROM SYSIBMADM.ADMINTABINFO A, SYSCAT.TABLESPACES TS, SYSCAT.TABLES T WHERE A.TABSCHEMA = T.TABSCHEMA AND A.TABNAME = T.TABNAME AND TS.TBSPACETYPE = 'S' AND T.TBSPACEID = TS.TBSPACEID AND ( DATA_OBJECT_P_SIZE >= 2147483648 OR LONG_OBJECT_P_SIZE >= 2147483648 OR INDEX_OBJECT_P_SIZE >= 2147483648 OR LOB_OBJECT_P_SIZE >= 2147483648 ); | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Windows only * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 10.5.0.5. * **************************************************************** | |
Local Fix: | |
Apply the fix and rerun RESTORE DATABASE or rebuild the affected object. | |
Solution | |
The problem is first fixed in DB2 version 10.5.0.5. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 30.09.2014 24.02.2015 09.04.2015 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.5.0.5 |