Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 1234»»»

Need help--very urgent.. Expand / Collapse
Author
Message
Posted Monday, May 11, 2009 5:27 PM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Wednesday, October 15, 2014 10:58 AM
Points: 334, Visits: 392
Hi All,

Here's issue. I am not able to backup one of our production database. This is the error it gives...

BackupIoRequest::WaitForIoCompletion: read failure on backup device 'E:\Database File\abc.mdf'. Operating system error 23(Data error (cyclic redundancy check).).

What can I do? This is an urgent production issue....Please let us know your view asap....
Post #714637
Posted Monday, May 11, 2009 10:05 PM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Tuesday, September 23, 2014 2:53 AM
Points: 1,101, Visits: 5,290
[quote]RPSql (5/11/2009)
read failure on backup device 'E:\Database File\abc.mdf'. Operating system error 23(Data error (cyclic redundancy check).).
quote]

Looks like .MDF file is currupted. Run DBCC CHECKDB.
Post #714697
Posted Monday, May 11, 2009 10:56 PM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Monday, November 3, 2014 2:42 PM
Points: 1,683, Visits: 1,798
I would agree that this points to a physical disk problem on your server. Your only recourse may be to recover from your previous backup at this point. Check your SQL Server Error Log for 824 and 825 errors in the log. Run drive diagnostics and then CHECKDB to find the extent of the damage.

Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs
Post #714717
Posted Tuesday, May 12, 2009 1:36 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 8:31 AM
Points: 40,456, Visits: 36,912
Please run the following and post all the results here.
DBCC CHECKDB (< Database Name > ) WITH NO_INFOMSGS, ALL_ERRORMSGS

Take a look at this article. http://www.sqlservercentral.com/articles/65804/



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #714761
Posted Tuesday, May 12, 2009 7:26 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Wednesday, October 15, 2014 10:58 AM
Points: 334, Visits: 392
The Database size is 320 GB. I have started to run DBCC Checkdb on that database yesterday. It is running since 20 hours....Any idea why it is taking so long and why it is not completed yet?

In activity monitor it is showing Wait type FCB_REPLICA_WRITE. What can I do now?????

Please answer as it is a production issue and our application is down currently.

Thanks in advance.
Post #715009
Posted Tuesday, May 12, 2009 7:33 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Monday, November 3, 2014 2:42 PM
Points: 1,683, Visits: 1,798
Unless you are normally running CHECKDB (a recommended practice to catch these problems early on and reduce downtime/risk of data loss) and can look at the historical runs for how long it takes to run, there isn't a whole lot that you can do except wait it out. If you stop it, you won't get the information that you need to help resolve the problems.

Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs
Post #715025
Posted Tuesday, May 12, 2009 7:37 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Wednesday, October 15, 2014 10:58 AM
Points: 334, Visits: 392
Thanks for your reply. I was littlebit worried as this database is not much large, but it's already a day since I am running this process...It's really taking so long....The thread in activity monitor is suspended and wait type is 'FCB_REPLICA_WRITE'.

Is this normal?
Post #715033
Posted Tuesday, May 12, 2009 7:41 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Monday, November 3, 2014 2:42 PM
Points: 1,683, Visits: 1,798
Per the Book Online, that wait type signals the following:

Occurs when the pushing or pulling of a page to a snapshot (or a temporary snapshot created by DBCC) sparse file is synchronized.

http://msdn.microsoft.com/en-us/library/ms179984.aspx


Based on that I'd say yes it is normal.


Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs
Post #715044
Posted Tuesday, May 12, 2009 7:47 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 8:31 AM
Points: 40,456, Visits: 36,912
RPSql (5/12/2009)
It is running since 20 hours....Any idea why it is taking so long and why it is not completed yet?

Maybe because there is corruption.

The checkDB algorithms are written in such a way that they can tell quickly if there is corruption or not, but if there is, then SQL has to go back and do extra detailed searches. it's called a 'deep-dive' and it can make the CheckDB time go up massively.

Wait until it's finished. To tell what's wrong we need the results. If you stop it now you're just going to have to run it to completion later.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #715055
Posted Tuesday, May 12, 2009 7:49 AM


Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: Monday, June 1, 2009 6:06 AM
Points: 518, Visits: 354
The file might be a corrupted one

+++BLADE+++
Post #715059
« Prev Topic | Next Topic »

Add to briefcase 1234»»»

Permissions Expand / Collapse