Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
timothyvb
Starting Member
2 Posts |
 Posted - 2013-10-24 : 19:34:12
|
| Hi all, brand new here. I've been looking into a corruption issue for a client and we are receiving the following error when running dbcc.Msg 8928, Level 16, State 1, Line 1Object ID 418100530, index ID 0, partition ID 27400636334080, alloc unit ID 27400636334080 (type In-row data): Page (4:5904588) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 418100530, index ID 0, partition ID 27400636334080, alloc unit ID 27400636334080 (type In-row data), page (4:5904588). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -1.CHECKDB found 0 allocation errors and 2 consistency errors in table 'appt_slot_templates' (object ID 418100530).CHECKDB found 0 allocation errors and 2 consistency errors in database 'NGProd'.repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (NGProd).From all the research that I've done we are looking at repairing with data loss at this point since the client doesn't have a clean back up. Any advise?Thanks!Tim |
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2013-10-25 : 16:11:07
|
| That should resolve the corruption issue, but you will likely lose that page. If you have any backup that contains that page, you could try to either restore the page, or after repairing with data loss, retrieve the lost data from that backup (Even if it is old, it may be better than losing it entirely).-ChadMicrosoft Certified Master SQL Server 2008 |
 |
|
|
prett
Posting Yak Master
212 Posts |
Posted - 2013-10-29 : 23:33:05
|
| Is there any problem with the backup? |
|
|
|
elliswhite
Starting Member
36 Posts |
Posted - 2014-05-05 : 01:49:52
|
| Hi The best solution if DBCC CHECKDB reports consistency errors is to restore from a known good backup. However, if you cannot restore from a backup, then CHECKDB provides a feature to repair errors. If system level problems such as the file system or hardware may be causing these problems, it is recommended you correct these first before restoring or running repair.You can try this also:- • Check the Windows System Event Log for any system level, driver, or disk related errors • Check the integrity of the file system with the chkdsk command. • Run any diagnostics provided by your hardware manufacturers for the computer and/or disk system. • Work with your hardware vendor or device manufacturer to ensure: • The hardware devices and the configuration confirms to the I/O requirements of SQL Server • The device drivers and other supporting software components of all devices in the I/O path are updated• Consider using a utility like SQL on the same drive as the databases that have reported the consistency errors. SQLI is a tool independent of the SQL Server Engine to test the integrity of I/O for the disk system. Note that SQL ships with SQL Server 2008 and does not require a separate download. • Check for any other errors reported by SQL Server such as Access Violations. These types of problems may lead to database corruption so be sure to resolve these errors first. • Ensure your databases are using the PAGE_VERIFY CHECKSUM option. If checksum errors are being reported, these are indicators that the consistency errors have occurred after SQL Server has written pages to disk so your disk system should be thoroughly checked. See How to Troubleshoot Msg 824 in SQL Server for more information about checksum errors. • Look for Msg 832 errors in the ERRORLOG. These are indicators that pages may be damaged while they are in cache before written to disk. See How to Troubleshoot Msg 832 in SQL Server for more information. • Try to restore a database backup you know that is "clean" (no errors from CHECKDB) and transaction log backups you know span the time when the error was encountered. If you can "replay" this problem by restoring a "clean" database backup and transaction logs then contact Microsoft Technical Support for assistance. • Data Purity errors can be a problem with the application inserting or updating invalid data into SQL Server tables. |
|
|
|
prett
Posting Yak Master
212 Posts |
Posted - 2014-05-08 : 04:21:56
|
| Hope this will help you:http://www.stellarinfo.com/sql-recovery.htm |
|
|
|
bakk
Starting Member
12 Posts |
Posted - 2014-05-28 : 06:22:49
|
| Did you execute the right DBCC CHECKDB statements? DBCC CHECKDB and DBCC DBREPAIR statements are inbuilt repair tool in MS SQL Server and if it doesn't work then the level of corruption is severe. But don't worry! its nothing like you can't recover it. Read this post to get the optimal solution.nalavadebela.wordpress.com/2014/04/05/how-to-repair-corrupt-mdf-file-of-microsoft-sql-server/ |
|
|
|
|
|
|
|
|
corruption issue