Error 9001 Severity 21
Contents |
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 error 9001 severity 21 state 4 company Business Learn more about hiring developers or posting ads with us Database Administrators Questions irs error 9001 Tags Users Badges Unanswered Ask Question _ Database Administrators Stack Exchange is a question and answer site for database professionals who wish fatal error 9001 to improve their database skills 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 error 9001 socket exception recv error server voted up and rise to the 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
Error 9001 Socket Exception Recv_timeout Server
05:13:00) Source spid20s Message Error: 9001, Severity: 21, State: 1. 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
SQL Server 2014 Express resources Windows Server 2012 resources Programs MSDN subscriptions Overview Benefits Administrators Students Microsoft Imagine Microsoft Student Partners ISV Startups TechRewards Events Community Magazine Forums Blogs Channel 9 Documentation APIs and reference Dev centers Retired content
Xfinity Error 9001
Samples We’re sorry. The content you requested has been removed. You’ll be auto the log for database is not available. check the event log for related error messages redirected in 1 second. Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From error 9001 severity 21 state 1 tempdb My Forums Answered by: Error: 9001, Severity: 21, State: 1 error and Error: 9001, Severity: 21, State: 5 SQL Server > SQL Server Express Question 0 Sign in to vote Hi all experts, I http://dba.stackexchange.com/questions/34061/error-9001-severity-21-state-1-the-log-for-database-db-name-is-not-availab am facing one problem in sql express, "The log for database 'x' is not available", I also found solution to set AUTO CLOSE=OFF. But I want to know more about this. Is this error is related with deadlock?? (I'm seeing error just before above error like "was deadlock on locked resources with another process and has been chosen as the deadlock victim. Rerun the transaction") Please help!!!!! https://social.msdn.microsoft.com/Forums/en-US/7e3ef5c9-dc92-495e-ba58-116563cf44eb/error-9001-severity-21-state-1-error-and-error-9001-severity-21-state-5?forum=sqlexpress Any help appreciated. Thanks in advance Saturday, October 31, 2015 10:25 AM Reply | Quote Answers 1 Sign in to vote Hi chaitanya, Thank you for posting in MSDN forum. Issue is not related to deadlock but please verify your event log for more information. Work around, Please set AUTO CLOSE=OFF and put database offline and online. It should solve your problem. Please have a look into very similar thread and some useful article for help, http://www.sqlservercentral.com/Forums/Topic1037190-1550-1.aspx SQL Server Error: 9001, Severity: 21, State: 5 – The log for database `database_name` is not available. Error: 9001, Severity: 21, State: 1 | The log for database ‘tempdb’ is not availableThanks, If my reply is helpful please mark as answer or vote as helpful. Proposed as answer by Lydia ZhangMicrosoft contingent staff, Moderator Monday, November 02, 2015 7:14 AM Marked as answer by chaitanya dhole Monday, November 02, 2015 8:02 AM Saturday, October 31, 2015 10:54 AM Reply | Quote 1 Sign in to vote database had 'autoclose' option enabled and while trying to open that database it messed up with some system process and got killed. not sure what all happened there. just disabled this option, took the database offline
Check the event log for related error messages. Resolve any errors and restart the database. | Error: 9001, 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/ Severity: 21, State: 5. | Matched: %Error%, Posted on June 26, 2014 by john.dacosta Upon being greeted with the following logs, I started 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 database has auto_close enabled. error 9001
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 integrity of the database. If there are error 9001 severity 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 Notify me of new comments via email. Blog at WordPress.com. %d bloggers like this: