Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

unexpected SQL server 2012 shutdown Expand / Collapse
Author
Message
Posted Tuesday, May 7, 2013 4:39 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Yesterday @ 9:48 AM
Points: 202, Visits: 352
Hi,

I have installed 3 new instances of SQL Server 2012 on a stand alone server. SQL Service is set to automatic on all of them. Yet, suddenly, all the instances have shut down abruptly throwing the following errors.
Need some advice around this issue?

SQL Server must shut down in order to recover a database (database ID 2). The database is either a user database that could not be shut down or a system database. Restart SQL Server. If the database fails to recover after another startup, repair or restore the database.

During undoing of a logged operation in database 'tempdb', an error occurred at log record ID (438:376:163). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.
Post #1450050
Posted Tuesday, May 7, 2013 4:45 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Yesterday @ 9:48 AM
Points: 202, Visits: 352
The build that I am running is this - 11.00.3128
Post #1450055
Posted Thursday, May 16, 2013 8:48 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Yesterday @ 9:48 AM
Points: 202, Visits: 352
Just checking if this question went unnoticed.
Post #1453592
Posted Thursday, May 16, 2013 11:29 AM
SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Tuesday, August 19, 2014 3:37 PM
Points: 4,389, Visits: 9,522
This indicates that you have a problem with tempdb (database ID 2). This could be related to the SAN dropping the connection, or corruption on the LUN, or some other problem.

You need to review all relevant event logs and error logs to determine what is causing the server to drop access to that database file.


Jeffrey Williams
Problems are opportunites brilliantly disguised as insurmountable obstacles.

How to post questions to get better answers faster
Managing Transaction Logs
Post #1453702
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse