Error 9001 Severity 21 State 4 Sql Server
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 error 9001 severity 21 state 1 the workings and policies of this site About Us Learn more about
Error 9001 Severity 21 State 5
Stack Overflow the company Business Learn more about hiring developers or posting ads with us Database Administrators Questions
The Log For Database Tempdb Is Not Available Error 9001
Tags Users Badges 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
The Log For Database Is Not Available. Check The Event Log For Related Error Messages
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 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 error 9001 severity 21 state 1 tempdb 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. 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
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 Samples We’re sorry. The content you requested has the log for database is not available sql server been removed. You’ll be auto redirected in 1 second. Ask a question Quick access Forums sql fatal error 9001 home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Error: 9001, Severity: 21, State: 1 error and sql autoclose Error: 9001, Severity: 21, State: 5 SQL Server > SQL Server Express Question 0 Sign in to vote Hi all experts, I am facing one problem in sql express, "The log for database 'x' is not available", I http://dba.stackexchange.com/questions/34061/error-9001-severity-21-state-1-the-log-for-database-db-name-is-not-availab 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!!!!! Any help appreciated. Thanks in advance Saturday, October 31, 2015 10:25 AM Reply | Quote Answers 1 Sign in to vote Hi chaitanya, Thank 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 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 and back online and it fixed the issue.Please click "Mark As Answer" if my post helped. Marked as answer by chaitanya dhole Monday, November 02, 2015 8:02 AM Saturday, October 31, 2015 11:39 AM Reply | Quote All replies 1 Sign in to vote select * from s
BIDS Helper (1) BitBucket Server (3) BPOTW (81) By Example (19) Central Management Server (8) CHECKDB (7) Code (1) Codecademy (1) CodePlex (1) Collations (1) Configuration (3) https://sqlnotesfromtheunderground.wordpress.com/2015/04/22/error-9001-severity-21-state-1-the-log-for-database-xxx-is-not-available/ Curah (7) Daily Dashboard (5) Data Quality Services (1) Database Design Series (2) http://serverfault.com/questions/238394/diagnosing-microsoft-sql-server-error-9001-the-log-for-the-database-is-not-avai/238398 Database Lifecycle Management (DLM) (3) DBA Gameification (2) DBCC (1) DHCP (1) Disaster Recovery (2) Download (11) Enterprise Policy Management Framework (8) Error Log (3) Event Viewer (1) Exams (2) Excel (11) Extended Events (2) Extended Property (1) Frameworks (2) GIT (2) GitHub (3) GPO (1) High Availability (1) HTML / CSS (1) error 9001 Import Export Wizard (1) Indexes (1) Installs and Patching (5) Instance Maintenance (2) Instant File Initialization (2) Kerberos (3) Least Privilage (5) Linked Server (1) Log Shipping (2) MAPT (1) Marked Transacion (1) MDW (1) Monitoring (1) MSDB (3) Outlook (4) Pester (2) Podcasts (1) Policy Based Management (9) PowerShell (53) PowerShell Desired State Configuration (DSC) (1) Profiler (2) PsExec (1) PSInfo (1) RedGate (1) Replication error 9001 severity (4) Roles (1) Scheduled Task (1) Schema (1) Script (2) Security (9) Server Side Trace (2) Service Broker (1) Severity (1) SharePoint (4) SharePoint Designer 2013 (1) SharePoint Online (1) shrinkfile (1) Source Control (1) sp_attach_single_file_db (1) sp_help_revlogin (1) SQL Agent (10) SQL Community (6) SQL Events (2) SQL Nexus (1) SQL Server (19) SQL Server 2005 (1) SQL Server Alerts (1) SQL Server Upgrade (1) SQL Server Version (4) SQLBits (1) sqlcmd (2) sqlps (2) SQLPX (1) SQLSaturday (1) sqlserverbuilds.blogspot.co.uk (4) SSDT-BI (2) SSIS (8) SSIS Reporting Pack (1) SSMS (10) SSRS (13) Suspect Mode (1) SysInternals (2) T-SQL (23) Table Variables (1) Team Foundation Server (1) Temp Tables (1) TempDB (2) Tips and Tricks (71) Transactional Replication (3) Transparent Data Encryption (1) Troubleshooting (10) Troubleshooting Tools (1) Undocumented SQL Stored Procedures (1) Unit Test (2) Users (1) Using Excel VBA to Export SQL Data Series (3) VBA (3) Visual Studio (3) Windows OS (3) XML (2) xp_cmdshell (3) Year in Review (2) Error 9001, Severity 21, State 1 "The log for database "XXX" is notavailable Posted by staggerlee011 on April 22, 2015 in Severity, Troubleshooting | Leave a comment Ran into an interesting one
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 more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered 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 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 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 their reply: There doesn't appear to be any other indications of the cause in the Event Log, so it's possible that the log was corrupted. Currently the memory's resources is at 87%, which also may have an impact but is unlikely. Can the log just "become corrupted?" My question: What are the next steps I should take to diagnose this problem? How can I determine if this is, indeed, a hardware problem? And if it is, are there any options beyond replacing the disk? Thanks sql-server-2008 share|improve this question asked Feb 21 '11 at 23:18 Scott Mitchell 2361310 add a comment| 6 Answers 6 active oldest votes up vote 13 down vote We