Select the product you need help with

FIX: A DELETE Statement with a Self-Join May Fail and You Receive a 625 Error

Article ID: 810026 - View products that this article applies to.

BUG #: 362962 (SHILOH_BUGS)

SYMPTOMS

A DELETE statement that includes a self-join may fail and you receive the following error message:

Error: 625, Severity: 20, State: 1
Cannot retrieve row from page (0:246) by RID because the slotid (681262616) is not valid..

When you run a DBCC CHECKDB statement on the database, after you receive the 625 error, DBCC CHECKDB does not report any errors.

Back to the top | Give Feedback

CAUSE

Because the query plan does not include the operator you must have to provide Halloween protection, the query may try to fetch the row that was deleted.

Back to the top | Give Feedback

WORKAROUND

To work around this error, specify OPTION (HASH JOIN) at the end of the query.

Back to the top | Give Feedback

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

290211

(http://support.microsoft.com/kb/290211/ )

How to obtain the latest SQL Server 2000 service pack

Hotfix information

The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

   Date         Time    Version        Size             File name     Description
   ---------------------------------------------------------------------------------

   08-Nov-2002  00:49   2000.80.701.0  7,471,188 bytes  Sqlservr.exe  SP2-based fix

NOTE: Because of file dependencies, the most recent hotfix or feature that contains the files may also contain additional files.

Back to the top | Give Feedback

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.

Back to the top | Give Feedback