Symptom
Server hangs after process hit on error 1249 followed by errors 1251 and 6103. In the log:
=====
.....
.....
Diagnostics for error 1249 for spid 111 follow. Please contact Sybase Technical Support.
[xxx] PSS information: pstat=0x10100, p2stat=0x1000, p3stat=0x1800, pattention=0, plasterror=0, plockstat=0x0
....
....
[xxx] Failed SEMAWAIT at 0x111111111
...
....
[xxx] Head of the SEMAWAIT chain at 0x12222222
;;;;;
......
Diagnostics for error 1249 for spid 111 end here.
...
Error: 1249, Severity: 20, State: 1
Process became runnable before lock it was waiting for was released.
,,,
ex_raise
lock__semawait
lock_psema
log__lock
xls__get_lastlogbp
plc__flush
xls_pre_alloc_numclrs
dol_logdml
...
end of stack trace, spid xxx, kpid 555555555, suid vvv
....
....
Error: 1251, Severity: 26, State: 1
An in-use preallocated semaphore cursor was encountered.
Error while undoing log row in database 'dbname'. Rid pageid = 0; row num = 0.
....
....
Error: 6103, Severity: 17, State: 1
Unable to do cleanup for the killed process; received Msg 3300.
WARNING: spid xxx with suid vvv and curdbid yy has an active transaction in dbid yy with xactid (111111111, 11).
=====
Processes are blocked by the process that hit on error 1249.
Read more...
Environment
SAP Adaptive Server Enterprise 16.0 SP03 PL04 and higher
Product
Keywords
Error 1249 1251 6103 lock__semawait lock_psema log__lock xls__get_lastlogbp Process became runnable before lock Error while undoing log row in database SEMAWAIT 829918 CR 829918 CR829918 CR#829918 , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , 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.