Symptom
-
First, the process exhausts the lock pool raising Error 1204 (other user processes are also raising the same error):
Error: 1204, Severity: 17, State: 2 occurred for User xxxx. Client IP address is 'xxx.xx.xx.xx'.
The message for this error is not shown in the ASE errorlog:
ASE has run out of LOCKS. Re-run your command when there are fewer active users, or contact a user with System Administrator (SA) role to reconfigure ASE with more LOCKS.
- Next, for the same process a message is logged indicating a possible heap memory corruption:
kbfalloc() retrieved null MEMFRAG from free list at 0x0x2aaab7dbfe10. Heap memory corruption may have occurred.
- ASE then reports an "infected with signal 11" error in the module kbfalloc() with a stack trace for this process while attempting to roll back the transaction:
Current process (0x12b30103) infected with signal 11 (SIGSEGV)
Address 0x0x000000000160846f (kbfalloc+0xb2f), siginfo (code, address) = (1, 0x0x0000000000000010)
- The stack trace includes functions:
kbfalloc
ubfallocf
createpool_n_alloc
memallocheap
scan_get_rowbuf
rec_undo_session
abort__all
xact__rollbackxact
xact__rollback_local
dropo
drop_with_retry
tmp_alldrop
s_free
s_pop
s_cleanframe
exc__raise
exc_raise
s_remap_lockid
s_lockstmt
Note: A complete stack trace is available under Attachments.
Read more...
Environment
SAP Adaptive Server Enterprise (ASE) 15.7 SP13x
Product
Keywords
CR810936, CR#810936, 810936 , 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.