DB2 - Problem description
Problem IT17470 | Status: Closed |
MEMBER COULD NOT BE ACTIVATED AFTER IT WAS STOPPED IN PURESCALE. | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
A member could not be activated with the following kind of error in pureScale environment. 2016-07-15-21.51.25.454631+540 I130101438A751 LEVEL: Severe PID : 27394228 TID : 22922 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : DBNAME APPHDL : 0-53 APPID: *N0.DB2.192168000002 HOSTNAME: HOST EDUID : 22922 EDUNAME: db2redom (DBNAME) 0 FUNCTION: DB2 UDB, recovery manager, sqlpPRecReadLog, probe:1275 MESSAGE : ZRC=0x8710001D=-2028994531=SQLP_LERR "Fatal Logic Error" DIA8526C A fatal error occurred in data protection services. DATA #1 : String, 65 bytes Unexpected end of logs. Recovery expects a log record to replay. DATA #2 : String, 25 bytes expectedFirstLsnToReplay: DATA #3 : SQLP_LSN8, PD_TYPE_SQLP_LSN8, 8 bytes 000000004DE5FBBE In db2stop prior getting this error, the following kind of warning was found in db2diag.log. 2016-07-14-00.05.10.171963+540 E10747538A528 LEVEL: Warning PID : 1114404 TID : 43084 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : DBNAME HOSTNAME: HOST EDUID : 43084 EDUNAME: db2loggr (DBNAME) 0 FUNCTION: DB2 UDB, data protection services, sqlpghck, probe:1880 MESSAGE : DIA2030W In-doubt transaction(s) exists at database shutdown time on log stream "0". Crash recovery will be performed on the next database connection. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * User in pureScale environment * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to V10.5 FP9. * **************************************************************** | |
Local Fix: | |
Once deactivate the database at all members at the same time and activate the database again. It will trigger group crash recovery which will resolve this error. | |
Solution | |
This problem is first fixed in DB2 V10.5 Fix Pack 9. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 13.10.2016 27.09.2017 27.09.2017 |
Problem solved at the following versions (IBM BugInfos) | |
9.0. | |
Problem solved according to the fixlist(s) of the following version(s) |