June 3, 2013 at 12:26 pm
Production Database in Suspect Mode...
Luckily we switched the nodes and working on other but trying to find the root cause of it.
Here are the logs
Can any one help me with it.
05/30/2013 04:03:48,spid251,Unknown,The log for database 'XXXXXXX' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
05/30/2013 04:03:48,spid251,Unknown,Error: 9001<c/> Severity: 21<c/> State: 1.
05/30/2013 04:03:48,spid254,Unknown,The log for database 'XXXXXX' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
05/30/2013 04:03:48,spid254,Unknown,Error: 9001<c/> Severity: 21<c/> State: 1.
05/30/2013 04:03:48,spid244,Unknown,The log for database 'XXXXXXX' This not available. Check the event log for related error messages. Resolve any errors and restart the database.
05/30/2013 04:03:48,spid244,Unknown,Error: 9001<c/> Severity: 21<c/> State: 4.
05/30/2013 04:03:48,spid5s,Unknown,LogWriter: Operating system error 170(The requested resource is in use.) encountered.
05/30/2013 04:03:48,spid5s,Unknown,Error: 17053<c/> Severity: 16<c/> State: 1.
05/30/2013 04:03:48,spid5s,Unknown,Write error during log flush.
05/30/2013 04:03:48,spid5s,Unknown,LogWriter: Operating system error 170(The requested resource is in use.) encountered.
05/30/2013 04:03:48,spid5s,Unknown,Error: 17053<c/> Severity: 16<c/> State: 1.
05/30/2013 00:00:11,spid22s,Unknown,This instance of SQL Server has been using a process ID of 2508 since 5/29/2013 3:56:31 PM (local) 5/29/2013 7:56:31 PM (UTC). This is an informational message only; no user action is required.
June 3, 2013 at 1:02 pm
Looks like a connection issue between SQL Server & the drive that holds the log file. SQL server can not access the log file and it looks like the drive that holds the log file is corrupt.
June 4, 2013 at 5:12 am
The log for database 'XXXXXXX' is not available.
is a clear message of the problem, but it could have different root cause.
- the folder on disk (or disk itself) where the LOG file resides is not available
- the LOG file itself is not available or corrupt (or locked by another program like anti-virus)
- insufficient rights on the LOG folder/file
June 4, 2013 at 6:35 am
Can you confirm that you can access the drive with the transaction log is located?
You might be able to get to location of the log from this
select physical_name from sys.master_files
where DB_NAME(database_id) = 'XXXXXXX'
and type_desc = 'LOG'
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply