Microsoft KB Archive/872842

= FIX: A CHECKDB statement reports a 2537 corruption error after SQL Server transfers data to a sql_variant column in SQL Server 2000 =

Article ID: 872842

Article Last Modified on 11/2/2007

-

APPLIES TO


 * Microsoft SQL Server 2000 Developer Edition
 * Microsoft SQL Server 2000 Standard Edition
 * Microsoft SQL Server 2000 Enterprise Edition
 * Microsoft SQL Server 2000 Personal Edition
 * Microsoft SQL Server 2000 Enterprise Edition
 * Microsoft SQL Server 2000 Workgroup Edition
 * Microsoft SQL Server 2000 Desktop Engine (Windows)
 * Microsoft SQL Server 2000 Developer Edition
 * Microsoft SQL Server 2000 Enterprise Edition 64-bit

-



Bug #: 471784 (Shiloh_bugs)

Bug #: 471793 (Shiloh_bugs)

Bug #: 361832(Shiloh_bugs)



Article contents

 * Summary
 * Symptoms
 * Resolution
 * Hotfix information
 * Prerequisites
 * Restart information
 * Hotfix file information
 * Status
 * More Information



SUMMARY
This article describes the following about this hotfix release:
 * The issues that are fixed by this hotfix package.
 * The prerequisites for installing the hotfix package.
 * Whether you must restart your computer after you install the hotfix package.
 * Whether the hotfix package is replaced by any other hotfix package.
 * Whether you must make any registry changes.
 * The files that are contained in the hotfix package.

back to the top



SYMPTOMS
A DBCC CHECKDB statement may report consistency errors in your database when all the following conditions are true:
 * SQL Server loads data to a column that is a sql_variant data type.
 * The data originates in another column that is a sql_variant data type, and at some point the data is sent on-the-wire by SQL Server.
 * The data is sent either directly to another server that is running SQL Server or to an intermediate file.
 * The sql_variant column contains character values.

Here are some examples of statements that could cause this behavior:
 * A bcp or a BULK INSERT statement from a file that was originally created by a SELECT statement or a BCP IN command from SQL Server.
 * A data load that is using Data Transformation Services.
 * A data load that is using SQL Server DMO Transfer Object.

The corruption error that is raised by DBCC CHECKDB is as follows:

 Msg 2537, Level 16, State 43, Server MYSERVER, Line 1 Table error: Object ID 1977058079, index ID 0, page (1:75), row 0. Record check (Valid SqlVariant) failed. Values are 4 and 0. DBCC results for 'MyTable'. There are 0 rows in 1 pages for object 'MyTable'.

CHECKDB found 0 allocation errors and 1 consistency errors in table 'MyTable' (object ID 1977058079).

CHECKDB found 0 allocation errors and 1 consistency errors in database 'MyReproDest'. repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (MyReproDest ). Note Even with the corruption error, you can still select the data for the row that reports the corruption error without any problems. But if you run the REPAIR_ALLOW_DATALOSS option, the row that reports the corruption may be deleted. Applying the hotfix that is mentioned in the &quot;Resolution&quot; section corrects the corruption and you do not have to run any repair options that may cause data loss.

For a list of previous hotfixes, see the &quot;Microsoft SQL Server 2000 post-Service Pack 3 or Microsoft SQL Server 2000 post-Service Pack 3a hotfixes&quot; section in the following Microsoft Knowledge Base article:

290211 How to obtain the most recent SQL Server 2000 service pack

back to the top



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

290211 How to obtain the latest SQL Server 2000 service pack

Prerequisites
This hotfix requires Microsoft SQL Server 2000 Service Pack 3 (SP3). For information about how to obtain SQL Server 2000 SP3, see the following article in the Microsoft Knowledge Base:

290211 How to obtain the most recent SQL Server 2000 Service Pack

back to the top

Restart information
You do not have to restart your computer after you apply this hotfix.

back to the top

Hotfix file information
This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.

