DB2 - Problem description
Problem IT30189 | Status: Closed |
UPGRADE DB MAY CORRUPT SQLSPCS FILES AND RESULT IN CHECKSUM ERROR WHEN DB IS ACTIVATED | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
db2 upgrade db completed successfully but activation of the database afterward failed with the following message: SQL0980C A disk error occurred. Subsequent SQL statements cannot be processed. SQLSTATE=58005 During the upgrade, a container name in SPCS files is compressed from an absolute path to a relative path but the 'Container memory used' is not updated accordingly, the wrong size is then written to disk into SQLSPCS.1 and SQLSPCS.2 files, it results in bad container checksum calculated when the db is activated afterward. Note that the absolute path has to be in /db path/your_instance/NODExxxx/SQLxxxxx to trigger this problem. Errors will be similar to this in db2diag.log: FUNCTION: DB2 UDB, buffer pool services, sqlbReadPoolOneFile, probe:1681 MESSAGE : ZRC=0x86020019=-2046689255=SQLB_CSUM "Bad Page, Checksum Error" DIA8426C A invalid page checksum was found for page "". DATA #1 : Pool control block, PD_TYPE_SQLB_POOL_CB, 54160 bytes name: USERSPACE1 poolID: 2 flags: 101 flags2: 20 local flags: 0 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher * **************************************************************** | |
Local Fix: | |
Asking Db2 support to format SPCS files, verify it is the APAR and patch the container name using the absolute path. | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 04.09.2019 16.01.2020 16.01.2020 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |