Home
  •  

Could not read and latch page.

Microsoft.SQLServer.2000.Could_not_read_and_latch_page (Rule)

Knowledge Base article:

Causes

The page read failed for some reason (see any accompanying errors), or a latch could not be taken (there may be latch timeout messages on the error log).

Per-state information:

State 1: The page is being read as part of the per-checks of critical system tables.

TYPE is 'SH'.

OPERATION is the name of the DBCC command being executed.

State 2: An indeterminate operation is being performed. The error was raised by generic DBCC read/latch code.

TYPE may be 'NL', 'SH', 'EX', 'UP', or 'Unknown'.

OPERATION is 'Acquire (Wait)' or the string provided by the buffer pool.

State 3: An indeterminate operation is being performed. The error was raised by generic DBCC read/latch code.

TYPE may be 'NL', 'SH', 'UP', 'EX', or 'Unknown'.

OPERATION is 'bufget'.

State 4: The page is being read to verify its page ID.

TYPE may be 'SH', 'UP', 'EX', or 'Unknown'.

OPERATION is 'VerifyPageId'.

State 5: The page is being repaired.

TYPE is 'SH'.

OPERATION is 'DbccExChangePageState ()'.

Resolutions

HARDWARE FAILURE

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

If you have persistent data corruption problems, try to swap out different hardware components to isolate the problem. Check to ensure that your system does not have write caching enabled on the disk controller. If you suspect this to be the problem, 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: There is no repair for this error, because it is only a symptom of the real problem. See the accompanying errors for details.

Element properties:

TargetMicrosoft.SQLServer.2000.DBEngine
CategoryEventCollection
EnabledTrue
Event Source$Target/Property[Type="SQL!Microsoft.SQLServer.DBEngine"]/ServiceName$
Alert GenerateTrue
Alert SeverityWarning
Alert PriorityNormal
RemotableTrue
Alert Message
Could not read and latch page.
{0}
Event LogApplication
CommentMom2005ID='{062D1173-AED9-44FD-AA99-D7C87DF30D37}'

Member Modules:

ID Module Type TypeId RunAs 
EventDS DataSource Microsoft.Windows.EventProvider Default
GenerateAlert WriteAction System.Health.GenerateAlert Default

Source Code:

<Rule ID="Microsoft.SQLServer.2000.Could_not_read_and_latch_page" Target="SQL2000Core!Microsoft.SQLServer.2000.DBEngine" Enabled="true" Comment="Mom2005ID='{062D1173-AED9-44FD-AA99-D7C87DF30D37}'" Remotable="true">

  <Category>EventCollection</Category>

  <DataSources>

    <DataSource ID="EventDS" TypeID="Windows!Microsoft.Windows.EventProvider">

      <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>

            <RegExExpression>

              <ValueExpression>

                <XPathQuery>EventDisplayNumber</XPathQuery>

              </ValueExpression>

              <Operator>MatchesMOM2005RegularExpression</Operator>

              <Pattern>^(17052|17055)$</Pattern>

            </RegExExpression>

          </Expression>

          <Expression>

            <RegExExpression>

              <ValueExpression>

                <XPathQuery>EventDescription</XPathQuery>

              </ValueExpression>

              <Operator>MatchesMOM2005BooleanRegularExpression</Operator>

              <Pattern>((^.*8966 and (not ^.*\n.*8966)) or (^.*8966.*\n.*8966)) AND (NOT ^.*[0-9]+.*8966) AND (NOT ^.*8966[0-9]+)</Pattern>

            </RegExExpression>

          </Expression>

        </And>

      </Expression>

    </DataSource>

  </DataSources>

  <WriteActions>

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

      <Priority>1</Priority>

      <Severity>1</Severity>

      <AlertOwner>$Data/PublisherName$</AlertOwner>

      <AlertMessageId>$MPElement[Name="Microsoft.SQLServer.2000.Could_not_read_and_latch_page.AlertMessage"]$</AlertMessageId>

      <AlertParameters>

        <AlertParameter1>$Data/EventDescription$</AlertParameter1>

      </AlertParameters>

      <Suppression>

        <SuppressionValue/>

      </Suppression>

    </WriteAction>

  </WriteActions>

</Rule>