marked SUSPECT by recovery

  • Hello

    I have executed a repair on a suspect databases as follows

    begin tran

    DBCC CHECKDB ( 'GSP_DEV_1_4_3', REPAIR_ALLOW_DATA_LOSS )

    Druing the process the network connection was lost and as a reult the db is now in a condition

    Server: Msg 926, Level 10, State 1, Line 1

    Database 'GSP_DEV_1_4_3' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.

    Server: Msg 5069, Level 16, State 1, Line 1

    ALTER DATABASE statement failed.

    There is a backup but this is rather out of date and will be of little use in recovering the situation. Any suggestions. The log is suggesting a manual restart of the database, I am not sure what this entails

  • What error messages show in SQL Server errorlog?

  • Please note, resolved by bouncing the server, but here are the log details anyway

    Messages in error log are

    DBCC CHECKDB (GSP_DEV_1_4_3, repair_allow_data_loss) executed by EMEA\ExonJG found 24 errors and repaired 2 errors.

    Error: 9004, Severity: 23, State: 3

    An error occurred while processing the log for database 'GSP_DEV_1_4_3'..

    Error: 3314, Severity: 21, State: 4

    Error while undoing logged operation in database 'GSP_DEV_1_4_3'. Error at log record ID (9839:9582:826)..

    Error: 9001, Severity: 21, State: 1

    The log for database 'GSP_DEV_1_4_3' is not available..

    Error: 3314, Severity: 21, State: 5

    Error while undoing logged operation in database 'GSP_DEV_1_4_3'. Error at log record ID (9839:9114:1)..

    Using 'dbghelp.dll' version '4.0.5'

    *Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL\log\SQL00096.dmp

    Error: 0, Severity: 19, State: 0

    SqlDumpExceptionHandler: Process 14 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process..Includes stack dump information

    Can not auto-restart the database(dbid 20). Try to start the database manually.

  • What version of SQL Server and service pack are you running?

  • Product 2000

    Build 534

    Service pack2000 SP2.01

    Edition Enterprise Edition

    on Windows NT 5.0 (Build 2195: Service Pack 2)

  • I think you have to take the Database out of suspect using

    sp_resetstatus [ @DBName = ] 'database'

    and then run dbcc's

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply