Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT06175 Status: Closed

HADR:STANDBY DATABASE MAY CRASH WITH ERROR "DIA8526C A FATAL ERROR
OCCURRED IN DATA PROTECTION SERVICES"

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
In some rare scenarios, during activate Standby db or start HADR 
on Standby, then connection is lost. after reconnection, during 
retrieving light scan, standby database may  crash with error 
"DIA8526C A fatal error occurred in data protection services" 
 
Error in db2diag.log 
====================== 
 
2014-11-24-11.38.28.181250+000 I149497A463          LEVEL: Error 
PID     : 5374716              TID : 36239          PROC : 
db2sysc 0 
INSTANCE: db2ab7               NODE : 000           DB   : AB7 
APPHDL  : 0-9                  APPID: *LOCAL.DB2.141124113600 
HOSTNAME: usadb231 
EDUID   : 36239                EDUNAME: db2shred (AB7) 0 
FUNCTION: DB2 UDB, recovery manager, sqlpshrEdu, probe:5772 
DATA #1 : <preformatted> 
Received EOL on standby. Error enountered. 
 
2014-11-24-11.38.41.364025+000 I154069A698          LEVEL: Error 
PID     : 5374716              TID : 7198           PROC : 
db2sysc 0 
INSTANCE: db2ab7               NODE : 000           DB   : AB7 
HOSTNAME: usadb231 
EDUID   : 7198                 EDUNAME: db2loggr (AB7) 0 
FUNCTION: DB2 UDB, recovery manager, sqlpgSwitchFromRedoToUndo, 
probe:510 
MESSAGE : ZRC=0x8710001D=-2028994531=SQLP_LERR "Fatal Logic 
Error" 
 
Stack: 
 
------Frame------ ------Function + Offset------ 
0x090000000078C154 pthread_kill + 0xD4 
0x09000000098644A4 sqloDumpEDU + 0x6C 
0x090000000C051F38 
sqleDoForceDBShutdownFODC__FP16sqeLocalDatabasei + 0x284 
0x0900000009813E0C ForceDBShutdown__16sqeLocalDatabaseFi + 0x6F0 
0x090000000C02C9B4 sqlpReplayMaster__FP8sqeAgent + 0x155C 
0x090000000A591B0C sqleIndCoordProcessRequest__FP8sqeAgent + 
0x670 
0x090000000A5AEABC RunEDU__8sqeAgentFv + 0x120 
0x090000000A5ADF80 EDUDriver__9sqzEDUObjFv + 0x13C 
0x090000000A5ADE08 sqlzRunEDU__FPcUi + 0x10 
0x090000000A3D1264 sqloEDUEntry + 0x26C
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* UPGRADE TO  DB2 V10.1 FP5                                    * 
****************************************************************
Local Fix:
Reactivate the db on HADR standby.
Solution
FIRST FIX IN DB2 V10.1 FP5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
18.12.2014
12.08.2015
12.08.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList