O Error Bad Page Id Detected During Read
Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On Home » SQL Server 7,2000 » Data Corruption » Error 823: I/O error error 823 severity 24 state 2 (bad page ID) detected... Error 823: I/O error (bad page ID) detected during read dbcc checkdb at offset 0x000000034ee000 in file 'E:\SQL\MSSQL\data\ls\Longshine.MDF' Rate Topic Display Mode Topic Options Author Message john_laspadajohn_laspada Posted Wednesday, November 14, 2007 2:08 PM Forum Newbie Group: General Forum Members Last Login: Tuesday, July 24, 2012 10:00 PM Points: 2, Visits: 51 This is a duzy:Was called to assist the DBA with an HR database that had not been backed up since Feb 2007, great. The following set of activities have been run with the following results. Any assistance would be greatly appreciated:Database Version: SQL 2000-8.00.194 (SQL Server 2000 RTM) - No service packsDatabaseName: LongShineMain Table trying to recover: C41select * from longshine..c41/*Server: Msg 823, Level 24, State 2, Line 1I/O error (bad page ID) detected during read at offset 0x000000034ee000 in file 'E:\SQL\MSSQL\data\ls\LongShine_Data.MDF'.Connection Broken*/DBCC CHECKDB('Longshine')/*CHECKDB found 0 allocation errors and 87 consistency errors in database 'LongShine'.repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (LongShine ).DBCC execution completed. If DBCC printed error messages, contact your system administrator.*/dbcc dbreindex('C41') /*Server: Msg 823, Level 24, State 2, Line 1I/O error (bad page ID) detected during read at offset 0x00000002100000 in file 'E:\SQL\MSSQL\data\ls\LongShine_Data.MDF'.Connection Broken*/DBCC CHECKTABLE ('LongShine.dbo.C41') /*There are 10511 rows in 411 pages for object 'C41'.CHECKTABLE found 0 allocation errors and 40 consistency errors in table 'C41' (object ID 821577965).repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKTABLE (LongShine.dbo.C41 ).*/The DBA has told me that she has tried to run the repair_allow_data_loss and they are missing around 61 rows of data from this year they are trying to query. I was trying to identify if I could read the actual data pages with using a dbcc traceon(3406) dbcc page('longshine,1,AnyPageNumber,1) in order to try to piece the data together but I cannot. I would even try to rebuild, not sure what to do or if anything is even possible. Anyone want to advise or work with me to see if the data can be read and pieced back together?John Post #422315 Paul RandalPaul Randal Posted Wednesday, November 14, 2007 2:43 PM
SQL 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 I/O http://www.sqlservercentral.com/Forums/Topic422315-265-1.aspx error (bad page ID) detected during read at... Reply to Topic Printer Friendly Author Topic ProgressBoy Starting Member 14 Posts Posted-03/10/2009: 11:10:19 I have only seen this error on SQL 2000 BOXES. Has anyone observed it on SQL 2005? Is it possible to get the same error in SQL 200%?I/O error (bad http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=121361 page ID) detected during read at offset ..... in file "......." sodeep Flowing Fount of Yak Knowledge USA 7174 Posts Posted-03/10/2009: 11:32:48 http://support.microsoft.com/kb/828339 paulrandal Yak with Vast SQL Skills USA 899 Posts Posted-03/10/2009: 13:25:37 And yes, you can see these on all versions.Paul S. Randal, Managing Director, SQLskills.com (www.SQLskills.com/blogs/paul)SQL Server MVP, Contributing Editor of TechNet MagazineAuthor of SQL 2005 DBCC CHECKDB/repair codeAuthor & Instructor of Microsoft Certified Master - Database course Topic Reply to Topic Printer Friendly Jump To: Select Forum General SQL Server Forums New to SQL Server Programming New to SQL Server Administration Script Library Data Corruption Issues Database Design and Application Architecture SQL Server 2012 Forums Transact-SQL (2012) SQL Server Administration (2012) SSIS and Import/Export (2012) Analysis Server and Reporting Services (2012) Replication (2012) Availability Groups and DR (2012) Other SQL Server 2012 Topics SQL Server 2008 Forums Transact-SQL (2008) SQL Server Administration (2008) SSIS and Import/Export (2008) High Availability (2008) Replication (2008) Analysis Ser
offset 0x0000000f3e4000 If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the http://www.dbforums.com/showthread.php?894211-I-O-error-(bad-page-ID)-detected-during-read-at-offset-0x0000000f3e4000 register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. Results 1 to 3 of 3 Thread: I/O error (bad page ID) detected during read at offset 0x0000000f3e4000 Tweet Thread Tools Show Printable Version Subscribe to this Thread… Search Thread Advanced Search Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 08-25-03,05:11 #1 o error Bluetooth View Profile View Forum Posts Registered User Join Date Aug 2003 Posts 4 Unanswered: I/O error (bad page ID) detected during read at offset 0x0000000f3e4000 Hi, Can anyone help me with this error? Microsoft OLE DB Provider for ODBC Drivers (0x80004005) [Microsoft][ODBC SQL Server Driver][SQL Server]I/O error (bad page ID) detected during read at offset 0x0000000f3e4000 in file 'C:\Program Files\Microsoft SQL Server\MSSQL\Data\RVHS_database.mdf'. What should i do o error bad to recover my database? Please help me out Reply With Quote 08-25-03,08:36 #2 dbadelphes View Profile View Forum Posts Registered User Join Date Feb 2003 Location Montreal, Canada Posts 117 Re: I/O error (bad page ID) detected during read at offset 0x0000000f3e4000 use DBCC CHECKDB (use NOINDEX first; id an index is corrrupted it won't be a problem), then try REPAIR_FAST or REPAIR_REBUILD (it's time consuming) - see Books Online for more Originally posted by Bluetooth Hi, Can anyone help me with this error? Microsoft OLE DB Provider for ODBC Drivers (0x80004005) [Microsoft][ODBC SQL Server Driver][SQL Server]I/O error (bad page ID) detected during read at offset 0x0000000f3e4000 in file 'C:\Program Files\Microsoft SQL Server\MSSQL\Data\RVHS_database.mdf'. What should i do to recover my database? Please help me out Steve Reply With Quote 08-25-03,10:31 #3 rdjabarov View Profile View Forum Posts Registered User Join Date Jul 2003 Location San Antonio, TX Posts 3,662 ooops, I don't think the recommended switches will do the trick. It 's REPAIR_ALLOW_DATA_LOSS that will fix page allocation errors (which is what you have here). Do it within a transaction and don't commit untill you see what repairs are done and what errors got fixed. Reply With Quote Quick Naviga