Symptom
When an SAP IQ 15.x database with with HG indexes is upgraded to 16.0 and DML is run on these tables, SAP IQ may crash in “hs_ohcidentity::operator=( const hs_ohcidentity& id).
stack trace below will be generated:
===== Thread Number xxxxxxxxxxxxxxx (IQ connID: 0000xxxxxx) =====
pc: 0x7f9b671d2e92 pcstkwalk(stk_trace*, int, db_log*, hos_fd*)+0x32
pc: 0x7f9b671d3501 ucstkgentrace(int, int)+0x121
pc: 0x7f9b671d474e DumpAllThreads(char const*, unsigned int, int)+0x12e
pc: 0x7f9b66f612ce hos_ABORT(char const*, unsigned int, char const*, char*, char*)+0x19e
pc: 0x7f9b67caf95f SigHndlr+0x4f
pc: 0x7f9d047ea850 _fini+0x9b6c01c8
pc: 0x7f9b678d72c3 hs_ohcidentity::operator=(hs_ohcidentity const&)+0x2a3
pc: 0x7f9b679023e3 hs_ohc::hs_ohc(db_IndexDef*, s_openmode, hs_dp const*)+0x9b3
pc: 0x7f9b67d61308 db_IndexDef::OpenSIndexWithLock(unsigned int)+0xb38
...
Read more...
Environment
SAP IQ 16.0
Product
SAP IQ 16.0
Keywords
KBA , BC-SYB-IQ , Sybase IQ , Bug Filed
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.