DB2 FOR LUW / DB2FORLUW / 970 - DB2

When TRACEREFRESHINTERVAL OR QUERYTIMEINTERVAL is set and a 
trusted routine is called it may cause the db2 instance to hang 
or crash. 
 
The following stack is an example or what has been observed: 
 
0x09000000062a01a0 
SqloMemoryProtectionEDU::enterSignalHandler()(??) + 0x20 
<signal> 
0x09000000062a01a0 
SqloMemoryProtectionEDU::enterSignalHandler()(??) + 0x20 
<signal> 
0x09000000045a4b40  fdprpro_symbol_fixer_5__fdpr_57(??) + 0x12c 
0x09000000045a4850  MemGetThrd__fdpr_1(??, ??, ??) + 0x20 
0x09000000041a5388  sqloMemFreePools(0x9001000a0c4f350, 0x0) + 
0xac 
0x0900000004107afc  sqloExitAppThread() + 0x34 
0x0900000004194964  CLI_cpTraceRefreshMon(??) + 0xbc 
0x09000000003594f4  _pthread_body(??) + 0xdc

Users Affected: Any using the TRACEREFRESHINTERVAL OR 
 
QUERYTIMEINTERVAL KEYWORD 
Problem Description: DB2 MAY TRAP OR HANG WHEN THE 
TRACEREFRESHINTERVAL OR QUERYTIMEINTERVAL KEYWORD IS USED WITH A 
TRUSTED ROUTINE 
Problem Summary: see above

Unset the keyword to avoid this issue.

DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

Problem was first fixed in Version 9.7 FixPak 3

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

10.09.2009
07.10.2010
07.10.2010

9.7.