<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQL Server 7,2000
»
Data Corruption
»
Faultfinding possible I/O issues
24 posts, Page 1 of 3
1
2
3
»
»»
Faultfinding possible I/O issues
Rate Topic
Display Mode
Topic Options
Author
Message
jblovesthegym
jblovesthegym
Posted Thursday, April 12, 2012 5:51 AM
Valued Member
Group: General Forum Members
Last Login: Wednesday, June 12, 2013 5:52 AM
Points: 52,
Visits: 214
Hi all,
Over the last few weeks 3 of our secondary (log-shipped) DB's have been marked 'Suspect', requiring drop+restore. I've been advised to check the I/O and try to faultfind.
What practices/native tools exist for SS2K to get started on the investigation? BTW, if the initial diagnosis involves creating non-temp tables/objects, I would rather avoid this as even making slight changes involves having to raise an RFC.
Also, would you recommend checking I/O on both Primary + Secondary servers?
Post #1282287
GilaMonster
GilaMonster
Posted Thursday, April 12, 2012 6:19 AM
SSC-Dedicated
Group: General Forum Members
Last Login: Today @ 11:41 AM
Points: 38,089,
Visits: 30,383
If the secondary has gone suspect and the primary is fine, then it's the secondary's IO subsystem that's the problem.
Start with the windows error log, any RAID logs, SAN logs. If you can, stop SQL on there and run SQLIOSim (I wouldn't run it with SQL running, too much load)
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 #1282301
jblovesthegym
jblovesthegym
Posted Thursday, April 12, 2012 10:40 AM
Valued Member
Group: General Forum Members
Last Login: Wednesday, June 12, 2013 5:52 AM
Points: 52,
Visits: 214
Hi Gail,
I've done some Perfmon analysis during the 100 seconds after which log shipping runs (every 15mins on the hour), only the logical disk today (physical tomorrow) but the results for the W: drive to which the logs are copied (and restored from) are as follows, I presume the values are milliseconds:
Avg Disk Bytes/Read:
- Avg = 18,199
- Max = 26021
Avg Disk Bytes/Transfer:
- Avg = 40,651
- Max = 65,536
Avg Disk Bytes/Write:
- Avg = 53,696
- Max = 65,536
Post #1282581
GilaMonster
GilaMonster
Posted Thursday, April 12, 2012 11:43 AM
SSC-Dedicated
Group: General Forum Members
Last Login: Today @ 11:41 AM
Points: 38,089,
Visits: 30,383
Perfmon is not the place to look, you don't have disk performance problems, you have disk stability problems.
And no, the figure for bytes/write is not milliseconds. It's bytes. It shows the average number of bytes written per second.
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 #1282638
jblovesthegym
jblovesthegym
Posted Friday, April 13, 2012 3:24 AM
Valued Member
Group: General Forum Members
Last Login: Wednesday, June 12, 2013 5:52 AM
Points: 52,
Visits: 214
GilaMonster (4/12/2012)
Perfmon is not the place to look, you don't have disk performance problems, you have disk stability problems.
Agreed, but I don't have a lot of immediate avenues of investigation left, so I was reaching. The event log (app/systeM) showed nothing suspicious around or immediately before the initial failure. We don't have the SAN/RAID guys in until Monday, and stopping the SQL service, even temporarily on Secondary, will require a bunch of form-filling. Ok, actually swapping the disk out is not a lengthy procedure, but I need to make a business case for the switch, and thus need proof the disk is not quite stable.
Post #1282984
GilaMonster
GilaMonster
Posted Friday, April 13, 2012 3:26 AM
SSC-Dedicated
Group: General Forum Members
Last Login: Today @ 11:41 AM
Points: 38,089,
Visits: 30,383
Nothing in any of the error logs?
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 #1282985
jblovesthegym
jblovesthegym
Posted Friday, April 13, 2012 4:12 AM
Valued Member
Group: General Forum Members
Last Login: Wednesday, June 12, 2013 5:52 AM
Points: 52,
Visits: 214
Hunted around but couldn't make much sense of it...
Error: 5180, Severity: 22, State: 1
Could not open FCB for invalid file ID 0 in database 'XXXXXXXXXXXXX'
Post #1283000
GilaMonster
GilaMonster
Posted Friday, April 13, 2012 4:14 AM
SSC-Dedicated
Group: General Forum Members
Last Login: Today @ 11:41 AM
Points: 38,089,
Visits: 30,383
What about the windows event logs?
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 #1283001
jblovesthegym
jblovesthegym
Posted Friday, April 13, 2012 4:30 AM
Valued Member
Group: General Forum Members
Last Login: Wednesday, June 12, 2013 5:52 AM
Points: 52,
Visits: 214
GilaMonster (4/13/2012)
What about the windows event logs?
Zip. The app log filled up with infomercials and doesn't stretch back that far. However I DID check it on the morning in question (the 11th) and found nothing. The only other 'critical' error was in te System log, a virtual disk service error, about 8 hours before and after the restore job failed:
"Unexpected failure. Error code: 2@0200001D"
Post #1283006
jblovesthegym
jblovesthegym
Posted Tuesday, April 24, 2012 10:47 AM
Valued Member
Group: General Forum Members
Last Login: Wednesday, June 12, 2013 5:52 AM
Points: 52,
Visits: 214
Any further thoughts, anyone?
Post #1289191
« Prev Topic
|
Next Topic »
24 posts, Page 1 of 3
1
2
3
»
»»
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
