home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC76905 Status: Closed

SQL0430N USER DEFINED FUNCTION "SYSPROC.PD_GET_DIAG_HIST"
(SPECIFIC NAME "PD_GET_DIAG_HIST") HAS ABNORMALLY TERMINATED.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
PD_GET_DIAG_HIST() may terminate with a signal 11 (SEGV 
segmentation violation) in function PDDIAGLOGGETEVENTFIELD(). 
When this happen, error << SQL0430N User defined function 
"SYSPROC.PD_GET_DIAG_HIST" (specific name "PD_GET_DIAG_HIST") 
has abnormally terminated >> will be raised . Trap files in the 
corresponding FODC subdirectory to DB2DUMP shows SEGV in 
pdDiagLogGetEventField : 
 
 
<StackTrace> 
 
------Function + Offset------ 
pdDiagLogGetEventField + 0x93C 
pdDiagGetLogRecordField + 0x8C0 
pdDiagGetNextLogRecordField + 0x2B4 
pdDiagGetNextLogRecord + 0x7B4 
pdDiagGetNextRecordFromBuffer + 0x1DC 
pdDiagGetNextRecord + 0x2E4 
getNextRows__17PADiagLogCollApplFUiPP13PA_DATA_VALUEPUiT3 + 
0x260 
pd_get_diag_hist + 0x77C 
sqloInvokeFnArgs + 0xCA0 
@76@sqlerRunRoutine__FP13sqleInvokerCBPi + 0x160 
sqlerDyload + 0x140 
sqlerFmpListener + 0xB0 
sqlerWorkerThreadEntry__FPv + 0x25C 
_pthread_body + 0xF0 
</StackTrace>
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All using sysproc.pd_get_diag_hist()                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See error description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 9.7 Fix Pack 5                        * 
****************************************************************
Local Fix:
This can sometime happen when users try to recycle the current 
db2diag.log manually by using "cat /dev/null > db2diag.log" or 
using "db2diag -A". Just re-issue the SYSPROC.PD_GET_DIAG_HIST() 
a second time.
available fix packs:
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

Solution
First fixed in DB2 version 9.7 Fix Pack 5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
10.06.2011
23.12.2011
23.12.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList