SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


The log for database is not available; Database was shutdown due to error 9001 in routine...


The log for database is not available; Database was shutdown due to error 9001 in routine 'XdesRMFull::Commit'.

Author
Message
SkyBox
SkyBox
SSC Eights!
SSC Eights! (878 reputation)SSC Eights! (878 reputation)SSC Eights! (878 reputation)SSC Eights! (878 reputation)SSC Eights! (878 reputation)SSC Eights! (878 reputation)SSC Eights! (878 reputation)SSC Eights! (878 reputation)

Group: General Forum Members
Points: 878 Visits: 737
Testing and Production db's have lost connection to the translog 2 days in a row now. Today, my prod db was marked suspect after the issue - SCARY. The other db's did not lose connection. Possibly because there was no activity at that moment.

No errors in SQL log, only windows. Server Resources were not necessarily be hammered. I will be scouring the web, but wanted to reach out to all of you as well. See info and errors below.


Plenty of available drive space for Log, db, and tempdb partitions. 144gb RAM
SQL Server 2008 SP1; Enterprise (64-bit)
OS: Win Server 2008 R2 Enterprise

Win app logs:
error1- LogWriter: Operating system error 21(The device is not ready.) encountered.
error2 - The log for database (testing) is not available. Check the event log for related error messages. Resolve any errors and restart the database.

info mess3- Database was shutdown due to error 9001 in routine 'XdesRMFull::Commit'. Restart for non-snapshot databases will be attempted after all connections to the database are aborted.

2 seconds later prod db goes down:
error4-
The log for database is not available. Check the event log for related error messages. Resolve any errors and restart the database.

error5 - During undoing of a logged operation in database, an error occurred at log record ID (86400:39070:17). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.

error6 - fcb::close-flush: Operating system error (null) encountered.

error7 - An error occurred during recovery, preventing the database (PRODUCTION :w00tSmile from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.

info mess8 -CHECKDB for database finished without errors on 2011-03-14 12:12:41.503 (local time). This is an informational message only; no user action is required.
GilaMonster
GilaMonster
SSC Guru
SSC Guru (232K reputation)SSC Guru (232K reputation)SSC Guru (232K reputation)SSC Guru (232K reputation)SSC Guru (232K reputation)SSC Guru (232K reputation)SSC Guru (232K reputation)SSC Guru (232K reputation)

Group: General Forum Members
Points: 232214 Visits: 46356
Looks like a hardware issue. Server is losing contact with the underlying drives.

SAN storage?

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
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


GilaMonster
GilaMonster
SSC Guru
SSC Guru (232K reputation)SSC Guru (232K reputation)SSC Guru (232K reputation)SSC Guru (232K reputation)SSC Guru (232K reputation)SSC Guru (232K reputation)SSC Guru (232K reputation)SSC Guru (232K reputation)

Group: General Forum Members
Points: 232214 Visits: 46356
p.s. If I were you, I'd be doing checkDB more often than once in 2 months.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
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


SkyBox
SkyBox
SSC Eights!
SSC Eights! (878 reputation)SSC Eights! (878 reputation)SSC Eights! (878 reputation)SSC Eights! (878 reputation)SSC Eights! (878 reputation)SSC Eights! (878 reputation)SSC Eights! (878 reputation)SSC Eights! (878 reputation)

Group: General Forum Members
Points: 878 Visits: 737
Yes, SAN storage. Just found out the tempdb partition and translog partition share the same physical drive. I can move the tempdb file to the larger database drive immediately - well late tonight.

Could this disk contention be causing the hardware error?

It's been running this way for a while now, but being hit harder lately. FYI - I will schedule CHECKDB's weekly, maybe daily now.
SkyBox
SkyBox
SSC Eights!
SSC Eights! (878 reputation)SSC Eights! (878 reputation)SSC Eights! (878 reputation)SSC Eights! (878 reputation)SSC Eights! (878 reputation)SSC Eights! (878 reputation)SSC Eights! (878 reputation)SSC Eights! (878 reputation)

Group: General Forum Members
Points: 878 Visits: 737
Just stumbled into a VERY similar thread on this site:
http://www.sqlservercentral.com/Forums/Topic355924-5-1.aspx#bm482958
GilaMonster
GilaMonster
SSC Guru
SSC Guru (232K reputation)SSC Guru (232K reputation)SSC Guru (232K reputation)SSC Guru (232K reputation)SSC Guru (232K reputation)SSC Guru (232K reputation)SSC Guru (232K reputation)SSC Guru (232K reputation)

Group: General Forum Members
Points: 232214 Visits: 46356
I wouldn't say disk contention (but I'm not a SAN expert). Check the physical connections, switch, anything between the server and SAN. From the Windows error log, the OS can't see the disk at points.

Moving the DB will help, but you still need to find the root cause.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
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


Greg Swanson
Greg Swanson
Valued Member
Valued Member (62 reputation)Valued Member (62 reputation)Valued Member (62 reputation)Valued Member (62 reputation)Valued Member (62 reputation)Valued Member (62 reputation)Valued Member (62 reputation)Valued Member (62 reputation)

Group: General Forum Members
Points: 62 Visits: 123
FYI: There is a VMWare issue that is associated with getting this error having to do with using the Paravirtual SCSI drivers. See the following KB: [url=http://support.microsoft.com/kb/2519834][/url]

Greg
SkyBox
SkyBox
SSC Eights!
SSC Eights! (878 reputation)SSC Eights! (878 reputation)SSC Eights! (878 reputation)SSC Eights! (878 reputation)SSC Eights! (878 reputation)SSC Eights! (878 reputation)SSC Eights! (878 reputation)SSC Eights! (878 reputation)

Group: General Forum Members
Points: 878 Visits: 737
Greg Swanson (6/1/2011)
FYI: There is a VMWare issue that is associated with getting this error having to do with using the Paravirtual SCSI drivers. See the following KB: [url=http://support.microsoft.com/kb/2519834][/url]

Greg


Not running WMWare on that system, but thanks for the info/update!
Terence Keys
Terence Keys
SSC Veteran
SSC Veteran (207 reputation)SSC Veteran (207 reputation)SSC Veteran (207 reputation)SSC Veteran (207 reputation)SSC Veteran (207 reputation)SSC Veteran (207 reputation)SSC Veteran (207 reputation)SSC Veteran (207 reputation)

Group: General Forum Members
Points: 207 Visits: 573
Hi
I know this is an old post but I had the same problem and we run a SAN an VMware so I thought it's related to that but then I found another post telling me to bring the db offline and online again and that actually worked. Very simple in the end.
er.neelkamal
er.neelkamal
Forum Newbie
Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)

Group: General Forum Members
Points: 9 Visits: 1
Restart the sql service, and it will start working.
The same thing happened for me also. and i did the same..
Now its working fine.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search