[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.
Over the last year, after we were forced to move our Immersion Events online, we’ve realized the power and flexibility of online training and we
Our classes are all open for registration and we have deep discounts running through the end of the month! Once again they will all be online,
(The Curious Case of… used to be part of our bi-weekly newsletter but we decided to make it a regular blog post instead so it can sometimes be more
The last post of the year! It’s been a terrible year all round, as I’m sure you’ll all agree, and I’m very glad we’re rolling
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
(The Curious Case of… used to be part of our bi-weekly newsletter but we decided to make it a regular blog post instead so it can sometimes be more
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?