August 1, 2011 at 8:53 pm
The log for database 'PICAPROD' is not available in SQL Server 2005.
it is occurring monthly twice or thrise. But during that time transactional backup job is running properly.
Resolve any errors and restart the database.
2011-08-01 05:20:08.66 spid53 Error: 9001, Severity: 21, State: 1.
2011-08-01 05:20:08.66 spid53 The log for database 'PICAPROD' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
If anyone knows how to resolve this issue. I checked with system admin they said that disk side no issue. I checked dbcc checkdb command also. no error in database side. Please hepl me asap.
Thanks
S.Jay
August 2, 2011 at 12:15 am
Try detaching and then attaching the database.
Try the steps posted here
http://www.sqlservice.se/allmant/dont-panic-the-log-for-database-name_here-is-not-available/
--------------------------------------------------------------------------------------------------
I am just an another naive wannabe DBA trying to learn SQL Server
August 2, 2011 at 1:53 am
BEFORE going for any harsh action I would investigate the issue.
What else is failing, causing issues to that sqlinstance at that time ?
(IO subsystem notifications, other db having alike issues, ....)
if - like you stated - that occurs a couple of times in a month, I would urge you to monitor your disks or to launch a checkdisk, dbcc checkdb, to rule out your disks being the cause, or just be able to fix it.
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
August 2, 2011 at 3:04 am
Sachin Nandanwar (8/2/2011)
Try detaching and then attaching the database.
No. Please no. Worst thing possible.
Unless by some miraculous chance the database was cleanly shut it will not reattach. You should never detach a database with any form of log problem.
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
August 2, 2011 at 3:06 am
subbaraju.jay (8/1/2011)
If anyone knows how to resolve this issue. I checked with system admin they said that disk side no issue. I checked dbcc checkdb command also. no error in database side. Please hepl me asap.
Put some alerts in so that you know the second it happens. Check that the drive the log file is on is accessible, check the windows event log for any disk-related errors.
Common cause of this is disks 'disappearing' from the server for a few seconds (usually config or connectivity problems), SQL notices that its file is missing and logs that kind of error.
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
August 2, 2011 at 3:18 am
GilaMonster (8/2/2011)
Sachin Nandanwar (8/2/2011)
Try detaching and then attaching the database.No. Please no. Worst thing possible.
Unless by some miraculous chance the database was cleanly shut it will not reattach. You should never detach a database with any form of log problem.
OK.Point duly noted...:-)
--------------------------------------------------------------------------------------------------
I am just an another naive wannabe DBA trying to learn SQL Server
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply