Symptom
- Running in a multiplex, update queries like LOAD table start to fail with numeric MaxToken mismatch errors
t490 *** <table name> rxpkts (numeric MaxToken mismatch between token count table (101) and llh table (100).
- s_Dictionary Dump Token numeric Key trace information is written to the iqmsg file
s_Dictionary Dump Token numeric Keys, keySize=18, maxToken=101
t490: token=0 Key=15
t490: token=1 Key=0
t490: token=2 Key=39
- Non-Fatal IQ Internal Error Detected errors at s_dpidx.cxx with stack at hs_dp::CheckIndexConsistency
** Non-Fatal IQ Internal Error Detected
** at slib/s_dpidx.cxx:7493 on thread 490 (TID 483)
hs_dp::CheckIndexConsistency(int)
hs_dpInsert::Complete()
dfiio_FP::PostFetchOpus()
dfo_IndexInsert::PostFetchOpus()
df_CombinerFinalFetchHelper::ExecWork
- Server will be running with option FP_NBIT_ENABLE_TOKENCOUNT_CHECK=’ON’ set
Read more...
Environment
- SAP IQ 16.x
Product
Keywords
sybase, 'load into', fail, abort, nonfatal, 'non fatal', insert, CR814019, CR#814019, 814019, iq161, corruption, log, mpx, writer, node, Query_Name, Dynamic, CR815978, CR#815978, 815978 , KBA , BC-SYB-IQ , Sybase IQ , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview