Normally, if users run "stop hadr on db <dbname>" on HADR
primary, primary will turn to a normal database and the service
should continue.
However, if many applications are connecting to the database
while the command is ran, HADR primary could be shutdown
because of a very small timing issue.
When the problem is hit, the following messages will appear in
the db2diag.log:
2012-04-04-09.09.55.577084-240 I1643682E464 LEVEL:
Warning
PID : 15011 TID : 46912711420224PROC :
db2sysc
INSTANCE: db2inst1 NODE : 000 DB : GDB
APPHDL : 0-894 APPID:
*LOCAL.db2inst1.120404131155
AUTHID : db2inst1
EDUID : 69 EDUNAME: db2agent (SAMPLE)
FUNCTION: DB2 UDB, High Availability Disaster Recovery,
hdrEduShutdown, probe:29002
MESSAGE : Info: HADR Shutdown has completed.
2012-04-04-09.09.55.706427-240 I1644147E558 LEVEL: Severe
PID : 15011 TID : 46912824666432PROC :
db2sysc
INSTANCE: db2inst1 NODE : 000 DB : GDB
APPHDL : 0-890 APPID:
*LOCAL.db2inst1.120404131153
AUTHID : db2inst1
EDUID : 42 EDUNAME: db2agent (SAMPLE)
FUNCTION: DB2 UDB, RAS/PD component,
pdResilienceIsSafeToSustain, probe:800
DATA #1 : String, 37 bytes
Trap Sustainability Criteria Checking
DATA #2 : Hex integer, 8 bytes
0x0000000400003040
DATA #3 : Boolean, 1 bytes
false
2012-04-04-09.09.55.706684-240 I1644706E556 LEVEL: Error
PID : 15011 TID : 46912824666432PROC :
db2sysc
INSTANCE: db2inst1 NODE : 000 DB : GDB
APPHDL : 0-890 APPID:
*LOCAL.db2inst1.120404131153
AUTHID : db2inst1
EDUID : 42 EDUNAME: db2agent (sample)
FUNCTION: DB2 UDB, base sys utilities, sqleagnt_sigsegvh,
probe:1
MESSAGE : Error in agent servicing application with coor_node:
DATA #1 : Hexdump, 2 bytes
0x00002AAABE00F592 : 0000
And stack of EDU 42 looks like:
TermDbConnect
AppStopUsing
sqlesrspWrp
sqleUCagentConnectReset
sqljsDrdaAsDriver |
