?
Solved

SQL 2000 latch page errors urgent

Posted on 2006-11-21
4
Medium Priority
?
1,142 Views
Last Modified: 2007-12-19
Hi This is canny urgent:

On last nights integrity check I have the following errors:

Msg 8966, Sev 16: Could not read and latch page (1:89000) with latch type UP. 菴륺 failed. [SQLSTATE 42000]
Msg 8966, Sev 16: Could not read and latch page (1:89001) with latch type UP. 菴륺 failed. [SQLSTATE 42000]
Msg 8966, Sev 16: Could not read and latch page (1:89002) with latch type UP. 菴륺 failed. [SQLSTATE 42000]
Msg 8966, Sev 16: Could not read and latch page (1:89003) with latch type UP. 菴륺 failed. [SQLSTATE 42000]
Msg 8966, Sev 16: Could not read and latch page (1:89004) with latch type UP. 菴륺 failed. [SQLSTATE 42000]
Msg 8966, Sev 16: Could not read and latch page (1:89005) with latch type UP. 菴륺 failed. [SQLSTATE 42000]
Msg 8966, Sev 16: Could not read and latch page (1:89006) with latch type UP. 菴륺 failed. [SQLSTATE 42000]
Msg 8966, Sev 16: Could not read and latch page (1:89007) with latch type UP. 菴륺 failed. [SQLSTATE 42000]

I also received the following warnings around the same time:


DESCRIPTION:      Error: 823, Severity: 24, State: 2
I/O error 1450(error not found) detected during read at offset 0x000000269bc000 in file 'D:\MSSQL\Data\agressodata5.ndf'.

This is worrying me ever so slightly........running a dbcc checkdb again shows all is well as though this is an intermittent error? I am worried that there may be corruption in my ndf file, is there any way to check this?

Additionally does anyone have any idea's what is causing this?
0
Comment
Question by:Netstore
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
4 Comments
 
LVL 28

Expert Comment

by:imran_fast
ID: 17986914
Run this on your database and check the result

DBCC CHECKDB
GO
0
 
LVL 28

Expert Comment

by:imran_fast
ID: 17986927
sorry i didn't notice you ran checkdb
next step

Checks the consistency of disk space allocation structures for a specified database.
DBCC CHECKALLOC ('YourDbName',REPAIR_FAST )
GO

REPAIR_ALLOW_DATA_LOSS
Performs all repairs done by REPAIR_REBUILD and includes allocation and deallocation of rows and pages for correcting allocation errors, structural row or page errors, and deletion of corrupted text objects. These repairs can result in some data loss. The repair can be done under a user transaction to allow the user to roll back the changes made. If repairs are rolled back, the database will still contain errors and should be restored from a backup. If a repair for an error has been skipped due to the provided repair level, any repairs that depend on the repair are also skipped. After repairs are completed, back up the database.
REPAIR_FAST
Performs minor, nontime-consuming repair actions such as repairing extra keys in nonclustered indexes. These repairs can be done quickly and without risk of data loss.
REPAIR_REBUILD
Performs all repairs done by REPAIR_FAST and includes time-consuming repairs such as rebuilding indexes. These repairs can be done without risk of data loss.
0
 
LVL 5

Author Comment

by:Netstore
ID: 17986964
I've ran another checkdb and no errors are returned ????????

However I ran a dbcc showcontig - (just to check my indexes) and get loads of :

Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (6:32018) with latch type SH. 1450(error not found) failed.
Server: Msg 8966, Level 16, State 1, Line 1

Is there any risk associated with the checkalloc command doing repairs on the fly?
Do I need to do it when the system is quiet? i.e. no users on. I take it I should be taking a backup before running any of this.

Any help greatly appreciated?
0
 
LVL 28

Accepted Solution

by:
imran_fast earned 2000 total points
ID: 17987016
You need to rebuild index either you can rebuilt index using
DBCC DBREINDEX on individual table or

>>I take it I should be taking a backup before running any of this.
It will be good but there won't be any problem

run this
DBCC CHECKALLOC ('YourDbName',REPAIR_REBUILD  )
GO

It will take time as it will rebuild indexes.
0

Featured Post

Get real performance insights from real users

Key features:
- Total Pages Views and Load times
- Top Pages Viewed and Load Times
- Real Time Site Page Build Performance
- Users’ Browser and Platform Performance
- Geographic User Breakdown
- And more

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Recently we ran in to an issue while running some SQL jobs where we were trying to process the cubes.  We got an error saying failure stating 'NT SERVICE\SQLSERVERAGENT does not have access to Analysis Services. So this is a way to automate that wit…
In part one, we reviewed the prerequisites required for installing SQL Server vNext. In this part we will explore how to install Microsoft's SQL Server on Ubuntu 16.04.
Using examples as well as descriptions, and references to Books Online, show the different Recovery Models available in SQL Server and explain, as well as show how full, differential and transaction log backups are performed
This videos aims to give the viewer a basic demonstration of how a user can query current session information by using the SYS_CONTEXT function
Suggested Courses

770 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question