Home
  •  

Table error: Cross object linkage

Microsoft.SQLServer.2012.Table_error__Cross_object_linkage_1_5_Rule (Rule)

Knowledge Base article:

Causes

The page P_ID1 points, in a parent-child manner, to a page (P_ID2) in a different object.

Per-state information:

State 1 (I_ID1 = 0): The pages are from a heap. Page P_ID1 has a forwarding record that points to a row in page P_ID2.

State 1 (I_ID1 > 0): The pages are from an index B-tree. Page P_ID1 has a child page pointer that points to page P_ID2.

State 2: The pages are from a text object. One of the following is true:

Page P_ID1 is a text page that has a record with a child pointer that pointer points to a record on page P_ID2.

Page P_ID1 is an index or data page that has an in-row text root that points to a text page P_ID2.

Resolutions

HARDWARE FAILURE

Run hardware diagnostics and correct all revealed problems. Also examine the Microsoft® Windows NT system and application logs and the SQL Server™ error log to see if the error occurred as a result of a hardware failure. Fix any hardware related problems.

If you have persistent data inconsistency problems, try to swap out different hardware components to isolate the problem. Check that your system does not have write caching enabled on the disk controller. If you suspect this to be the case, contact your hardware vendor.

Finally, you might find it beneficial to switch to a completely new hardware system, including reformatting the disk drives and reinstalling the operating system.

RESTORE FROM BACKUP

If the problem is not hardware related and a known clean backup is available, restore the database from the backup.

DBCC CHECKDB

If no clean backup is available, execute DBCC CHECKDB without a repair clause to determine the extent of the corruption. DBCC CHECKDB will recommend a repair clause to use. Then, execute DBCC CHECKDB with the appropriate repair clause to repair the corruption.

CAUTION: If you are unsure what effect DBCC CHECKDB with a repair clause has on your data, contact your primary support provider before executing this statement.

CAUTION: This repair may cause data loss.

The repair depends on the error state:

State 1 (heap): The forwarding record on page P_ID1 will be deleted and all non-clustered indexes over the heap will be rebuilt.

State 1 (B-tree): The index containing page P_ID1 will be rebuilt.

State 2: The two records in pages P_ID1 and P_ID2 will be deleted.

If running DBCC CHECKDB with one of the repair clauses does not correct the problem, contact your primary support provider.

If the error still occurs once there are no errors reported by DBCC CHECKDB, script out the constraints, drop the constraints, and then recreate the constraints. If you still receive the error, transfer the data into a new table and drop the existing table.

Overrideable Parameters

Name

Description

Default Value

Enabled

Enables or disables the workflow.

Yes

Priority

Defines Alert Priority.

1

Severity

Defines Alert Severity.

2

Element properties:

TargetMicrosoft.SQLServer.2012.DBEngine
CategoryEventCollection
EnabledTrue
Event_ID8925
Event Source$Target/Property[Type="SQL!Microsoft.SQLServer.DBEngine"]/ServiceName$
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
RemotableTrue
Alert Message
Table error: Cross object linkage
{0}
Event LogApplication
CommentMom2012ID='{4131B4E6-3994-4D3F-83EA-228232BB9798}';MOM2012GroupID={467ECC75-C5DA-42BD-955C-A73BBB51AF74}

Member Modules:

ID Module Type TypeId RunAs 
_F6DA1507_12AF_11D3_AB21_00A0C98620CE_ DataSource Microsoft.Windows.EventProvider Microsoft.SQLServer.SQLDefaultAccount
GenerateAlert WriteAction System.Health.GenerateAlert Default

Source Code:

<Rule ID="Microsoft.SQLServer.2012.Table_error__Cross_object_linkage_1_5_Rule" Target="SQL2012Core!Microsoft.SQLServer.2012.DBEngine" Enabled="true" ConfirmDelivery="true" Remotable="true" Comment="Mom2012ID='{4131B4E6-3994-4D3F-83EA-228232BB9798}';MOM2012GroupID={467ECC75-C5DA-42BD-955C-A73BBB51AF74}">

  <Category>EventCollection</Category>

  <DataSources>

    <DataSource ID="_F6DA1507_12AF_11D3_AB21_00A0C98620CE_" Comment="{F6DA1507-12AF-11D3-AB21-00A0C98620CE}" TypeID="Windows!Microsoft.Windows.EventProvider" RunAs="SQL!Microsoft.SQLServer.SQLDefaultAccount">

      <ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>

      <LogName>Application</LogName>

      <Expression>

        <And>

          <Expression>

            <SimpleExpression>

              <ValueExpression>

                <XPathQuery>PublisherName</XPathQuery>

              </ValueExpression>

              <Operator>Equal</Operator>

              <ValueExpression>

                <Value>$Target/Property[Type="SQL!Microsoft.SQLServer.DBEngine"]/ServiceName$</Value>

              </ValueExpression>

            </SimpleExpression>

          </Expression>

          <Expression>

            <SimpleExpression>

              <ValueExpression>

                <XPathQuery>EventDisplayNumber</XPathQuery>

              </ValueExpression>

              <Operator>Equal</Operator>

              <ValueExpression>

                <Value>8925</Value>

              </ValueExpression>

            </SimpleExpression>

          </Expression>

        </And>

      </Expression>

    </DataSource>

  </DataSources>

  <WriteActions>

    <WriteAction ID="GenerateAlert" TypeID="SystemHealth!System.Health.GenerateAlert">

      <Priority>1</Priority>

      <Severity>2</Severity>

      <AlertMessageId>$MPElement[Name="Microsoft.SQLServer.2012.Table_error__Cross_object_linkage_1_5_Rule.AlertMessage"]$</AlertMessageId>

      <AlertParameters>

        <AlertParameter1>Event ID: $Data/EventDisplayNumber$. $Data/EventDescription$</AlertParameter1>

      </AlertParameters>

      <Suppression>

        <SuppressionValue/>

      </Suppression>

    </WriteAction>

  </WriteActions>

</Rule>