Ms Sql Server Error 9001
Contents |
up Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On Home » SQL Server 2008
Error 9001 Severity 21 State 4
» SQL Server 2008 Administration » Log not available error 9001 19 posts,Page the log for database is not available sql server 1 of 212»» Log not available error 9001 Rate Topic Display Mode Topic Options Author Message shaun.stuartshaun.stuart Posted Monday,
Error 9001 Severity 21 State 1 Tempdb
December 20, 2010 7:31 AM SSCommitted Group: General Forum Members Last Login: Friday, October 7, 2016 8:42 AM Points: 1,953, Visits: 837 Came in to work this morning to face a bunch fatal error 9001 occurred sql server of alerts for severity 21 errors."DESCRIPTION: The log for database 'SpotlightManagementFramework' is not available. Check the event log for related error messages. Resolve any errors and restart the database."Hmm.. The drive the log is on was available and logs for other DB were on it. Plenty of space left. Window Application event log showed no errors other than the one listed above. Windows System the log for database 'tempdb' is not available. check the event log for related error messages log showed no errors. I ran dbcc checkdb on the database and the only error reported was that the log was not available.I took the database offline, then brought it online again and all seems good now. DBCC Checkdb gives no errors. DBCC loginfo(0) gives info, so I'm assuming the log is available. Now just trying to figure out what happened.Took a closer look at the SQL error log and I see this:12/20/2010 02:30:01,spid20s,Unknown,The log for database 'SpotlightManagementFramework' is not available. Check the event log for related error messages. Resolve any errors and restart the database.12/20/2010 02:30:01,spid20s,Unknown,Error: 9001
log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn
Sql Autoclose
more about hiring developers or posting ads with us Database Administrators Questions Tags Users Badges Unanswered event id 9001 group policy Ask Question _ Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills
Msg 9001, Level 21, State 1, Line 1
and learn from others in the community. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the http://www.sqlservercentral.com/Forums/Topic1037190-1550-1.aspx top Error 9001, Severity: 21, State: 1 The log for database 'DB_NAME' is not available [closed] up vote 3 down vote favorite I have a SQL Server 2008 R2. I got a mail that the backup had failed, I opened the SQL log viewer and started browsing. And i found these two errors a bunch of times. error 1: Date 31-01-2013 13:20:30 Log SQL Server (Current - 01-02-2013 05:13:00) Source spid20s Message Error: 9001, Severity: 21, State: 1. http://dba.stackexchange.com/questions/34061/error-9001-severity-21-state-1-the-log-for-database-db-name-is-not-availab/53892 error 2: Date 31-01-2013 13:20:30 Log SQL Server (Current - 01-02-2013 05:13:00) Source spid20s Message The log for database 'DB_NAME' is not available. Check the event log for related error messages. Resolve any errors and restart the database. After a little googling, I had read a few times that the errors indicated that the DB or log file maybe corrupt. I read that I could confirm it, by running a DBCC CHECKDB 'DB_NAME', so i did, and here are the last to lines of the output: CHECKDB found 0 allocation errors and 0 consistency errors in database 'DB_NAME'. DBCC execution completed. If DBCC printed error messages, contact your system administrator. The output shows that the DB isn't corrupt. But can the log file still be corrupt? I also read that one solution might be run something called "Emergency Mode Repair" to fix the corrupt files. But some users did NOT recommend it. Could another solution be to delete the log file completely and then create a new?. sql sql-server-2008-r2 backup logs share|improve this question asked Feb 4 '13 at 13:20 Arviddk 933310 closed as off-topic by Martin Smith, RolandoMySQLDBA, Marian, Michael - sqlbot, Erwin Brandstetter Dec 26 '13 at 16:59 This question does not appear to belong here. Either it's not database-related or it otherwise conflicts with the scope of our site. See What topics can I ask about he
Check the event log for related error messages. Resolve any errors and restart the database. https://dacosta9.wordpress.com/2014/06/26/sql-server-error-9001-severity-21-state-5-the-log-for-database-database_name-is-not-available-check-the-event-log-for-related-error-messages-resolve-any-errors-and-restart-the-database-e/ | Error: 9001, Severity: 21, State: 5. | Matched: %Error%, Posted on June 26, 2014 by john.dacosta Upon being greeted with the following logs, I started http://stackoverflow.com/questions/13505881/website-fatal-error-9001 investigating the issue. I found the issue to be caused by the database being closed, and not any major underlying disk issue. Check if your error 9001 database has auto_close enabled.
select @@SERVERNAME AS server_name,getutcdate() as report_date_utc,name as database_name, is_auto_close_on , state_desc, user_access_desc
from sys.databases
where is_auto_close_on = 1
order by name asc
If autoclose is on, switch this database to no longer use auto_close. Before making any changes, check the error 9001 severity integrity of the database. If there are no errors generated by this command, then move on to changing the auto_close option.
dbcc checkdb('database_name')
alter database [database_name] set offline with rollback immediate;
go
alter database [database_name] set online;
alter database [database_name] set AUTO_CLOSE OFF;
Like this:Like Loading... Related Posted in administration, database, sqlTagged AUTO_CLOSE error: 9001 SQL SERVER Post navigation ←NoSQL company Basho loses CEO and CTOInstalling LogMeIn Hamachi for Linux (Beta) command line version on Ubuntu 16.04 LTS→ Leave a Reply Cancel reply Enter your comment here... Fill in your details below or click an icon to log in: Email (required) (Address never made public) Name (required) Website You are commenting using your WordPress.com account. (LogOut/Change) You are commenting using your Twitter account. (LogOut/Change) You are commenting using your Facebook account. (LogOut/Change) You are commenting using your Google+ account. (LogOut/Change) Cancel Connecting to %s No
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Website fatal error 9001 up vote 2 down vote favorite 1 I know this question has been asked here before, but none of the suggestions have worked for me. I have an ASP.NET MVC (v. 3) website on a shared server. The website was working fine for a few weeks now, until I started getting a Fatal Error 9001 error straight after login. Because this is a shared server, there are only very limited things I can do with the database (and I don't know that much about databases anyway). The help desk insist that there is nothing wrong with their server. I got various suggestions from them: Upgrading to the business plan because I am out of space Even though the mdb file is small, the ldb can grow very quickly. The ldb file is probably taking up all the space. I have 100MB available, the database size is 16.5MB. Can the ldb file take up the remaining space? There is something wrong with my SQL queries and I should check the website. I'm using EF with linq to sql. Everything was working fine until now... Can there be something that goes wrong in the queries that causes this sort of error? There is nothing wrong to be seen in the db logs, so this error cannot possibly have happened. I should log it next time it happens and contact again. I found some posts on SO suggesting that restoring a DB backup can get rid of the issue. I do not have a recent backup, and can't take a new one because of a fatal error 9001 occurring. What el