There was an error in the way that out-of-buffers exceptions were handled, which has now been fixed. The error occurred only when all buffer cache pages were in use. When all buffer cache pages are in use, the server is sometimes unable to correctly update the internal state of the database. When this situation occurs, out-of-buffers exceptions are logged, like this:
Exception Thrown from slib/s_blockmap.cxx:6953, Err# 0, tid 26 origtid 26
O/S Err#: 0, ErrID: 2097 (s_nobuffersexception); SQLCode: -1009031, SQLState: 'QSA31', Severity: 14
main Bufman: All buffer cache pages are in use, ask your DBA to increase the size of the buffer cache. Current buffer cache is 13753MB.
When these exceptions occur, the server should roll back the current transaction to avoid corrupting the database; but in some instances this did not occur.
The exception above was incorrectly followed by this commit message:
The errors caused by committing a transaction do not appear immediately, but are detected at some later time when an 밒ncorrect page header read (IPHR) error is reported:
main Bufman: Incorrect page header read; from slib/s_trycatch.cxx:3033 into buffer a2e1748
CR812764, CR#812764, 812764, "out of buffers", s_blockmap, IPHR, "Incorrect page header read", "main Bufman", 812764, , KBA , BC-SYB-IQ , Sybase IQ , Problem
About this pageThis 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.