The information in this article applies to:
BUG #: 18717 (SQLBUG_65) SYMPTOMSA 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: The following conditions must be true for this problem to occur:
RESOLUTIONA 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. http://www.microsoft.com/support/supportnet/overview/overview.aspThe English version of this fix should have the following file attributes or later: NOTE: Due to file dependencies, the most recent hotfix or feature that contains the above files may also contain additional files.WORKAROUNDTo work around this problem, instead of doing a DBCC DBREINDEX, perform an explicit DROP INDEX and CREATE INDEX for every index on the table. STATUSMicrosoft 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 |
Last Reviewed: November 2, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |