BUG: DBCC DBREINDEX May Cause a LOAD TRAN to Fail with Error 1511

ID: Q233258

The information in this article applies to:

Microsoft SQL Server version 6.5 Service Pack 5 and 5a

BUG #: 18717 (SQLBUG_65)

SYMPTOMS

A transaction log dump that was generated after a DBCC DBREINDEX was issued on a huge table of the database may cause a subsequent load of the log dump to fail with error 1511, and will leave the database in a suspect state. You will see the following errors:

Msg 1511, Level 20, State 4
Sort cannot be reconciled with transaction log

Msg 4313, Level 16, State 1
Recreate index failed for table %d, index %d. The table has been left in an inconsistent state, and the index is missing, so LOAD TRANSACTION errors may result. Run DBCC CHECKTABLE on the table if LOAD TRANSACTION succeeds. Error while redoing log row in database '%s'. Rid pageid is %x and row num is %x.

The following conditions must be true for this problem to occur:

The transaction log was generated with SQL Server 6.5 Service Pack 5 or later.

Before the log was dumped, a DBCC DBREINDEX was performed on this database on a large table's clustered index and the SORTED_DATA_REORG option was used.

The table also has at least one nonclustered index.

RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next SQL Server service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp

The English version of this fix should have the following file attributes or later:


   Version    File name      Platform
   -----------------------------------------

   6.50.440   Sqlservr.exe   Intel and Alpha

NOTE: Due to file dependencies, the most recent hotfix or feature that contains the above files may also contain additional files.

NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, and if it is determined that you only require the fix you requested, no fee will be charged. However, if you request additional technical support, and if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support, you may be charged a non-refundable fee.

For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base:

Q154871 Determining If You Are Eligible for No-Charge Technical Support

WORKAROUND

To work around this problem, instead of doing a DBCC DBREINDEX, perform an explicit DROP INDEX and CREATE INDEX for every index on the table.

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 6.5 Service Pack 5 and 5a.

Additional query words:


Keywords          : SSrvAdmin kbbug6.50.sp5 
Version           : winnt:6.5 Service Pack 5 and 5a
Platform          : winnt 
Issue type        : kbbug

Last Reviewed: August 12, 1999