Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


The log for database "databasename" is not available.


The log for database "databasename" is not available.

Author
Message
diogenes1331
diogenes1331
SSC Journeyman
SSC Journeyman (98 reputation)SSC Journeyman (98 reputation)SSC Journeyman (98 reputation)SSC Journeyman (98 reputation)SSC Journeyman (98 reputation)SSC Journeyman (98 reputation)SSC Journeyman (98 reputation)SSC Journeyman (98 reputation)

Group: General Forum Members
Points: 98 Visits: 54
"The log for database MYDB is not avaiable" .. when writing an UPDATE statement to a table.

We first observed this problem today in a database but I found out that in addition we have had an error in the application log

"Backup Request: WaitForIOCompletion: Write failure on backup device "Y:\MyDB_Log.ld.
Operating Syste Rror 1117: The request could not be perfoirmed because of an IO error".

I can perfectly see the LUN where the transaction log is and I can get to that folder an d connect to the database to do SELECTS or even see the properties from Enterprise Manager, but we cannot do anything that involves the transaction log.



SQLZ
SQLZ
SSC Eights!
SSC Eights! (874 reputation)SSC Eights! (874 reputation)SSC Eights! (874 reputation)SSC Eights! (874 reputation)SSC Eights! (874 reputation)SSC Eights! (874 reputation)SSC Eights! (874 reputation)SSC Eights! (874 reputation)

Group: General Forum Members
Points: 874 Visits: 940

Hi,

It sure sounds like there is a potential problem with the hardware.  Just because you can see the lun and get to the folder doesn't mean there's a problem.  There could be a write problem that isn't affecting reads for example.

Check the SQL Server error log.  If you see any 823 errors refer to the following articles.

http://support.microsoft.com/default.aspx?kbid=828339

and

http://support.microsoft.com/kb/826433/

I'd always get the hardware vendor to check for hardware failures.  The fact that the error message indicates that there is an IO error indicates that this is where the problem most likely lies.

Good luck.



Karl
source control for SQL Server
Marcello Bruno
Marcello Bruno
Forum Newbie
Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)

Group: General Forum Members
Points: 1 Visits: 1
I had the "The Log for Database 'X' is not available" error as well. I detached and reattached the database, and problem solved.
LaPointeMW
LaPointeMW
Forum Newbie
Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)

Group: General Forum Members
Points: 1 Visits: 5
Same problem here. Reattaching worked for me, thanks.
Ed.Watson aka SQLGator
Ed.Watson aka SQLGator
Mr or Mrs. 500
Mr or Mrs. 500 (545 reputation)Mr or Mrs. 500 (545 reputation)Mr or Mrs. 500 (545 reputation)Mr or Mrs. 500 (545 reputation)Mr or Mrs. 500 (545 reputation)Mr or Mrs. 500 (545 reputation)Mr or Mrs. 500 (545 reputation)Mr or Mrs. 500 (545 reputation)

Group: General Forum Members
Points: 545 Visits: 264
I could not detach as it gave the same error, but I took it offline and then back online and it was working fine.

Ed Watson aka SQLGator
Microsoft SQL Server MVP

Follow me on Twitter!
Go Gators!
Greg A Goss
Greg  A Goss
Old Hand
Old Hand (321 reputation)Old Hand (321 reputation)Old Hand (321 reputation)Old Hand (321 reputation)Old Hand (321 reputation)Old Hand (321 reputation)Old Hand (321 reputation)Old Hand (321 reputation)

Group: General Forum Members
Points: 321 Visits: 402
I ran into this issue today and confirmed that the detach/reattach or offline/online switch works for current SQL versions as well (SQL 2008 R2 in this case).
tt-615680
tt-615680
Old Hand
Old Hand (334 reputation)Old Hand (334 reputation)Old Hand (334 reputation)Old Hand (334 reputation)Old Hand (334 reputation)Old Hand (334 reputation)Old Hand (334 reputation)Old Hand (334 reputation)

Group: General Forum Members
Points: 334 Visits: 1201
Taking the database "offline then "online" again seems to fix the issue.
johnwalker10
johnwalker10
SSC Veteran
SSC Veteran (246 reputation)SSC Veteran (246 reputation)SSC Veteran (246 reputation)SSC Veteran (246 reputation)SSC Veteran (246 reputation)SSC Veteran (246 reputation)SSC Veteran (246 reputation)SSC Veteran (246 reputation)

Group: General Forum Members
Points: 246 Visits: 282
•   Take the database offline.
•   Bring it back online.
•   Run DBCC checkdb to make sure everything is good.
•   Set Auto Close = False.
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