SAP Knowledge Base Article - Preview

3093900 - s_dpidx or s_dpNBit  non-fatal “Invalid key length or offset found in the dictionary of index” – SAP IQ  

Symptom

On rare occasions after executing a DML operation such as a LOAD, INSERT or UPDATE for tables that contain varchar or varbinary columns the SQL transaction may fail with messages like

 

  • Invalid key length or offset found in the dictionary of index <table index name> (datatype as varchar): maxLength = 50 around token(1)

  • s_Dictionary Dump Token varchar Keys

  • slib/s_llhtable.cxx:3456 datatype varchar not supported yet.

  • Non-Fatal IQ Internal Error Detected at slib/s_dpidx.cxx:7763

  • Stacktrace calls …

                   hs_dp::CheckIndexConsistency

                   hs_dpInsert::Complete()

                   df_CompleteIter::ExecWork

                   workAllocator::DoWork

                   hos_thread::Main()

                   hos_lwtask::Start

                   IQWorkerStarter

 

 

You may also encounter these types of errors  “slib/s_dpNBit.cxx:3186 invalid key offset”

 

This will only apply to index objects that were originally created in a IQ 15.x system and upgraded to IQ 16.x , where a index rebuild has not been done. 


Read more...

Environment

SAP IQ 16.0 any platform

SAP IQ 16.1 any platform

Only databases that were upgraded from a IQ 15.x  version

Product

SAP IQ 16.1

Keywords

sybase, upgrade, CR825351, CR#825351 , 825351, CR812631, CR#812631 , 812631, key, token, dictionary, fail, query,  , 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 ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.