Database restore suspect. Unable to open database ' XX ' version 611. Please upgrade this database to the latest version. __ Database

found a database on the Internet, in their own SQL Server 2008 R2 restore, there is an error, it seems that the version is different.

The restore was unsuccessful, the database was canceled, but it was in a "suspicious" state and could not be viewed and used.

Some repair operations are also useless.

when the database is online, the error comes out. (You can also view the error log)

Use master

Go

ALTER DATABASE pagenumber SET ONLINE

Message 3418, Level 16, State 1, line 2nd

The restore operation cannot delay error 824. You can delay errors only in databases that use the full recovery model and the active backup log chain.

Message 926, Level 14, State 1, line 2nd

Unable to open database ' pagenumber '. The restore operation has marked the database as suspect. For more information, see SQL Server error log.

Message 5069, Level 16, State 1, line 2nd

ALTER DATABASE statement failed.

Message 3418, Level 16, State 1, line 2nd

The restore operation cannot delay error 824. You can delay errors only in databases that use the full recovery model and the active backup log chain.

Message 926, Level 14, State 1, line 2nd

Unable to open database ' pagenumber '. The restore operation has marked the database as suspect. For more information, see SQL Server error log.

Message 5069, Level 16, State 1, line 2nd

ALTER DATABASE statement failed.

Message 824, Level 24, State 2, line 2nd

SQL Server has detected a consistent, logical I/O error checksum (should be: 0X8E3FFDD9, but actually: 0X8AE47DD9). In the file ' F:\Microsoft sqlserver\mssql10_50.mssqlserver\mssql\data\pagenumber.mdf ', the offset is 0x00000000190000 location to the database ID15 The error occurred while the page (1:200) in was performing a read. The SQL Server error log or other messages in the System event log may provide more detailed information. This is a serious error condition that threatens the integrity of the database and must be corrected immediately. Please perform a complete database consistency check (DBCCCHECKDB). This error can be caused by a number of factors; For more information, see SQL Server Books Online.

Message 3414, Level 21, State 2, line 2nd

An error occurred during recovery, causing the database ' pagenumber ' (database ID15) to not be restarted. Please diagnose and correct these recovery errors, or restore them from a known good backup. If you cannot correct the error, or if it is an unexpected error, contact your technical support personnel.

Solve:

allow error restore when restoring a database:

Use master

Go

Restore Database PageNumber

From DISK = ' D:\PageNumber.bak ' with Continue_after_error,recovery

1160 pages have been processed for the database ' pagenumber ', file ' PageNumber ' (located on file 1).

453 pages have been processed for the database ' pagenumber ', file ' Pagenumber_log ' (located on file 1).

Message 824, Level 16, State 2, line 1th

SQL Server has detected a consistent, logical I/O error checksum (should be: 0X8E3FFDD9, but actually: 0X8AE47DD9). In the file ' F:\Microsoft sqlserver\mssql10_50.mssqlserver\mssql\data\pagenumber.mdf ', the offset is 0x00000000190000 location to the database ID15 The error occurred while the page (1:200) in was performing a read. The SQL Server error log or other messages in the System event log may provide more detailed information. This is a serious error condition that threatens the integrity of the database and must be corrected immediately. Please perform a complete database consistency check (DBCC CHECKDB). This error can be caused by a number of factors; For more information, see SQL Server Books Online.

Converting database ' pagenumber ' from version 611 to current version 661.

The database ' PageNumber ' is being upgraded from version 611 to version 621.

The database ' PageNumber ' is being upgraded from version 621 to version 622.

The database ' PageNumber ' is being upgraded from version 622 to version 625.

The database ' PageNumber ' is being upgraded from version 625 to version 626.

The database ' PageNumber ' is being upgraded from version 626 to version 627.

The database ' PageNumber ' is being upgraded from version 627 to version 628.

The database ' PageNumber ' is being upgraded from version 628 to version 629.

The database ' PageNumber ' is being upgraded from version 629 to version 630.

The database ' PageNumber ' is being upgraded from version 630 to version 631.

The database ' PageNumber ' is being upgraded from version 631 to version 632.

The database ' PageNumber ' is being upgraded from version 632 to version 633.

The database ' PageNumber ' is being upgraded from version 633 to version 634.

