SAP Knowledge Base Article - Preview

3601647 - 707 reported after DSI thread goes down while performing an insert - ASE

Symptom

  • DSI thread goes down while an insert was running
  • statement cache is enabled
  • 707 error is reported when querying table where insert fail when DSI thread went down

Error: 707, Severity: 20, State: 11
System error detected during attempt to free memory at address 0x2abdc3d04000. Please consult the ASE error log for more details.

  • stack trace reported in ASE error log

pcstkwalk
ucstkgentrace
ucbacktrace
terminate_process
hdl_default
s_handle
exc__raise
exc_raise
mem__pagesfree
mem_freepages
mem__free_this_phdr
memfree
mem_procmem_lastchance_clean
terminate_process
hdl_default
s_handle
exc__raise
exc_raise
mem__pagesfree
mem_freepages
mem__free_this_phdr
memfree
s_execute

  • appears that when DSI thread went down, an index got corrupted on the insert
  • After rebooting ASE server, re-running query the 707 is still reported along with stack
  • Forcing a different index in the query which generated the stack, the 707 is no longer reported
  • drop and reported the index in the query that failed, then resuming DSI thread the 707 and stack trace reappears
  • ONLY WAY TO RESOLVE 707 ERROR IS TO RESTORE FROM BACKUPS


Read more...

Environment

SAP Adaptive Server Enterprise (ASE) 16.0 SP04

Product

SAP Adaptive Server Enterprise 16.0.4

Keywords

707, CR 830701 , 830701, DSI, index, replication , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Product Enhancement

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.