9001 Error
Contents |
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and error 9001 sql server policies of this site About Us Learn more about Stack Overflow the company
Error 9001 Tempdb
Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered unrecoverable error 9001 Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can irs error 9001 ask a question Anybody can answer The best answers are voted up and rise to the top Diagnosing Microsoft SQL Server error 9001: The log for the database is not available up vote 15 down vote favorite 2 Over the weekend a website I run stopped functioning, recording the following error in the Event Viewer each time a request is made to the
Fatal Error 9001
website: Event ID: 9001 The log for database 'database name' is not available. Check the event log for related error messages. Resolve any errors and restart the database. The website is hosted on a dedicated server, so I am able to RDP into the server and poke around. The LDF file for the database exists in the C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA folder, but attempting to do any work with the database from Management Studio results in a dialog box reporting the same error - 9001: The log for database is not available... This is the first time I've received this error, and I've been hosting this site (and others) on this dedicated web server for over two years now. It is my understanding that this error indicates a corrupt log file. I was able to get the website back online by Detaching the database and then restoring a backup from a couple days ago, but my concern is that this error is indicative of a more sinister problem, namely a hard drive failure. I emailed support at the web hosting company and this was t
additional information might be available elsewhere. Thank you for searching on this message; your search helps us identify those http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=SQL%20Server&ProdVer=2000.80.760.0&EvtID=9001&EvtSrc=MSSQLServer&LCID=1033 areas for which we need to provide more information. If the product or version you are looking for is not listed, you can use this search box to search TechNet, the Microsoft Knowledge Base, and TechNet Blogs for more information. Enter the product name, event source, and event ID. For example: Vista Application Error 1001.
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 http://dba.stackexchange.com/questions/34061/error-9001-severity-21-state-1-the-log-for-database-db-name-is-not-availab more about hiring developers or posting ads with us Database Administrators Questions Tags Users Badges 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/ Unanswered Ask Question _ Database Administrators Stack Exchange is a question and answer site for database professionals who wish 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 voted up and rise to the error 9001 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: error 9001 socket 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 932310 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 abou
Check the event log for related error messages. Resolve any errors and restart the database. | 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 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.
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 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. Create a free website or blog at WordPress.com. %d bloggers like t