2448640 - ERROR "Can't get a new log page in dbid X" with Signal 11 in la_alloc_one_page() - SAP ASE 16.0

• Getting the following error in the ASE error log:

ERROR: Can't get a new log page in dbid X (num_left=1, num_in_plc=1, num_in_plc_at_start=1, num_newlogpgs_allocated=0)

• It is followed by an "infected with signal 11" in the module la_alloc_one_page() with a stack trace:

Current process (0x102100a5) infected with signal 11 (SIGSEGV)
Address 0x0x0000000000ee6107 (la_alloc_one_page+0x207), siginfo (code, address) = (1, 0x0x0000000000000170)

• The stack trace includes functions:

la_alloc_one_page
log__newpage
plcblock__flush
xls_flush_plcqueue
plc__flush
xls_preflush
syslogs_finishlog
finishlog
xact__endxact
xact__commitxact
xact_commit

  Note: A complete stack trace is available under Attachments.

• A subsequent 1251 error is reported after the stack trace:

Error: 1251, Severity: 26, State: 1
An in-use preallocated semaphore cursor was encountered.
Error while undoing log row in database 'tempdb4'.  Rid pageid = 0; row num = 0.
WARNING: spid 779 with suid 4 and curdbid 0 has an active transaction in dbid 13 with xactid (0, 0).

SAP Adaptive Server Enterprise (ASE) 16.0

CR804338, CR#804338, 804338, SEGV, segmentation, storage, access, violation, fault, segfault, kisignal, stacktrace, registers , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Bug Filed