Symptom
- ASE errorlog reports a burst of spids hitting a signal 11 at address ubffreef
- The affected spids are child / worker processes (WP)
- As there are many intertwined log records for each WP, the error sequence in the log is long and difficult to read
- As there are many intertwined log records for each WP, the error sequence in the log is long and difficult to read
- A somewhat cleaned up example of ASE log records looks like :
- with Parent_spid:Child_spid are highlighted in this way:
00:0016:03291:04888:2024/11/09 11:08:35.54 kernel Address 0x0000000102462c58 (ubffreef+0x170), siginfo (code, address) = (50, 0x0000000045435461)
00:0009:03291:04478:2024/11/09 11:08:35.55 kernel Address 0x0000000102462c30 (ubffreef+0x148), siginfo (code, address) = (50, 0x415356494e474f1c)
00:0010:03291:03259:2024/11/09 11:08:35.54 kernel Address 0x0000000102462c30 (ubffreef+0x148), siginfo (code, address) = (50, 0x0b5a494e57412069)
...
00:0016:03291:04888:2024/11/09 11:08:35.55 kernel Current process (0x270f1388) infected with signal 11 (SIGSEGV)
00:0009:03291:04478:2024/11/09 11:08:35.54 kernel Current process (0x26f3137a) infected with signal 11 (SIGSEGV)
00:0010:03291:03259:2024/11/09 11:08:35.54 kernel Current process (0x27111389) infected with signal 11 (SIGSEGV)
and each spid has a stack trace including routines
ubffreef
LeMJOp::_LeOpRelease
s_result_const_memfree
kw_exec
- with Parent_spid:Child_spid are highlighted in this way:
Read more...
Environment
SAP Adaptive Server Enterprise (ASE) 16.0 SP03 & SP04
Product
SAP Adaptive Server Enterprise 16.0
Keywords
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.