Today's synchronous replication has appeared as follows:
Table Error: Database ID 20, Object ID 5575058, Index ID 0. CHAIN LINKAGE Mismatch. (1: 1617) -> Next = (1: 1618), But (1: 1618) -> prev = (1: 356). .
Error: 8908, SEVERITY: 22, State: 6
Check the online book, explain the following: Message TextTable error: Database ID% D, Object ID% D, INDEX ID% d. CHAIN LINKAGE Mismatch.% S_pgid-> next =% s_pgid, but% s_pgid-> prev =% s_pgID .ExplanationThis error occurs when Microsoft® SQL Server ™ detects an inconsistency in the page linkage of one of the page chains associated with a table, for example, when a page's next pointer points to a page whose previous pointer points back to a different page. there is one doubly-linked page chain for the table data as well as one for each index level. Important This is a serious error and must be corrected immediately. If DBCC statements detect this error during run-time processing, error 605 will also occur .ActionDetermine which table is corrupt by examining the current page in the error message. Execute DBCC CHECKDB without a repair clause to determine the extent of the corruption. Then, execute DBCC CHECKDB with the appropriate repair clause to repair the corruption. If the page is Associated Wi th an index, it is sometimes possible to resolve the problem by dropping the index. In most cases, you must recover the database from a known clean backup.If the error involves an index page, use the REPAIR_REBUILD clause. If the error involves a data page, it may be necessary to use the REPAIR_ALLOW_DATA_LOSS clause. In the likely event that you can not allow the loss of data, you will need to restore from a known clean backup. If the problem persists, contact your primary support provider. Have the Output from DBCC Checkdb Available for Review To Master Find Database ID 20 The corresponding Database ID 20 is DISRIBUTION, Object ID 5575058 corresponds to MSREPL_COMMAVANDS, then execute dbcc checkdb in Distribution, the result shows no errors, then execute synchronous copy is OK ... .
