SAP Knowledge Base Article - Preview

1912577 - Error log hits Error 839 "Grabbed buffer dirty but not writing.." followed by a stack trace - SAP ASE

Symptom

  • The ASE server reports one or many instances of Error 839 in the ASE errorlog, for example:

Msg 839, Level 21, State 1:
Server 'server_name', Line 1:
Grabbed buffer dirty but not writing: BUF=0x000001008f20a438, MASS=0x000001008f20a438, Buf#=0, page=0x000001008a5c8800, dbid=2, Mass vdevno=4, vpage=168136, Buf lpage=554184, Mass stat=0x4211208, Buf stat=0x1, size=2048, cid=0 ('default data cache'), Pinned xdes=0x0000000000000000, spid=0

  • The ASE server is shut down or becomes unusable (hang).

Read more...

Environment

  • Sybase Adaptive Server Enterprise (ASE) 15.0.3
  • Sybase Adaptive Server Enterprise (ASE) 15.5
  • SAP Sybase Adaptive Server Enterprise (ASE) 15.7

Product

SAP Adaptive Server Enterprise 15.7 ; Sybase Adaptive Server Enterprise 15.0 ; Sybase Adaptive Server Enterprise 15.5

Keywords

835, 6902, CR737543, CR#737543, 737543, LRU, chain, trace, flag, 897, diagnostics , KBA , tempdb , lru , lru chain , 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 ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.