The English version of this hotfix has the file attributes (or later file attributes) 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 -  18-Aug-2004  01:55  2000.80.970.0     664,128  Autoplt.dll 18-Aug-2004 01:55  2000.80.970.0      78,400  Console.exe 18-Aug-2004 01:55  2000.80.970.0     332,352  Ctasksui.dll 18-Aug-2004 01:55  2000.80.970.0     315,968  Custtask.dll 18-Aug-2004 01:55  2000.80.970.0      33,340  Dbmslpcn.dll 08-Apr-2004 21:42                    786,432  Distmdl.ldf 08-Apr-2004 21:42                  2,359,296  Distmdl.mdf 10-Oct-2003 18:48                        180  Drop_repl_hotfix.sql 18-Aug-2004 01:55  2000.80.970.0   1,905,216  Dtspkg.dll 18-Aug-2004 01:55  2000.80.970.0     528,960  Dtspump.dll 18-Aug-2004 01:55  2000.80.970.0   1,557,052  Dtsui.dll 18-Aug-2004 01:55  2000.80.970.0     639,552  Dtswiz.dll 10-Oct-2003 18:48                    747,927  Instdist.sql 10-Oct-2003 18:48                      1,581  Inst_repl_hotfix.sql 18-Aug-2004 01:55  2000.80.970.0     352,828  Isqlw.exe 18-Aug-2004 01:55  2000.80.970.0      82,492  Itwiz.exe 18-Aug-2004 01:55  2000.80.970.0      90,692  Msgprox.dll 19-May-2004 23:43  8.11.40209.0      209,408  Mssdi98.dll 18-Aug-2004 01:55  2000.80.970.0      62,024  Odsole70.dll 18-Aug-2004 01:56  2000.80.970.0      25,144  Opends60.dll 18-Aug-2004 01:55  2000.80.970.0      57,904  Osql.exe 18-Aug-2004 01:55  2000.80.970.0     279,104  Pfutil80.dll 10-Oct-2003 18:37                    550,780  Procsyst.sql 08-Apr-2004 21:42                     12,305  Qfe469315.sql 08-Apr-2004 21:42                     19,195  Qfe469571.sql 18-Aug-2004 00:26                      5,155  Qfe472197.sql 18-Aug-2004 01:55  2000.80.970.0     143,940  Qrdrsvc.exe 18-Aug-2004 02:16                  1,105,167  Replmerg.sql 18-Aug-2004 01:55  2000.80.970.0     221,768  Replprov.dll 18-Aug-2004 01:55  2000.80.970.0     307,784  Replrec.dll 18-Aug-2004 00:46  2000.80.970.0     159,813  Replres.rll 18-Aug-2004 00:26                  1,086,925  Replsys.sql 10-Oct-2003 18:48                    986,603  Repltran.sql 18-Aug-2004 01:55  2000.80.970.0     287,304  Rinitcom.dll 18-Aug-2004 01:55  2000.80.970.0      78,416  Sdiclnt.dll 18-Aug-2004 01:55  2000.80.970.0      66,112  Semmap.dll 18-Aug-2004 01:55  2000.80.970.0      57,916  Semnt.dll 18-Aug-2004 01:55  2000.80.970.0     492,096  Semobj.dll 18-Aug-2004 01:20  2000.80.970.0     172,032  Semobj.rll 18-Aug-2004 01:55  2000.80.970.0      53,832  Snapshot.exe 13-Jul-2004 20:59                    117,834  Sp3_serv_uni.sql 18-Aug-2004 01:54  2000.80.970.0      28,672  Sqlagent.dll 18-Aug-2004 01:55  2000.80.970.0     311,872  Sqlagent.exe 18-Aug-2004 01:54  2000.80.970.0     168,001  Sqlakw32.dll 18-Aug-2004 01:55  2000.80.970.0      33,344  Sqlctr80.dll 18-Aug-2004 01:55  2000.80.970.0   4,215,360  Sqldmo.dll 18-Aug-2004 01:55                     25,172  Sqldumper.exe 18-Aug-2004 00:35  2000.80.970.0      28,672  Sqlevn70.rll 18-Aug-2004 01:55  2000.80.970.0     156,224  Sqlmaint.exe 18-Aug-2004 01:55  2000.80.970.0     180,792  Sqlmap70.dll 18-Aug-2004 01:55  2000.80.970.0     188,992  Sqlmmc.dll 18-Aug-2004 01:15  2000.80.970.0     479,232  Sqlmmc.rll 18-Aug-2004 01:55  2000.80.970.0     401,984  Sqlqry.dll 18-Aug-2004 01:55  2000.80.970.0      57,920  Sqlrepss.dll 18-Aug-2004 01:55  2000.80.970.0   7,581,777  Sqlservr.exe 18-Aug-2004 01:55  2000.80.970.0     590,396  Sqlsort.dll 18-Aug-2004 01:55  2000.80.970.0      45,644  Sqlvdi.dll 18-Aug-2004 01:55  2000.80.970.0     106,588  Sqsrvres.dll 18-Aug-2004 01:55  2000.80.970.0      33,340  Ssmslpcn.dll 18-Aug-2004 01:55  2000.80.970.0      82,492  Ssnetlib.dll 18-Aug-2004 01:55  2000.80.970.0      25,148  Ssnmpn70.dll 18-Aug-2004 01:55  2000.80.970.0     123,456  Stardds.dll 18-Aug-2004 01:55  2000.80.970.0     158,240  Svrnetcn.dll 18-Aug-2004 01:55  2000.80.970.0      76,416  Svrnetcn.exe 18-Aug-2004 01:55  2000.80.970.0      49,228  Ums.dll 18-Aug-2004 01:55  2000.80.970.0      98,872  Xpweb70.dll Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

back to the top



STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the &quot;Applies to&quot; section.

This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.

back to the top



MORE INFORMATION
For additional information about the naming schema for Microsoft SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:

822499 New naming schema for Microsoft SQL Server software update packages

For additional information about the terminology that Microsoft uses when correcting software after it is released, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

back to the top

Additional query words:

Keywords: kbbug kbfix kbqfe kbsqlserv2000presp4fix kbhotfixserver KB872842

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.