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 12»»

The log for database is not available; Database was shutdown due to error 9001 in routine 'XdesRMFull::Commit'. Expand / Collapse
Author
Message
Posted Wednesday, May 4, 2011 2:39 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, August 22, 2014 12:45 PM
Points: 161, Visits: 665
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 ) 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.
Post #1103497
Posted Wednesday, May 4, 2011 2:44 PM


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 @ 2:38 AM
Points: 42,832, Visits: 35,963
Looks like a hardware issue. Server is losing contact with the underlying drives.

SAN storage?



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 #1103500
Posted Wednesday, May 4, 2011 2:47 PM


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 @ 2:38 AM
Points: 42,832, Visits: 35,963
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 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 #1103501
Posted Wednesday, May 4, 2011 2:54 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, August 22, 2014 12:45 PM
Points: 161, Visits: 665
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.
Post #1103508
Posted Wednesday, May 4, 2011 3:02 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, August 22, 2014 12:45 PM
Points: 161, Visits: 665
Just stumbled into a VERY similar thread on this site:
http://www.sqlservercentral.com/Forums/Topic355924-5-1.aspx#bm482958
Post #1103512
Posted Wednesday, May 4, 2011 3:19 PM


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 @ 2:38 AM
Points: 42,832, Visits: 35,963
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 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 #1103520
Posted Wednesday, June 1, 2011 10:56 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, July 11, 2014 11:42 AM
Points: 18, Visits: 105
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
Post #1118193
Posted Wednesday, June 1, 2011 11:53 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, August 22, 2014 12:45 PM
Points: 161, Visits: 665
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!
Post #1118259
Posted Monday, January 28, 2013 10:03 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Tuesday, May 20, 2014 12:19 AM
Points: 19, Visits: 334
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.
Post #1412748
Posted Tuesday, March 19, 2013 1:53 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, March 19, 2013 1:51 AM
Points: 1, Visits: 0
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.
Post #1432514
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse