3560916 - Error 834 followed by stack trace and error 6103 - SAP ASE

• ASE errorlog reports error 834 followed by error 6103
• As a result the ASE may hang or show a blocking (zombie) spid that fills up the transaction log
  
  
• Typical log entries include:
  The example is from an issue on a user tempdb, but it can be seen on any type of database
  For a full sequence refer to attached file Full_ASE_log_sequence.txt
  
  Error: 834, Severity: 20, State: 3
  Illegal attempt to clean buffer BUF= ... (truncated)
  
  Error: 21, Severity: 20, State: 1
  WARNING - Fatal Error 834 occurred at Nov  5 2025  2:45PM.  Please note the error and time, and contact a user with System Administrator (SA) authorization.
  
  WARNING: Pss 0x000000033052e528 found with open sdes. pspid 1234, psuid 13, pcurdb 2, range entry 0, sdesp 0x00000002ebff8ee0, objid 1234567
  WARNING: Pss 0x000000033052e528 found with open sdes. pspid 1234, psuid 13, pcurdb 2, system table entry 0, sdesp 0x00000002ec28f758, objid 8.
  
  Error: 6103, Severity: 17, State: 1
  Unable to do cleanup for the killed process; received Msg 3300.
  
  
• Error 834 can be followed by a stacktrace that can include modules:
  
  bufunkeep_cache
  bufdbtlastlog
  buffree
  bufunkeep_do_decrement
  log__newpage
  plc__flush
  xls_preflush
  plcblock__flush
  finishlog

SAP Adaptive Server Enterprise (ASE) - All versions

error 834, error 6103, zombie spid, transaction log, buffer inconsistency, Adaptive Server Enterprise, Sybase database, process cleanup, spid issue, database reboot, log space release, internal memory structures , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , Problem