SAP Knowledge Base Article - Preview

2287666 - IQ server got crashed with "slib/s_vdo.cxx:733".

Symptom

1.   IQ server got crashed while running sp_iqcheckdb against a problematic table with VERIFY mode.
  DBCC was running in order to check the table because the IQ server also got crashed in a row due to the table.
  Also, the same crash happened whenever running below commands as well.
  It seems like the table was corrupted.

select "count"() from "OWNER001"."TAB001"
call "sp_iqcheckdb"('verify table OWNER001.TAB001')
drop index "OWNER001"."TAB001"."COL001"
alter table "OWNER001"."TAB001" rename "TAB001_CRASH"
drop table "OWNER001"."TAB001"
call "sp_iqrowdensity"('table OWNER001.TAB001')


 
 [Abort error message]
 **************************************************
 ***   SAP IQ Abort:
 ***      From:  slib/s_vdo.cxx:733
 ***      PID: 27096
 ***      Exception Location: 0x9ffffffe6d6d5f40
 ***      Error ID: 2054,  Exception Type: hs_vdoexception
 ***      Thread: 139  (TID: 19, Original TID: 19)
 ***      Error #: 5,  O/S Error #: 0
 ***      Argument: 
 -- (slib/s_vdo.cxx 733)
 ***      Argument:  1775
 ***      Argument:  1
 **************************************************

2.  The stacks generated are almost identical, butdepending on the executed transactions, they are getting different in the middle of abort thread stacks.
 
 _Z13ucstkgentraceii + ..................
 _Z14DumpAllThreadsPKcji + ..................
 _Z9hos_ABORTPKcjRK13hos_exceptionPcS4_ +..................
 _Z10ThrowAbortRK13hos_exception + ..................
 _Z5ThrowRK13hos_exception + ..................
 _ZN6hs_vdo8GetValueERK11hs_vdorecidmPvPm + ..................
 _ZN11db_TableDef16InstantiateIndexEP11db_IndexDefP7UIIndexP10db_Catalog + ..................
 _ZN11db_TableDef11LoadColumnsEP7UITableP10db_CatalogjjP13st_connection + ..................
 _ZN11db_TableDef9LoadTableEP7UITableP10db_CatalogP11st_databasejjP8st_txncbjP13st_connectioni + ..................
 _ZN10db_Catalog9LoadTableEP7UITablejjjP8st_txncbji + ..................
 _ZN10db_Catalog16FindTableVersionEP13st_connectionP7UITablejjj + ..................
 _ZN10db_Catalog17FindTableByITableEP7UITablejjj + ..................
 _ZN18opt_TableReference16InitTableColumnsEP7df_HeapP10opt_Select + ..................    // abort thread stacks are getting different starting from this line depending on tasks which caused the crash.
 _ZN10opt_Select16InitializeTablesEv + ..................
 _ZN10opt_Select23InitializeNestedQueriesEP12opt_QueryExp + ..................
 _ZN10opt_Driver12GenerateTreeEP9QueryNodeP9st_cursorPK11a_statementP7UITableP7UIIndexP4s_bmPjPP19db_RebuildIndexInfoiP7a_tableP18hos_vector_noerrorP8hs_storeiP22db_IQParallelIndexInfoP16rv_MergeCmdState + ..................
 _ZN15st_cursorIQtoSA5ParseEv + ..................
 _ZN15st_cursorIQtoSA8DescribeEv + ..................
 _ZN17df_DescribeCursor5ParseEv + ..................
 _ZN10st_command24DoCmdThroughResourceGateEv + ..................
 _ZN8st_iqdml14DescribeCursorEP11a_statementP12UIConnectionP8UICursorP13a_cursor_spec + ..................

3. It was possible to retrieve the all rows from the problematic table and migrate them into a new table.

4. CR 796275 had been reported with the similar stacktrace.


Read more...

Environment

  • IQ 16.0 SP10.08
  • HP-UXi 11.31
  • Multiplex

Product

SAP IQ 16.0

Keywords

SAP IQ, crash, s_vdo, GetValue, _ZN6hs_vdo8GetValueERK11hs_vdorecidmPvPm , 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.