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 IC99584 Status: Closed

INSTANCE MAY CRASH IF THERE INCONSISTENT STATISTICS

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
Instance may crash if there inconsistent statistics 
 
Description: 
Instance may crash if there inconsistent statistics by receiving 
a sigsegv at sqlv_longcompdfp128. 
You may find similar stacktrace back at a trap file. 
 
<StackTrace> 
-----FUNC-ADDR---- ------FUNCTION + OFFSET------ 
0x0000020006DD955A 
_Z25ossDumpStackTraceInternalmR11OSSTrapFileiP7siginfoPvm + 
0x0102 
                (/home/cdbinst1/sqllib/lib64/libdb2osse.so.1) 
0x0000020006DD9766 ossDumpStackTraceV98 + 0x007a 
                (/home/cdbinst1/sqllib/lib64/libdb2osse.so.1) 
0x0000020006DD4752 _ZN11OSSTrapFile4dumpEmiP7siginfoPv + 0x00ee 
                (/home/cdbinst1/sqllib/lib64/libdb2osse.so.1) 
0x00000200035D8D82 sqlo_trce + 0x0926 
                (/home/cdbinst1/sqllib/lib64/libdb2e.so.1) 
0x00000200036BF018 sqloEDUCodeTrapHandler + 0x0250 
                (/home/cdbinst1/sqllib/lib64/libdb2e.so.1) 
0x00000201E0C09DF0 address: 0x201e0c09df0 
0x0000020003F19BE2 
_Z19sqlv_longcompdfp128PK14sqlrxCollationP10sqlz_valueS3_j + 
0x0026 
                (/home/cdbinst1/sqllib/lib64/libdb2e.so.1) 
0x0000020004B1E77A 
_Z8sqlrxcp2PK14sqlrxCollationP10sqlz_valueS3_j + 0x0fba 
                (/home/cdbinst1/sqllib/lib64/libdb2e.so.1) 
0x000002000264280A 
_Z18sqlno_ff_frq_rangeP13sqlno_globalsP19sqlno_ff_essentialsPdjS 
3_jP10sqlz_valueS5_P9sqlnq_cst14sqlnq_funclassS8_f17sqlno_prefix 
_typePK14sqlrxCollationPfSD_P25sqlno_xml_stats_interface + 
0x046e 
                (/home/cdbinst1/sqllib/lib64/libdb2e.so.1) 
0x0000020002646078 
_Z18sqlno_ff_nud_rangeP13sqlno_globalsP19sqlno_ff_essentialsP9sq 
lnq_cstPdjff14sqlnq_funclassP10sqlz_value17sqlno_prefix_type13SQ 
LNN_BOOLEANPfPb + 0x0bb0 
                (/home/cdbinst1/sqllib/lib64/libdb2e.so.1) 
0x000002000264C784 address: 0x000002000264C784 ; dladdress: 
0x0000020000078000 ; offset in lib: 0x00000000025D4784 ; 
                (/home/cdbinst1/sqllib/lib64/libdb2e.so.1) 
0x000002000264E674 address: 0x000002000264E674 ; dladdress: 
0x0000020000078000 ; offset in lib: 0x00000000025D6674 ; 
                (/home/cdbinst1/sqllib/lib64/libdb2e.so.1) 
0x0000020002657242 address: 0x0000020002657242 ; dladdress: 
0x0000020000078000 ; offset in lib: 0x00000000025DF242 ; 
                (/home/cdbinst1/sqllib/lib64/libdb2e.so.1) 
0x000002000265A4CC 
_Z16sqlno_ff_computeP13sqlno_globalsP19sqlno_ff_essentialsP16sql 
no_listheader13SQLNN_BOOLEAN + 0x09b8 
                (/home/cdbinst1/sqllib/lib64/libdb2e.so.1) 
0x00000200028B41A4 _Z18sqlno_ntup_ff_scanP13sqlno_globals + 
0x1778 
   : 
---
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 UDB Version 10.5                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 10.5 FixPack 4.                           * 
****************************************************************
Local Fix:
available fix packs:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
Problem was first fixed in DB2 UDB Version 10.5 FixPack 4.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
24.02.2014
08.09.2014
08.09.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.4 FixList