Consequences of Error 644?

My customer has encountered Error 644 (Could not find the index entry for RID
'%.*hs' in index page %S_PGID, index ID %d, database '%.*ls'.). I have
looked at the following KB entries:
PRB: Additional SQL Server Diagnostics Added to Detect Unreported I/O Problems
http://support.microsoft.com/default...b;en-us;826433
FIX: You receive a 644 error message when you run an UPDATE statement and
the isolation level is set to READ UNCOMMITTED
http://support.microsoft.com/?kbid=834290
I need help in interpreting this error for my customer. What they want to
know is:
1) Is this indicative of a larger problem?
2) Is it likely to happen repeatedly?
3) Is there a solution besides the available hotfix (since a hotfix is
always a scary thing to apply to a production system)?
Is there anything beyond what is offered in the above KB articles that can
help my customer?
Thanks,
Ron
You'd do best to call CSS to get the exact answer.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"RonTop" <RonTop@.discussions.microsoft.com> wrote in message
news:DC27912A-11CA-4084-959B-2F414F7DD27E@.microsoft.com...
> My customer has encountered Error 644 (Could not find the index entry for
RID
> '%.*hs' in index page %S_PGID, index ID %d, database '%.*ls'.). I have
> looked at the following KB entries:
> PRB: Additional SQL Server Diagnostics Added to Detect Unreported I/O
Problems
> http://support.microsoft.com/default...b;en-us;826433
> FIX: You receive a 644 error message when you run an UPDATE statement and
> the isolation level is set to READ UNCOMMITTED
> http://support.microsoft.com/?kbid=834290
> I need help in interpreting this error for my customer. What they want to
> know is:
> 1) Is this indicative of a larger problem?
> 2) Is it likely to happen repeatedly?
> 3) Is there a solution besides the available hotfix (since a hotfix is
> always a scary thing to apply to a production system)?
> Is there anything beyond what is offered in the above KB articles that can
> help my customer?
> Thanks,
> Ron
|||If you get the errr while running DBCC - The error is telling you that a row
exists in a table, but the index entry for some index is missing... This
could be a transient problem, - one that occurs because you are running
DBCCs while users are making changes.. re-run DBCC on the table. If the
error moves to a different row or a different table, it is just a transient
error due to timing... However if the same error shows up in the same
location - it is a hard error and must be addressed.
You can drop and re-create the index, since the index is created from the
table.
If you get the error while running and UPdate statement, the KB article you
mention provideds the details. It says that the problem is a SQL Server
software problem, and will not lead to corruption. If it is this case, it
will happen repeatedly when the customer does the same work which caused the
issue originally... I would apply the hotfix - but I would first open a
call to PSS ($249) - to get their advice.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"RonTop" <RonTop@.discussions.microsoft.com> wrote in message
news:DC27912A-11CA-4084-959B-2F414F7DD27E@.microsoft.com...
> My customer has encountered Error 644 (Could not find the index entry for
RID
> '%.*hs' in index page %S_PGID, index ID %d, database '%.*ls'.). I have
> looked at the following KB entries:
> PRB: Additional SQL Server Diagnostics Added to Detect Unreported I/O
Problems
> http://support.microsoft.com/default...b;en-us;826433
> FIX: You receive a 644 error message when you run an UPDATE statement and
> the isolation level is set to READ UNCOMMITTED
> http://support.microsoft.com/?kbid=834290
> I need help in interpreting this error for my customer. What they want to
> know is:
> 1) Is this indicative of a larger problem?
> 2) Is it likely to happen repeatedly?
> 3) Is there a solution besides the available hotfix (since a hotfix is
> always a scary thing to apply to a production system)?
> Is there anything beyond what is offered in the above KB articles that can
> help my customer?
> Thanks,
> Ron
sqlsql