/support/notes/service/sap_logo.png){kind=logo}
SAP Knowledge Base Article - PreviewSymptom
SIGSEGV is caught by VEH_Optimize
Return VXACTION_CONTINUE from VEH_Optimize
Address 0x0x00000000016fb962 (Optimize+0xe12), siginfo (code, address) = (1, 0x0x000000000017bd0c)
Current process (0x4333012b) infected with signal 11 (SIGSEGV)
Read more...
Environment
SAP Adaptive Server Enterprise (ASE) 16 SP04 PL03
Product
SAP Adaptive Server Enterprise 16.0
Keywords
SEGV, segmentation, storage, access, violation, segfault, kisignal, stacktrace, stack, CR828013, CR#828013, 828013 , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , 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.
/support/notes/service/facebook.svg)
/support/notes/service/twitter.svg)
/support/notes/service/youtube.svg)
/support/notes/service/linkedin.svg)
/support/notes/service/instagram2.svg)