On a Db2 LUW database , a query may return the following error
when column organized tables are involved.:
SQL0901N The SQL statement or command failed because of a
database system
error. (Reason "unexpected error at
GetJoinPayloadEvaluator.cpp:152".)
SQLSTATE=58004
db2diag.log:
2020-11-27-17.07.06.810495+000 I5539149E3429 LEVEL:
Error
PID : 686517 TID : 48064345663232 PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB :
DBNAME
APPHDL : 0-1604 APPID:
*LOCAL.db2inst1.201127170653
UOWID : 2 ACTID: 2
AUTHID : DB2INST1 HOSTNAME: XXXXXXX
EDUID : 371 EDUNAME: db2agntcol (BLUDB) 0
FUNCTION: DB2 UDB, CDE Trace, cdeDiagnosticsFacility, probe:157
DATA #1 : String, 277 bytes
AssertionFailedException: An assertion 'mSizeOfUnencFKeyInBytes
== mJoinHashTableInfo->getSizeOfUnencKeyInBytes() || 0 ==
mJoinHashTableInfo->getSizeOfUnencKeyInBytes()' failed.
Additional info: unencoded key size mismatch 104 96 792
Thrown at GetJoinPayloadEvaluator.cpp : 157
DATA #2 : Function name in Library, 255 bytes
ibm_cde::query::GetJoinPayloadEvaluator::GetJoinPayloadEvaluator
(ibm_cde::query::Queue*, ibm_cde::query::Evaluator::InputInfo,
ibm_cde::query::Evaluator::InputInfo, Uint32, const
ibm_cde::query::SyntaxTree*, ibm_cde::services::MemPoolHandle,
ibm_cde::quer
DATA #3 : File name, 27 bytes
GetJoinPayloadEvaluator.cpp
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved to the nearest symbol)
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved to the nearest symbol)
[0] 0x00002B62FB040117
_ZN7ibm_cde8services6Tracer9traceDataENS0_11ComponentIDENS0_16Co
mmonTraceLevelENS1_10TraceEventEPKcmS6_PKvmRKSbIcSt11char_trait
+ 0x947
[1] 0x00002B62FAFE1D81
_ZNK7ibm_cde8services13BaseException14traceExceptionENS0_11Compo
nentIDEPKc + 0x251
[2] 0x00002B62FAFD9F27
_ZN7ibm_cde8services24AssertionFailedException17constructAndThro
wENS0_11ComponentIDEPKcmS4_S4_RNS0_16CdeOStringStreamE + 0xB7
[3] 0x00002B62FE926EE7
_ZN7ibm_cde5query23GetJoinPayloadEvaluatorC1EPNS0_5QueueENS0_9Ev
aluator9InputInfoES5_jPKNS0_10SyntaxTreeEP13SQLO_MEM_POOLPNS0_1
+ 0x8A7
[4] 0x00002B62FC5773DB
_ZN7ibm_cde5query17EvaluationRoutine29formEvaluationRoutineInter
nalEPKNS0_10SyntaxTreeERKNS0_14QueryResourcesERNS_4data22TableA
+ 0x10A3B
[5] 0x00002B62FC57EFE6
_ZN7ibm_cde5query17EvaluationRoutine21formEvaluationRoutineEsRNS
_4data22TableAccessorAllocatorERKNS0_19QueryResultInfoListERNS0
+ 0x486
[6] 0x00002B62FCE38635
_ZN7ibm_cde5query9Scheduler19genSingleTableQueryEPNS0_10SyntaxTr
eeEPNS0_18NLJoinControlBlockE + 0x2C5
[7] 0x00002B62FCE3D739
_ZN7ibm_cde5query9Scheduler19runSingleTableQueryEv + 0x769
[8] 0x00002B62FCE4056B
_ZN7ibm_cde5query9Scheduler17runCompositeQueryEv + 0x33B
[9] 0x00002B62FCE41690
_ZN7ibm_cde5query9Scheduler15runMasterThreadEPvPi + 0x110
[10] 0x00002B62FCE25D9A
_ZN7ibm_cde5query17cdeEntryPointImplEP8sqeAgentPvS3_ + 0x6A
[11] 0x00002B62FD728B65
_ZN12cdeInterface16startCdeSubagentEP8sqeAgent + 0x115
[12] 0x00002B6302932FCD _Z14sqlriInvokeCdeP8sqlrr_cb + 0x3D
[13] 0x00002B630279769F
_Z15sqlriSectInvokeP8sqlrr_cbP12sqlri_opparm + 0x4EF
[14] 0x00002B63022154AD _Z16sqlrr_smp_routerP8sqlrr_cb + 0x48D
To further confirm the underlying cause is this APAR, the Query
Execution Plan needs to be examined.
The Query Explain Plan can be generating using the DB2 Explain
facility (db2exfmt), or DB2 Optim Query Tuner / Graphical
Explain. Ideally, The
Query Explain Plan should be examined to determine if a
duplicate join predicate is present on the same Hash Join, in
the formatted explain output.
For example:
35) Predicate used in Join,
Comparison Operator: Equal (=)
Subquery Input Required: No
Filter Factor: 0.0909091
Predicate Text:
--------------
(Q3.KEY_ID = Q8.FIRST_KEY) |
