2126195 - Exception Thrown from slib/s_packedRec.cxx - SAP IQ

• Some UPDATE or SELECT DISTINCT queries running in IQ 16.0 randomly fail with Non-Fatal errors detected at s_packedRec(), for example:

Exception Thrown from slib/s_packedRec.cxx:1313, Err# 3, tid 39 origtid 39
O/S Err#: 0, ErrID: 2063 (s_packedRecException); SQLCode: -1006000, SQLState: 'QBA00', Severity: 23
IQ Internal error. Please report this to SAP IQ support.

•  Failing query may produce a stack trace at call s_packedRec::ConditionKeysFromHDVal after an NBitFetch or ByteFetch, for example:

s_packedRec::ConditionKeysFromHDVal()
s_packedRec::AcceptRec()
s_phash::FindKeyIfExists()
s_dpNBitFetch::InProbe()
hs_dp::ConstructLookupFind()
vpp::ConstructLookupFind()

or

s_packedRec::ConditionKeysFromHDVal()
s_packedRec::AcceptRec()
s_phash::FindKeyIfExists()
s_dpByteFetch::InProbe()
hs_dp::ConstructLookupFind()
vpp::ExecuteParallelFind()

• If a query plan is produced then you may see a VARCHAR or VARBINARY column output in the leaf nodes declared with an incorrect data type length when used in a Hash Push Down Join (HPDJ), for example:

Output 1:  dc.DIM_E_RAN_RBS.RNC_ID:
Output 1     Data Type:  varchar (5)  --> the effective length we used
Output 1     Column's Declared Data Type:  varchar (35) –-> the max possible length
Output 1     Base Distincts:  24
Output 1     Indexes:  FP(5-bit), HG

SAP IQ 16.0

KBA , BC-SYB-IQ , Sybase IQ , Bug Filed