Select the product you need help with
FIX: "Cannot locate version record and page is not allocated" error message occurs when you rebuild an index by using the ONLINE option in SQL Server 2005, in SQL Server 2008 or in SQL Server 2008 R2Article ID: 2413430 - View products that this article applies to. Microsoft distributes Microsoft SQL Server 2005, Microsoft SQL Server 2008 and Microsoft SQL Server 2008 R2 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 2005, SQL Server 2008 or SQL Server 2008 R2 release. On This PageSYMPTOMSConsider the following scenario:
In this scenario, an assertion error occurs, and you receive the following messages in the SQL Server error log: <Date><Time> <spid> * BEGIN STACK DUMP: <Date><Time> <spid> *<Date><Time> <spid> <Date><Time> <spid> * <Date><Time> <spid> * Location: AppendOnlyVerStoreMgr.cpp:731 <Date><Time> <spid> * Expression: 0 <Date><Time> <spid> * SPID:<spid> <Date><Time> <spid> * Process ID: 6328 <Date><Time> <spid> * Description: Cannot locate version record and page is not allocated. Status = 3 <Date><Time> <spid> * <Date><Time> <spid> * Input Buffer 170 bytes - <Date><Time> <spid> * ALTER INDEX <Table Name> ON <Index> REBUILD WITH(O <Date><Time> <spid> * NLINE = ON) CAUSEThis issue occurs because the versioning information for a new record of the index key is copied from the old record of the index key. Therefore, the error occurs when the index is rebuilt. RESOLUTIONCumulative update informationSQL Server 2008 R2The fix for this issue was first released in Cumulative Update 5. For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base: 2438347 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 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:
(http://support.microsoft.com/kb/2438347/
)
Cumulative Update package 5 for SQL Server 2008 R2 981356
(http://support.microsoft.com/kb/981356/
)
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was releasedSQL Server 2005 Service Pack 4The fix for this issue was first released in Cumulative Update 1 for SQL Server 2005 Service Pack 4. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:2464079 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 2005 fix release. Microsoft recommends 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:
(http://support.microsoft.com/kb/2464079/LN/
)
Cumulative update package 1 for SQL Server 2005 Service Pack 42485757 Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 4 hotfix to an installation of SQL Server 2005 Service Pack 4. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
(http://support.microsoft.com/kb/2485757/LN/
)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 4 was released SQL Server 2005 SP3The fix for this issue was first released in Cumulative Update 12. For more information about how to obtain this cumulative update package for SQL Server 2005 SP3, click the following article number to view the article in the Microsoft Knowledge Base:2345449 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 2005 SP3 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:
(http://support.microsoft.com/kb/2345449/
)
Cumulative update package 12 for SQL Server 2005 Service Pack 3 960598
(http://support.microsoft.com/kb/960598/
)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released SQL Server 2008 Service Pack 1The fix for this issue was first released in Cumulative Update 11 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:2413738 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 fix release. Microsoft recommends 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:
(http://vkbexternal.partners.extranet.microsoft.com/VKBWebService/ViewContent.aspx?scid=KB;LN;2413738)
Cumulative update package 11 for SQL Server 2008 Service Pack 1970365 Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
(http://vkbexternal.partners.extranet.microsoft.com/VKBWebService/ViewContent.aspx?scid=KB;LN;970365)
The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was releasedSQL Server 2008 Service Pack 2The fix for this issue was first released in Cumulative Update 2 for SQL Server 2008 Service Pack 2. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:2467239 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 fix release. Microsoft recommends 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:
(http://support.microsoft.com/kb/2467239/LN/
)
Cumulative update package 2 for SQL Server 2008 Service Pack 22402659 Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 2 hotfix to an installation of SQL Server 2008 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
(http://support.microsoft.com/kb/2402659/LN/
)
The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released WORKAROUNDTo work around this issue, rebuild the index of this database by setting the ONLINE option to OFF in the query. STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. REFERENCESFor more information about online index operations, visit the following Microsoft website: General information about index operations
(http://msdn.microsoft.com/en-us/library/ms177442(v=SQL.90).aspx)
Detailed description of online index operations
(http://msdn.microsoft.com/en-us/library/ms191261(v=SQL.90).aspx )
Properties |


Back to the top








