Symptom
- Whilst inserting data into a table column the index cardinality exceeds an upper threshold and a dynamic conversion to a Flat style FP index occurs. These messages seen in the iqmsg file...
Informational: Index Cardinality Exceeded Converting index to flat:
rids have no associated ridmap or mergemap
- The FP rollover to flat fails with a ridmap missing region message and ridmap dump
barray t600 pmSumPacketLatency: CheckColumnEBMCoverage
barray t600 *** ridmap missing region for [nnnnnnn,nnnnnnn] previous region: [nnnnnnn,nnnnnnn] current region: [nnnnnnn,nnnnnnn]
...
barray t600 C41 BEGIN dump RidMap:
- A Non-Fatal internal error detected error is thrown at slib/s_dpidx.cxx with this stack trace
hs_dp::CheckIndexConsistency
df_FPRolloverIterator::ExecWork
workAllocator::DoWork
hos_team::StartWork
hos_team::Exec
dfiio_FP::RolloverIfNeeded()
dfiio_FP::PostFetchOpus()
dfo_IndexInsert::PostFetchOpus()
- A sp_iqcheckdb consistency check run against the table shows no errors.
Read more...
Environment
- SAP IQ 16.1
Product
SAP IQ 16.1
Keywords
sybase, abort, fail, stacktrace, stktrc, 's_dpidx.cxx:7540', 'roll over', flatfp, nonfatal, 'non fatal', CR816096, CR#816096, 816096, dbcc, , 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.