|
Problem IC97176
|
Status: Closed |
HADR STANDBY DB COULD RUN INTO A TRAP WHEN IT'S REMOTE DB IS ALSO A STANDBY DB |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
When a standby database is configured with a remote database
that is also a standby database then the standby database could
run a trap and crash with a segmentation fault. The following
stack will found in the trap file
StackTrace
<StackTrace>
0x090000000AD6BD6C sqloFDBitIsSet__FiP17sqlo_select_fdset + 0xAC
0x090000000AD70660
hdrEduAcceptEvent__6hdrEduFP8HDR_DBCBP14HDR_EVENT_TYPEPP11HDR_HD
R
_MSGPP8HDR_RQST + 0x2780
0x090000000AD79B50 hdrEduS__6hdrEduFPUl + 0xC90
0x090000000ADA2C68 hdrEduEntry__6hdrEduFv + 0x14A8
0x090000000ADA3D0C RunEDU__6hdrEduFv + 0x10C
0x0900000009953C24 EDUDriver__9sqzEDUObjFv + 0x244
0x0900000009953F7C sqlzRunEDU__FPcUi + 0x3C
0x090000000969FEFC sqloEDUEntry + 0x7BC
</StackTrace>
The following message will be found in the db2diag.log
> 2013-09-25-17.04.12.933092-240 I452726A495 LEVEL:
Info
> PID : 7405584 TID : 5657 KTID :
22020337
> PROC : db2sysc 0
> INSTANCE: svtdbm NODE : 000 DB :
HADRDB
> HOSTNAME: tempsvt01
> EDUID : 5657 EDUNAME: db2hadrs.0.0 (HADRDB)
0
> FUNCTION: DB2 UDB, High Availability Disaster Recovery,
> hdrSendHsMsgNoDefer, probe:30539
> DATA #1 : <preformatted>
> A HDR_MSG_NOTPRIMARY message was sent to tempsvt02:49856
(9.23.2.198:49856) |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* HADR users in any configuration *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to product DB2 version 10.1 fixpack 4 *
**************************************************************** |
| Local Fix: |
Restart the standby database and configure the databases that
one of the database is a primary database. |
| available fix packs: |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 version 10.1 fixpack 4 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 24.10.2013
02.06.2014
02.06.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.4
|
 |
