Quantcast
Channel: SQL Server Database Engine forum
Viewing all articles
Browse latest Browse all 12963

SQL Server 2012: Can't start database after it crashed with millions of uncommitted transactions

$
0
0

Hi All,

A long running query with millions of uncommitted transactions was running when the server crashed. When I try to restart SQL Server 2012, I get the following messages in ERRORLOG:

2014-03-10 14:32:09.77 spid20s     Recovery of database 'SQL2012' (5) is 0% complete (approximately 6501 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2014-03-10 14:32:09.77 spid20s     Recovery of database 'SQL2012' (5) is 0% complete (approximately 11055 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-03-10 14:32:29.76 spid20s     Recovery of database 'SQL2012' (5) is 0% complete (approximately 6381 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-03-10 14:33:16.03 spid20s     Recovery of database 'SQL2012' (5) is 1% complete (approximately 6405 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-03-10 14:33:36.03 spid20s     Recovery of database 'SQL2012' (5) is 1% complete (approximately 6361 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-03-10 14:33:56.03 spid20s     Recovery of database 'SQL2012' (5) is 1% complete (approximately 6320 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-03-10 14:34:00.11 spid20s     Recovery of database 'SQL2012' (5) is 1% complete (approximately 6225 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-03-10 14:34:00.11 spid20s     22347 transactions rolled forward in database 'SQL2012' (5:0). This is an informational message only. No user action is required.
2014-03-10 14:34:00.11 spid20s     Recovery of database 'SQL2012' (5) is 1% complete (approximately 6225 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
2014-03-10 14:34:00.19 spid6s      Recovery of database 'SQL2012' (5) is 32% complete (approximately 230 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
2014-03-10 14:34:11.67 spid6s       Failed allocate pages: FAIL_PAGE_ALLOCATION 8
2014-03-10 14:34:11.67 spid6s     
Process/System Counts                         Value
---------------------------------------- ----------
Available Physical Memory                11810967552
Available Virtual Memory                    9752576
Available Paging File                    14068871168
Working Set                              3860353024
Percent of Committed Memory in WS               100
Page Faults                                 1168332
System physical memory high                       1
System physical memory low                        0
Process physical memory low                       0
Process virtual memory low                        1
2014-03-10 14:34:11.67 spid6s     

Pages of errors like the block above follow. This seems to be related to the bug described in kbase entry 2769594 but I have installed SP1 cumulative patches 2 and 3 with no success.

Thanks in advance

Zane


Viewing all articles
Browse latest Browse all 12963

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>