FIX: Latch time-out error when you have heap tables and when data compression is enabled in SQL Server 2008 R2 or in SQL Server 2012

Article translations Article translations
Article ID: 2719217 - View products that this article applies to.
Microsoft distributes Microsoft SQL Server 2008 R2 and Microsoft SQL Server 2012 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 and Microsoft SQL Server 2012 fix release.
Expand all | Collapse all

On This Page

Symptoms

Consider the following scenario:
  • You have the hotfix from Microsoft Knowledge Base (KB) article 2590839 installed on a Microsoft SQL Server 2008 R2 or Microsoft SQL Server 2012 instance.
  • You host a database on an instance of SQL Server.
  • The database has a table that is stored as a heap.
  • You enable data compression on the table.
  • You enable Read Committed Snapshot Isolation (RCSI) for the database.
In this scenario, you receive the following latch time-out message on the Page Free Space (PFS) page:

Time Stamp SpidID Time out occurred while waiting for buffer latch -- type 3, bp 0000000500DA4380, page 1:1, stat 0xb, database id: 10, allocation unit id: 6488064, task 0x00000004538BF0C8 : 0, waittime 300 seconds, flags 0x100000001a, owning task 0x00000004538BF0C8. Continuing to wait.

Note To recover from this issue, you might have to restart SQL Server, or you might have to kill the process in Task Manager.

Cause

This issue occurs because an exclusive latch on the PFS page is not released after a ghost bit is updated on the PFS page.

Resolution

Service pack information for SQL Server 2008 R2

To resolve this problem, obtain the latest service pack for SQL Server 2008 R2. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2527041 How to obtain the latest service pack for SQL Server 2008 R2

Cumulative update information

SQL Server 2008 R2 Service Pack 1

The fix for this issue was first released in Cumulative Update 8. For more information about how to obtain this cumulative update package for SQL Server 2008 R2 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
2723743 Cumulative update package 8 for SQL Server 2008 R2 SP1
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 Service Pack 1 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2567616 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 SP1 was released

SQL Server 2012

The fix for this issue was first released in Cumulative Update 2 for SQL Server 2012. For more information about how to obtain this cumulative update package for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
2703275 Cumulative update package 2 for SQL Server 2012 is available
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2692828 The SQL Server 2012 builds that were released after SQL Server 2012 was released

SQL Server 2008 R2

The fix for this issue was first released in Cumulative Update 14 for SQL Server 2008 R2. For more information about how to obtain this cumulative update package for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
2703280 Cumulative update package 14 for SQL Server 2008 R2
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
981356 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Properties

Article ID: 2719217 - Last Review: November 19, 2012 - Revision: 5.0
Applies to
  • Microsoft SQL Server 2012 Developer
  • Microsoft SQL Server 2012 Enterprise
  • Microsoft SQL Server 2012 Standard
  • Microsoft SQL Server 2012 Web
  • Microsoft SQL Server 2008 R2 Datacenter
  • Microsoft SQL Server 2008 R2 Developer
  • Microsoft SQL Server 2008 R2 Enterprise
  • Microsoft SQL Server 2008 R2 Standard
  • Microsoft SQL Server 2008 R2 Web
  • Microsoft SQL Server 2008 R2 Workgroup
Keywords: 
kbtshoot kbqfe kbfix kbsurveynew kbexpertiseadvanced KB2719217

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com