DB2 - Problem description
Problem IC94685 | Status: Closed |
"a numeric conversion has unexpectedly failed" error dumped in the db2diag.log file | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
While compiling a query with one or more join operations, DB2 might dump the following error message in db2diag.log file: FUNCTION: DB2 UDB, data services, sqlrxcon, probe:219 DATA #1 : String, 117 bytes ASSERTION FAILED!!! ASSERTION EXPRESSION: convertNumRc == 0 SOURCE FILE NAME: sqlrxcon.C SOURCE FILE LINE NUMBER: 208 DATA #2 : Codepath, 8 bytes 0 DATA #3 : String, 72 bytes CONTACT DB2 SERVICE, assert a numeric conversion has unexpectedly failed DATA #4 : String, 13 bytes convertNumRc: DATA #5 : Hex integer, 4 bytes 0x80160008 DATA #6 : String, 23 bytes datain zvalue and data: DATA #7 : Hexdump with no ASCII beside it, 24 bytes 0x070000000EBF1BF8 : 0002 1400 0002 0000 0700 0000 303D 7F20 0x070000000EBF1C08 : 0900 1000 A0AB 2628 DATA #8 : Hexdump with no ASCII beside it, 11 bytes 0x07000000303D7F20 : 0000 0000 0000 0000 0000 0C DATA #9 : String, 24 bytes dataout zvalue and data: DATA #10: Hexdump with no ASCII beside it, 24 bytes 0x070000000EBF1298 : 0002 0108 0000 0002 0700 0000 0EBF 1900 0x070000000EBF12A8 : 0700 0000 303A 89D0 DATA #11: Hexdump with no ASCII beside it, 1 bytes 0x070000000EBF1900 : 00 CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol) [0] 0x0900000031986984 pdLog + 0xF4 [1] 0x09000000327BF038 sqlrxcon2__FP8SQLRXNLSP10sqlz_valueT2 + 0x194 [2] 0x0900000031B6E658 sqlrxcp2__FCPC14sqlrxCollationP10sqlz_valueT2Ui + 0x1698 [3] 0x0900000035172078 sqlno_ff_nud_col_eq_col__FP13sqlno_globalsP19sqlno_ff_essentials P9sqlnq_cstfT4T3N24PfT9 + 0x15C8 [4] 0x09000000351703EC @155@sqlno_ff_col_eq_col__FP13sqlno_globalsP19sqlno_ff_essential sPfT3P16sqlno_listheader13SQLNN_BOOLEAN + 0x19E8 [5] 0x0900000033AF0FA4 @155@sqlno_ff_compute_atomprd__FP13sqlno_globalsP19sqlno_ff_esse ntialsP16sqlno_listheader13SQLNN_BOOLEAN + 0x106C [6] 0x090000003437A7E0 sqlno_ff_compute__FP13sqlno_globalsP19sqlno_ff_essentialsP16sqln o_listheader13SQLNN_BOOLEAN + 0x28C [7] 0x0900000034398AB4 sqlno_prop_recompute_pred_ff__FP13sqlno_globalsP9sqlno_qtbP11sql no_tableP10sqlno_isetPf + 0x760 [8] 0x09000000343A6C58 sqlno_prop_recompute_pred_ff__FP13sqlno_globalsP9sqlno_qtbP11sql no_tableP10sqlno_isetPf@glueB33 + 0x74 [9] 0x09000000328EDC48 @155@sqlno_prop_compute_nud_adjustments__FP13sqlno_globalsP9sqln o_qtb + 0x338 Note : The memory addresses and/or some hexdump may be different from that shown above. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All V9.7 users. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 Fix Pack 9. * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows | |
Solution | |
Fixed in DB2 Version 9.7 Fix Pack 9. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 06.08.2013 17.12.2013 17.12.2013 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP9 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.9 | |
9.7.0.9 |