When ROS is enabled, during TAKEOVER command DB2 may panic and
fail when calling the
function sqlbSwapDirtyLists with the following messages
appearing in the db2diag.log:
2012-12-15-13.19.37.192346+000 I630342E414 LEVEL:
Warning
PID : 8366 TID : 46913919379776PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
EDUID : 95 EDUNAME: db2hadrs (SAMPLE) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery,
hdrSDoTakeover,
probe:47002
MESSAGE : Initiating HADR takeover request, forcing
applications.
2012-12-15-13.19.37.192480+000 I630757E398 LEVEL:
Warning
PID : 8366 TID : 46913919379776PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
EDUID : 95 EDUNAME: db2hadrs (SAMPLE) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery,
hdrSDoTakeover,
probe:47001
MESSAGE : Info: Standby has initiated a takeover.
<< >>
2012-12-15-13.19.37.274041+000 I631156E400 LEVEL:
Warning
PID : 8366 TID : 46913919379776PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
EDUID : 95 EDUNAME: db2hadrs (SAMPLE) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery,
hdrSDoTakeover,
probe:47042
MESSAGE : Info: Standby switching roles to primary.
<< >>
2012-12-15-13.19.37.396365+000 I632581E1949 LEVEL: Severe
PID : 8366 TID : 46913915185472PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-24 APPID: *LOCAL.DB2.121214182048
EDUID : 96 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, Common Trace API, sqlbfix, probe:3632
DATA #1 : String, 53 bytes
sqlbSwapDirtyLists has a non-empty target dirty list
DATA #2 : Hexdump, 288 bytes
................
2012-12-15-13.19.37.396537+000 E634531E924 LEVEL:
Critical
PID : 8366 TID : 46913915185472PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-24 APPID: *LOCAL.DB2.121214182048
EDUID : 96 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, RAS/PD component, pdStartFODC, probe:10
MESSAGE : ADM14001C An unexpected and critical error has
occurred:
"Panic".
The instance may have been shutdown as a result.
"Automatic"
FODC
(First Occurrence Data Capture) has been invoked and
diagnostic
information has been recorded in directory
"/home/db2inst1/sqllib/db2dump/FODC_Panic_2012-12-15-13.19.37.39
6499_
0000/". Please look in this directory for detailed
evidence
about
what happened and contact IBM support if necessary to
diagnose
the
problem.
2012-12-15-13.19.37.396754+000 I635456E522 LEVEL: Severe
PID : 8366 TID : 46913915185472PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-24 APPID: *LOCAL.DB2.121214182048
EDUID : 96 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, buffer pool services, sqlb_panic, probe:20
RETCODE : ZRC=0x87020002=-2029912062=SQLB_BPSE "Debug logic
error
detected"
DIA8501C A buffer pool logic error has occurred.
2012-12-15-13.19.37.396848+000 I635979E434 LEVEL: Severe
PID : 8366 TID : 46913915185472PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-24 APPID: *LOCAL.DB2.121214182048
EDUID : 96 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, buffer pool services, sqlb_panic, probe:20
MESSAGE : Severe error in buffer pool services |
