BUG: Using PINTABLE on SYSOBJECTS May Cause Memory Starvation (221978)
The information in this article applies to:
This article was previously published under Q221978
BUG #: 18617 (SQLBUG_65)
SYMPTOMS
When either DBCC NEWALLOC or DBCC CHECKALLOC is executed on a database in which the sysobjects table has been pinned in memory, many pages from other tables may also become pinned, causing the data cache to become stressed. SQL Server may appear to be slow or to stop responding and the following errors may be reported in the error log:
spid21 Lazywriter: WARNING, LRU list is empty (1 free bufs, 3945 total bufs)
bufwait: timeout, BUF_IO, bp 0xf2c220, pg 0x1049, stat 0x801100/0x6, obj 0, bpss 0xfbe468
WORKAROUND
Do not pin the sysobjects table. Use DBCC UNPINTABLE to mark the sysobjects table as no longer being resident in RAM.
For more information on DBCC PINTABLE and DBCC UNPINTABLE, see the SQL Server Books Online.
STATUS
Microsoft has confirmed this to be a problem in SQL Server 6.5.
Modification Type: | Major | Last Reviewed: | 10/3/2003 |
---|
Keywords: | kbBug kbpending KB221978 |
---|
|