The database ' PageNumber ' is being upgraded from version 634 to version 635.

The database ' PageNumber ' is being upgraded from version 635 to version 636.

The database ' PageNumber ' is being upgraded from version 636 to version 637.

The database ' PageNumber ' is being upgraded from version 637 to version 638.

The database ' PageNumber ' is being upgraded from version 638 to version 639.

The database ' PageNumber ' is being upgraded from version 639 to version 640.

The database ' PageNumber ' is being upgraded from version 640 to version 641.

The database ' PageNumber ' is being upgraded from version 641 to version 642.

The database ' PageNumber ' is being upgraded from version 642 to version 643.

The database ' PageNumber ' is being upgraded from version 643 to version 644.

The database ' PageNumber ' is being upgraded from version 644 to version 645.

The database ' PageNumber ' is being upgraded from version 645 to version 646.

The database ' PageNumber ' is being upgraded from version 646 to version 647.

The database ' PageNumber ' is being upgraded from version 647 to version 648.

The database ' PageNumber ' is being upgraded from version 648 to version 649.

The database ' PageNumber ' is being upgraded from version 649 to version 650.

The database ' PageNumber ' is being upgraded from version 650 to version 651.

The database ' PageNumber ' is being upgraded from version 651 to version 652.

The database ' PageNumber ' is being upgraded from version 652 to version 653.

The database ' PageNumber ' is being upgraded from version 653 to version 654.

The database ' PageNumber ' is being upgraded from version 654 to version 655.

The database ' PageNumber ' is being upgraded from version 655 to version 660.

The database ' PageNumber ' is being upgraded from version 660 to version 661.

The RESTORE DATABASE successfully processed 1613 pages, costing 0.416 seconds (30.280 MB/s).

The version is upgraded from 611 to 661 and can finally come in. You can fix it in some other way after you come in.

 

Use master

Go

DBCC CHECKDB (pagenumber)

 

PageNumber the DBCC results.

Service Broker Message 9675, State 1: Parsed message type: 14.

Service Broker Message 9676, State 1: Parsed services contract: 6.

Service Broker Message 9667, State 1: Parsed services: 3.

Service Broker Message 9668, State 1: Serviced queues analyzed: 3.

Service Broker Message 9669, State 1: parsed session endpoint: 0.

Service Broker Message 9674, State 1: parsed session Group: 0.

Service Broker message 9670, State 1: Parsed remote service bindings: 0.

Service Broker Message 9605, State 1: Parsed session priority: 0.

Message 8939, Level 16, State 98, line 2nd

Table error: Object ID 0, index ID-1, partition ID 0, allocation unit ID 72164616100118528 (type unknown), page (1:200). Test (Is_off (Buf_ioerr, Pbuf->bstat)) failed. Values are 12716041 and-4.

CHECKDB found that 0 allocation errors and one consistency error were not associated with any single object.

Sys.sysrscols the DBCC results.

There are 635 rows on the 7 page of the object ' Sys.sysrscols '.

(......) Omit n rows)

sys.queue_messages_2041058307 the DBCC results.

There are 0 rows on the 0 page of the object ' sys.queue_messages_2041058307 '.

The DBCC result of test.

Message 8928, Level 16, State 1, line 2nd

Object ID 2073058421, index ID 1, partition ID72057594038452224, allocation unit ID 72057594042449920 (type In-row data): Unable to Process page (1:200). For more information, see other error messages.

Message 8976, Level 16, State 1, line 2nd

Table error: Object ID 2073058421, index ID 1, partition ID72057594038452224, allocation unit ID 72057594042449920 (type in-row data). The page (1:200) was not found during the scan, but the page's parent (1:1142) and previous page (1:199) refer to it. Please check the previous error message.

Message 8978, Level 16, State 1, line 2nd

Table error: Object ID 2073058421, index ID 1, partition ID72057594038452224, allocation unit ID 72057594042449920 (type in-row data). Page (1:201) is missing a reference to it from the previous page (1:200). This may be because of a link problem.

There are 999 rows on the 999 page of the object ' Test '.

CHECKDB found 0 allocation errors and 3 consistency errors in table ' Test ' (object ID 2073058421).

sys.filestream_tombstone_2089058478 the DBCC results.

There are 0 rows on the 0 page of the object ' sys.filestream_tombstone_2089058478 '.

