Quantcast
Channel: SQLServerCentral » SQL Server 2014 » Administration - SQL Server 2014 » Latest topics
Viewing all articles
Browse latest Browse all 6525

db suspect & error

$
0
0
We have SQL 2014 cluster in vmware. Suddenly the user db is in suspect mode.From the event viewer the sequences of events1) Backup database successfully processed (around 11 pm). Scheduled full backup job ran that time2) The desktop window manager has exited with (around 7 am)3) SQLServerLogMgr::LogWriter: Operating system error 170(The requested resource is in use) (around 2pm)4) The log for database "testdb" is not available. Check the event log for related error messages. Resolve any errors and restart the database (around 2 pm)5) Database "testdb" was shutdown due to error 9001 in routine 'XdesRMFull::CommitInternal'. Restart for non-snapshot databases will be attempted after all connections to the database are aborted (Around 2pm)6)fcb:close-flush Operating system error (null) encountered (around 2 om)7) fcb:close-flush Operating system error (null) encountered (around 2 pm)8) Starting up database "testdb" (around 2 pm)From step 3 - step 8 has same timestamp9) 55 transactions rolled forward in database "testdb". This is info msg only. No user action required10)FCB::ZeroFile(), GetOverLappedResult(): Operating system error 170(The requested resource is in use) (Time stamp 4 sec after step8)11) An error occured during recovery, preventing db "Testdb" from restarting. Diagnose the recovery errors and fix them or restore from a known good backup. If errors not corrected or expected, contact technical support12) Login failed for the user "TestUser". Reason: Failed to open the explicitly specified database13) Continuous login failures for 1 hr14) SQLServerLogMgr::LogWriter: Operating system error 170(The requested resource is in use) (around 3pm)15) The log for database [b]"tempdb"[/b] is not available. Check the event log for related error messages. Resolve any errors and restart the database (around 3 pm)Continuously seen these msg.So restarted the active node. It makes the SQL failover. After that able to see the DBs normally.No clue what happened?

Viewing all articles
Browse latest Browse all 6525

Trending Articles