Log:
Date,Source,Severity,Message
05/31/2010 16:23:37,spid51,Unknown,EMERGENCY MODE DBCC CHECKDB (InProSys<c/> repair_allow_data_loss) executed by sa terminated abnormally due to error state 0. Elapsed time: 0 hours 0 minutes 34 seconds.
05/31/2010 16:23:37,spid51,Unknown,Unable to read and latch page (1:1400) with latch type SH. 23(?????? ? ?????? (CRC).) failed.
05/31/2010 16:23:37,spid51,Unknown,Error: 8966<c/> Severity: 16<c/> State: 2.
05/31/2010 16:23:37,spid51,Unknown,External dump process return code 0x20000001.<nl/>External dump process returned no errors.
05/31/2010 16:23:31,spid51,Unknown,Stack Signature for the dump is 0x00000168
05/31/2010 16:23:31,spid51,Unknown,* Short Stack Dump
05/31/2010 16:23:31,spid51,Unknown,* -------------------------------------------------------------------------------
05/31/2010 16:23:31,spid51,Unknown,* *******************************************************************************
05/31/2010 16:23:31,spid51,Unknown,*
05/31/2010 16:23:31,spid51,Unknown,* ProSys'<c/> REPAIR_ALLOW_DATA_LOSS)
05/31/2010 16:23:31,spid51,Unknown,* --Alter Database InProSys SET Single_user DBCC CheckDB('In
05/31/2010 16:23:31,spid51,Unknown,* Input Buffer 212 bytes -
05/31/2010 16:23:31,spid51,Unknown,*
05/31/2010 16:23:31,spid51,Unknown,* DBCC database corruption
05/31/2010 16:23:31,spid51,Unknown,*
05/31/2010 16:23:31,spid51,Unknown,* 05/31/10 16:23:31 spid 51
05/31/2010 16:23:31,spid51,Unknown,* BEGIN STACK DUMP:
05/31/2010 16:23:31,spid51,Unknown,*
05/31/2010 16:23:31,spid51,Unknown,* *******************************************************************************
05/31/2010 16:23:31,spid51,Unknown,***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL10.S8\MSSQL\LOG\SQLDump0001.txt
05/31/2010 16:23:31,spid51,Unknown,**Dump thread - spid = 0<c/> EC = 0x05BC39E0
05/31/2010 16:23:31,spid51,Unknown,Using 'dbghelp.dll' version '4.0.5'
05/31/2010 16:23:05,spid51,Unknown,Warning: The log for database 'InProSys' has been rebuilt. Transactional consistency has been lost. The RESTORE chain was broken<c/> and the server no longer has context on the previous log files<c/> so you will need to know what they were. You should run DBCC CHECKDB to validate physical consistency. The database has been put in dbo-only mode. When you are ready to make the database available for use<c/> you will need to reset database options and delete any extra log files.
05/31/2010 16:23:04,spid51,Unknown,Starting up database 'InProSys'.
05/31/2010 16:23:04,spid51,Unknown,Starting up database 'InProSys'.
05/31/2010 16:23:03,spid51,Unknown,The log scan number (326134:306:1) passed to log scan in database 'InProSys' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication<c/> re-create the publication. Otherwise<c/> restore from backup if the problem results in a failure during startup.
05/31/2010 16:23:03,spid51,Unknown,Error: 9003<c/> Severity: 20<c/> State: 1.
05/31/2010 16:23:03,spid51,Unknown,Starting up database 'InProSys'.
05/31/2010 16:22:50,spid51,Unknown,Setting database option SINGLE_USER to ON for database InProSys.
As message output, it gives:
Warning: The log for database 'InProSys' has been rebuilt. Transactional consistency has been lost. The RESTORE chain was broken, and the server no longer has context on the previous log files, so you will need to know what they were. You should run DBCC CHECKDB to validate physical consistency. The database has been put in dbo-only mode. When you are ready to make the database available for use, you will need to reset database options and delete any extra log files.
Msg 7985, Level 16, State 2, Line 3
System table pre-checks: Object ID 3. Could not read and latch page (1:1400) with latch type SH. Check statement terminated due to unrepairable error.
DBCC results for 'InProSys'.
Msg 8966, Level 16, State 2, Line 3
Unable to read and latch page (1:1400) with latch type SH. 23(?????? ? ?????? (CRC).) failed.
CHECKDB found 0 allocation errors and 1 consistency errors not associated with any single object.
CHECKDB found 0 allocation errors and 1 consistency errors in database 'InProSys'.
is the minimum repair level for the errors found by DBCC CHECKDB (InProSys, repair_allow_data_loss).
Now, my database marked as [Single-User].
What's next ?