[Edit 2014: there’s an additional bug in SQL Server 2012/2014 – see this post for details.]
Msg 831, Level 20, State 1, Line 1 Unable to deallocate a kept page.
More details are in KB article 919142, which was only recently made public.
Back in 2009 I started posting a summary at the end of the year of what I read during the year and people enjoy it
We’re tremendously excited to be developing a library of AI-focused courses, as well as new courses focused on traditional SQL Server topics, all based on
From now until mid-December we have our lowest prices ever on our signature 158-hour Blackbelt training bundle: US$1,599 for Lifetime access (no expiration) US$899 for
It’s been a while since I wrote one of these, but I’m picking up the series again. This is a question that came in through
Back in 2009 I started posting a summary at the end of the year of what I read during the year and people have been
(Yes, this is for last year!) Back in 2009 I started posting a summary at the end of the year of what I read during
With training and consulting from SQLskills, you’ll be able to solve big problems, elevate your team’s capacity, and take control of your data career.
4 thoughts on “(Not a) CHECKDB error “Unable to deallocate a kept page””
Thanks Paul.
Hi Lads,
I meet this issues on SQL Server 2012 with AGs.
No fun at all.
Please find err logs below.
Should I contact to Microsoft directly ?
“
During undoing of a logged operation in database ‘databaseName’, an error occurred at log record ID (26946:8958:47). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.
Unable to deallocate a kept page.
SQL Server must shut down in order to recover a database (database ID 21). The database is either a user database that could not be shut down or a system database. Restart SQL Server. If the database fails to recover after another startup, repair or restore the database.
“
Yes – likely corruption that you’ll need to recover from.
I also met the same error as Jakub this weekend on a SQL 2012 SP1 (11.0.3349).
Any chance on “hoping” this bug was reintroduced by any chance?