Fault environment: WinNT4.0Cluster SQL Server7.0
Fault Description: At 8:30, the database is discovered, and the CLUSTER will not be able to get up.
Event type: error
Source: Clussvc
Event Category Directory: (2052)
Event ID: 1066
date:
2005-1-21
Time: 8:23:20
Users: N / A
Computer: Test
description:
Cluster Disk Resource Disk G :: Is Corrupt. Running Chkdsk / f To Repair Problems.
Please check the instructions and support centers at http://go.microsoft.com/fwlink/events.asp to achieve other information.
According to the error record, you need to do Check Disk on Test / G. After making full backup on the database, stop the Cluster service, then restart Server, Chkdsk g: / f is successful. Start SQL Server again, still unable to open, Windows EVENT logs out of the following error
Event type: information
Event Source: MSSQLSERVER $ TEST
Event Category Directory: Server
Event identification code: 17055
date:
2005-1-21
Time: 8:23:54
Users: N / A
Computer: Test
description:
17052: Database 'Tempdb' Cannot Be Opened. It has seen. See the SQL Server ErrorLog for more information.
Please check the instructions and support centers at http://go.microsoft.com/fwlink/events.asp to achieve other information.
data:
0000:
9C
42 00 00
0A
00 00 00 ...
...
0030: 00 00 ..
In the Microsoft website, find 17055, 10752 error code has no results. By looking for keyword "Database 'Tempdb' Cannot Be Opened", find an article to rebuild Tempdb http://support.microsoft.com/default.aspx?scid= KB; EN-US; 288809
Handling method: According to Microsoft documents, the operation steps are as follows
1. Set SQL Server Virtul Server Name
C: /> set _cluster_network_name = Yoursqlvirtualname
2. Command line launches SQL Server single user mode (command line window can not be closed)
C: /> SQLSERVR-C-F -T3608 -T4022
3. Turn on the query analyzer, log in with SA, and execute the system stored procedure to reset the TEMPDB status.
EXEC MASTER..SP_RESETSTATUS TEMPDB
4. Press Ctrl C to close the command line window of step 2
5. Start SQL Server normally, then rebuild TEMPDB
6. Restore the environmental parameter settings of step 1
C: /> set _cluster_network_name =
At this point, the database returns to normal.
