Symptom
- Client process using alter table to change a table's lock schema is unexpectedly terminated.
- Errorlog contains an Infected with signal 11 error in function alt__lock_fix_computedcol
Current process (0x870044) infected with signal 11 (SIGSEGV)
Address 0x0x00000000014f4681 (alt__lock_fix_computedcol+0x301), siginfo (code, address) = (1, 0x(nil))
SQL causing error: alter table xxx lock datarows
SQL Text: alter table xxx lock datarows
curdb = xx
curcmd = 306 program = isql
extended error information: hostname: xxxxxxxx login: xxxxxx
pcstkwalk+0x3a3()
ucstkgentrace+0x263()
ucbacktrace+0x50()
terminate_process+0x1057()
kisignal+0x31f()
ut_handle
alt__lock_fix_computedcol+0x301()
altlock_handle
alt_lock_change+0xd1e()
hdl_backout_msg
ut_handle
ut_handle
hdl_backout_msg
altertab+0x9c3()
s__altertab+0x4f()
s_execute+0x354c()
sequencer+0x948()
tdsrecv_language+0x189()
conn_hdlr+0x10c0()
end of stack trace
Read more...
Environment
SAP Adaptive Server Enterprise (ASE) 15.7
Product
Keywords
SIGSEGV, SEGV, infected, signal, alt__lock_fix_computedcol, 748008 , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , 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.
SAP Knowledge Base Article - Preview