Sys.syscommittab the DBCC results.

There are 0 rows on the 0 page of the object ' Sys.syscommittab '.

CHECKDB found 0 allocation errors and 4 consistency errors in the database ' PageNumber '.

Repair_allow_data_loss is the lowest level of repair for errors found by DBCC CHECKDB (pagenumber).

DBCC execution completed. If DBCC prints an error message, contact your system administrator.

 

 

you can see the second-last line above, Repair_allow_data_loss allows you to fix data loss.

execute the following code, where CHECKDB output repair parameters:

Use master

Go

ALTER DATABASE pagenumber SET single_user

Go

DBCC CHECKDB (Pagenumber,repair_allow_data_loss)

Go

ALTER DATABASE pagenumber SET multi_user

Go

PageNumber the DBCC results.

Service Broker Message 9675, State 1: Parsed message type: 14.

Service Broker Message 9676, State 1: Parsed services contract: 6.

Service Broker Message 9667, State 1: Parsed services: 3.

Service Broker Message 9668, State 1: Serviced queues analyzed: 3.

Service Broker Message 9669, State 1: parsed session endpoint: 0.

Service Broker Message 9674, State 1: parsed session Group: 0.

Service Broker message 9670, State 1: Parsed remote service bindings: 0.

Service Broker Message 9605, State 1: Parsed session priority: 0.

Message 8939, Level 16, State 98, line 1th

Table error: Object ID 0, index ID-1, partition ID 0, allocation unit ID 72164616100118528 (type unknown), page (1:200). Test (Is_off (Buf_ioerr, Pbuf->bstat)) failed. Values are 12584969 and-4.

the error has been fixed.

CHECKDB found that 0 allocation errors and one consistency error were not associated with any single object.

CHECKDB fixes 0 allocation errors and a consistency error that is not associated with any single object.

Sys.sysrscols the DBCC results.

There are 635 rows on the 7 page of the object ' Sys.sysrscols '.

(......) Omit n rows)

sys.queue_messages_2041058307 the DBCC results.

There are 0 rows on the 0 page of the object ' sys.queue_messages_2041058307 '.

The DBCC result of test.

FIX: Object ' dbo in database ' pagenumber '. Test ' successfully regenerated the clustered index.

FIX: Page (1:200) has been released from Object ID 2073058421, index ID 1, partition ID 72057594038452224, allocation unit ID 72057594042449920 (type in-row data).

Message 8945, Level 16, State 1, line 1th

Table error: Object ID 2073058421 will be regenerated, index ID 1.

the error has been fixed.

Message 8928, Level 16, State 1, line 1th

Object ID 2073058421, index ID 1, partition ID72057594038452224, allocation unit ID 72057594042449920 (type In-row data): Unable to Process page (1:200). For more information, see other error messages.

the error has been fixed.

Message 8976, Level 16, State 1, line 1th

Table error: Object ID 2073058421, index ID 1, partition ID72057594038452224, allocation unit ID 72057594042449920 (type in-row data). The page (1:200) was not found during the scan, but the page's parent (1:1142) and previous page (1:199) refer to it. Please check the previous error message.

the error has been fixed.

Message 8978, Level 16, State 1, line 1th

Table error: Object ID 2073058421, index ID 1, partition ID72057594038452224, allocation unit ID 72057594042449920 (type in-row data). Page (1:201) is missing a reference to it from the previous page (1:200). This may be because of a link problem.

the error has been fixed.

There are 999 rows on the 999 page of the object ' Test '.

CHECKDB found 0 allocation errors and 3 consistency errors in table ' Test ' (object ID 2073058421).

CHECKDB fixes 0 Allocation errors and 3 consistency errors in table ' Test ' (object ID 2073058421).

sys.filestream_tombstone_2089058478 the DBCC results.

There are 0 rows on the 0 page of the object ' sys.filestream_tombstone_2089058478 '.

Sys.syscommittab the DBCC results.

There are 0 rows on the 0 page of the object ' Sys.syscommittab '.

CHECKDB found 0 allocation errors and 4 consistency errors in the database ' PageNumber '.

CHECKDB fixes 0 allocation errors and 4 consistency errors in the database ' PageNumber '.

DBCC execution completed. If DBCC prints an error message, contact your system administrator.