Fixes are available
DB2 Version 9.1 Fix Pack 4a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 4 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 7 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 5 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 6 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 6a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 7a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 8 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 9 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12 for Linux, UNIX and Windows
APAR status
Closed as program error.
Error description
If a WRITE SUSPEND command is still being processed and a WRITE RESUME command is issued from another session, it could lead to a crash. The WRITE RESUME agent's stack trace may be similar to: ossDumpStackTraceInternal + 0xe0 ossDumpStackTrace + 0x50 _ZN11OSSTrapFile4dumpEmiP9__siginfoPv + 0x140 sqlo_trce + 0x890 sqloDumpDiagInfoHandler + 0x100 ---- Signal 29 (SIGURG) delivered ---- _kill + 0x30 sqloDumpEDU + 0x40 _Z10sqle_panicv + 0x70 _ZNK17SQLO_SLATCH_CAS6420dumpDiagInfoAndPanicEPKcjmmlmiS1_mi + 0x260 _ZN17SQLO_SLATCH_CAS6422releaseConflictComplexEv + 0xa30 _ZN17SQLO_SLATCH_CAS6415releaseConflictEv + 0x90 _Z27sqlbUnsuspendDBControlFilesP12SQLB_GLOBALS + 0x5f0 _Z18sqlbUnsuspendWritetP12SQLB_GLOBALS + 0xd80 sqlbSetWriteResume + 0x4c0 [...]
Local fix
Avoid issuing a WRITE RESUME command whilst a WRITE SUSPEND command is running.
Problem summary
Users affected: Users using a split-mirror backup strategey. Problem Description: Issuing a write suspend whilst another write suspend is being processed may result in a crash. Problem Summary: Issuing a write suspend whilst another write suspend is being processed may result in a crash.
Problem conclusion
First fixed in DB2 UDB Version 9.1, FixPak 4
Temporary fix
Comments
APAR Information
APAR number
IY98630
Reported component name
DB2 UDB ESE HP-
Reported component ID
5765F4103
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2007-05-17
Closed date
2008-02-12
Last modified date
2008-02-12
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
DB2 UDB ESE HP-
Fixed component ID
5765F4103
Applicable component levels
R910 PSY
UP
Document Information
Modified date:
07 January 2022