DB2 - Problem description
Problem IT34970 | Status: Closed |
ABNORMAL TERMINATION OF DATABASE WITH "ERROR DURING LOG PAGE VALIDATION." FROM SQLPGWLP, PROBE:390. | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
This is a problem for pureScale database. The first error is indicated by the following message in db2diag.log: 2020-09-13-20.18.34.074473+540 I449073A409 LEVEL: Severe PID : 3932826 TID : 164886 PROC : db2sysc 2 INSTANCE: myinst1 NODE : 002 DB : MYDB HOSTNAME: myhost2 EDUID : 164886 EDUNAME: db2loggw (MYDB) 2 FUNCTION: DB2 UDB, data protection services, sqlpgwlp, probe:390 DATA #1 : Error during log page validation. After this message, many other error messages and dump files are produced, eventually resulting in FODC_ForceDBShutdown and abnormal termination of the database on the affected member in the pureScale cluster. This problem only affects a single member in the cluster. Other members are not affected. Subsequent member crash recovery is successful. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * pureScale * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.1 * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * pureScale * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.1 * **************************************************************** | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 17.11.2020 13.07.2021 13.07.2021 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |