This article was previously published under Q233258
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 18717 (SQLBUG_65)
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.
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.
Microsoft has confirmed this to be a problem in SQL Server version 6.5. This problem has been corrected in the Post Service Pack 5a Update for Microsoft SQL Server version 6.5. To install the Post Service Pack 5a Update, you must have either SQL Server 6.5 SP5 or SP5a installed.
For information about how to download and install the SQL Server 6.5 Service Pack 5a, refer to the following article in the Microsoft Knowledge Base:
197177 INF: How to Obtain SQL Server 6.5 Service Pack 5a
If you already have SQL Server 6.5 SP5 or SP5a installed, you can download the Post SP5a Update from the following article in the Microsoft Knowledge Base:
274036 INF: How to Obtain SQL Server 6.5 Post Service Pack 5a Update
For more information, contact your primary support provider.