Error 8914
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsTroubleshootingCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: DBCC CHECKDB Errors SQL Server dbcc checkdb with repair_allow_data_loss > SQL Server High Availability and Disaster Recovery Question 0 Sign dbcc page in to vote SQL 2005I ran the following: DBCC CHECKDB (‘DATABASENAME’) Errors are produced DBCC CHECKDB dbcc checkdb repair ('DATABASENAME') DBCC results for 'AllDocStreams'. Msg 8914, Level 16, State 1, Line 1 Incorrect PFS free space information for page (1:26839) in object ID 181575685, index ID 1, partition ID 293374720802816, alloc unit ID 71788018805309440 (type LOB data). Expected value 0_PCT_FULL, actual value 100_PCT_FULL. I wanted to view the PAGE by doing
dbcc traceon(3604) DBCC PAGE (1,26839,1) (But keeps telling me there is no page) So i tried DBCC IND('TEST','AllDocStreams',1) Found the PagePID of 26839 then i found IAMFID so i tried DBCC PAGE (1,1577,3) still no page I was trying to find the PCT FULL on the page? but can't find the page its talking about. I can do a REPAIR_WITH_DATA_LOSS but i wanted to figure out what it is actually repairing and what the message is really telling me Thanks Thursday, January 24, 2008 3:48 PM Reply | Quote Answers 1 Sign in to vote The error is pretty benign - it's not an actual corruption. It's saying that the PFS (Page Free Space) entry for that page has the wrong amount of free space noted - 100% instead of 0%. All this means is that the page may be picked up be a free-space scanner looking to insert data into a text page and it will find the page is actually full and move on to the next page. All repair will do is set the correct free space setting, but you'll need to take the database into single-user mode (essSQL Server experts to answer whatever question you can come up with. Our new SQL Server Forums are live! Come on over! We've restricted the ability to create new threads on these forums. SQL Server Forums Profile | ActiveTopics | Members | Search | ForumFAQ Register Now and get your question answered! Username: Password: Save Password Forgot your Password? All Forums General SQL Server Forums Data Corruption Issues Advice for "Incorrect PFS free space information" Reply to Topic Printer Friendly Author Topic kensai Posting Yak Master 172 Posts Posted-07/25/2011: 07:54:11 https://social.msdn.microsoft.com/Forums/sqlserver/en-US/e34bbbab-6413-4377-9bcb-29abb9af543d/dbcc-checkdb-errors?forum=sqldisasterrecovery One of our databases is giving this error: DBCC CHECKDB (MyDb) WITH NO_INFOMSGS, ALL_ERRORMSGS Msg 8914, Level 16, State 1, Line 1 Incorrect PFS free space information for page (1:218) in object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). Expected value 0_PCT_FULL, actual value 100_PCT_FULL. Msg 8914, Level 16, State 1, Line 1 Incorrect PFS free http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=163437 space information for page (1:219) in object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). Expected value 0_PCT_FULL, actual value 100_PCT_FULL. Msg 8914, Level 16, State 1, Line 1 Incorrect PFS free space information for page (1:220) in object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). Expected value 0_PCT_FULL, actual value 100_PCT_FULL. Msg 8914, Level 16, State 1, Line 1 Incorrect PFS free space information for page (1:221) in object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). Expected value 0_PCT_FULL, actual value 100_PCT_FULL. CHECKDB found 0 allocation errors and 4 consistency errors in table 'sys.sysobjvalues' (object ID 60). CHECKDB found 0 allocation errors and 4 consistency errors in database 'MyDb'. repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (MyDb). The system seem to work fine, we're not getting any errors. I'm really reluctant to run repair_allow_data_loss because this one is a very critical database. I appreciate any advice on this.Using Microsoft SQL Server 2008 (SP2) - 10.0.4279.0 (X64) Mar 10 2011 15:03:15 Copyright (c) 1988-2008 Microsoft Corporation Enterprise Edition (64-bi
running DBCC CHECKDB() job on SQL 2008 R2 SP1 with SQL 2005 compatibility Level databases, it failed with the below DBCC results https://sqlarchive.wordpress.com/2015/01/11/consistency-errors-due-to-msg-8914-pfs-free-space/ for ‘MESTEMPLATEDOCUMENTS'. Msg 8914, Level 16, State 1, Line 1 Incorrect PFS free space information for page (1:87991) in object ID 1394416337, index ID 1, partition ID 72057602418868224, alloc unit ID 72057601377828864 (type LOB data). Expected value 0_PCT_FULL, actual value 100_PCT_FULL. Msg 8914, Level 16, State 1, Line 1 Incorrect PFS free space information for dbcc checkdb page (1:88697) in object ID 1394416337, index ID 1, partition ID 72057602418868224, alloc unit ID 72057601377828864 (type LOB data). Expected value 0_PCT_FULL, actual value 100_PCT_FULL. Msg 8914, Level 16, State 1, Line 1 Incorrect PFS free space information for page (1:91929) in object ID 1394416337, index ID 1, partition ID 72057602418868224, alloc unit ID 72057601377828864 (type dbcc checkdb with LOB data). Expected value 0_PCT_FULL, actual value 100_PCT_FULL. Msg 8914, Level 16, State 1, Line 1 Incorrect PFS free space information for page (1:91931) in object ID 1394416337, index ID 1, partition ID 72057602418868224, alloc unit ID 72057601377828864 (type LOB data). Expected value 0_PCT_FULL, actual value 100_PCT_FULL. Msg 8914, Level 16, State 1, Line 1 Incorrect PFS free space information for page (1:91932) in object ID 1394416337, index ID 1, partition ID 72057602418868224, alloc unit ID 72057601377828864 (type LOB data). Expected value 0_PCT_FULL, actual value 100_PCT_FULL. There are 0 rows in 1 pages for object "MESTEMPLATEDOCUMENTS". CHECKTABLE found 0 allocation errors and 5 consistency errors in table ‘MESTEMPLATEDOCUMENTS'(object ID 1394416337). repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKTABLE (dbo.MESTEMPLATEDOCUMENTS'). DBCC execution completed. If DBCC printed error messages, contact your system administrator. Resolution After a Brief research found this solution from Paul Randall http://www.sqlskills.com/blogs/paul/corruption-bug-that-people-are-hitting-msg-8914-pfs-free-space/ As solution didn’t work, I had to go ahead and do the repair Implementing the repair on Dev or Test