DB2 - Problembeschreibung
Problem IC97177 | Status: Geschlossen |
HADR STANDBY DB COULD RUN INTO A TRAP WHEN IT'S REMOTE DB IS ALSO A STANDBY DB | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * HADR users of all configurations * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to product version 10.5 fixpack 3 * **************************************************************** | |
Local-Fix: | |
Restart the standby database and configure the databases that one of the database is a primary database. | |
verfügbare FixPacks: | |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows | |
Lösung | |
First fixed in DB2 version 10.5 fixpack 3 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 24.10.2013 08.09.2014 08.09.2014 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.5.0.4 |