- ASE errorlog shows a signal 11 including stack trace functions ind_rowcopy and level0__getnextrow
- The stacktrace shows that the failed process was processing a cursor:
SQL Text: DECLARE cursor_name CURSOR FOR
- Within the stacktrace sequence, 'lasterror' shows error 9504 (lasterror = 9504) which means that an isolation level 0 cursor scan has failed
- Error 9504 is "An isolation level 0 cursor scan has failed on an attempted restart for cursor '...'. The cursor is being closed.
- The stack trace includes the following functions:
- The server stacktrace can be generated from various starting points as indicated below, but the defining elements are the ones above
- Known sequences include a segmentation fault at function (1) ind__itagsetup or (2) text
Current process (0x40b10400) infected with signal 11 (SIGSEGV)
Address 0x00000000803dc730 (ind__itagsetup+0x30) ...
- Note: An example of a complete stacktrace of this variety is available under Attachments.
Current process (0x255014d) infected with signal 11 (SIGSEGV)
Address 0x0000000100669b1c (text.fdpr.chunk.4+0x18) -- AIX platform
Address 0x0000000100669b1c (text+0x12)
- SAP Adaptive Server Enterprise (ASE) 15.7
CR#609943, CR609943, 609943, traceflag, trace , flag, 457, insensitive, sensitive, SEGV, segmentation, storage, access, violation, fault, segfault, kisignal, stack, registers , KBA , memory corruption , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Bug Filed
About this pageThis 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.