SAP Knowledge Base Article - Preview

3375888 - DB6: HADR encountered an abnormal condition. Reason code: "10" with Pacemaker cluster manager

Symptom

Perform a HADR test failover to Standby in HADR
During the takeover an issue occurs (crash of standby, slow takeover where manual db2_kill is issued). 
Restart is performed following shutdown.
Initiate again the takeover and the following error is reported in the db2diag.log  

2023-08-05-17.28.47.411882+120 E91380E468            LEVEL: Error
PID     : 13252                TID : 140726113396480 PROC : db2sysc 0
INSTANCE: db2test               NODE : 000            DB   : TEST    
HOSTNAME: test
EDUID   : 169                  EDUNAME: db2hadrs.0.0 (TEST) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrEdu::hdrEduS, probe:21310
DATA #1 : String, 63 bytes
A previous takeover by force on this database did not complete.

 

2023-08-05-17.28.47.412034+120 E91849E456            LEVEL: Error
PID     : 13252                TID : 140726113396480 PROC : db2sysc 0
INSTANCE: db2test              NODE : 000            DB   : TEST     
HOSTNAME: TEST
EDUID   : 169                  EDUNAME: db2hadrs.0.0 (TEA) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrEdu::hdrEduS, probe:21315
MESSAGE : ADM12509E  HADR encountered an abnormal condition. Reason code: "10"


Read more...

Environment

DB2 LUW IBM
Pacemaker cluster resource manager.

Keywords

HADR_STATE, TAKEOVER BY FORCE , KBA , BC-DB-DB6 , DB2 Universal Database for Unix / NT , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.