FIX: You may receive an assertion or database corruption may occur when you use the bcp utility or the "Bulk Insert" Transact-SQL command to import data in SQL Server 2000
Bug #: 50000914 (SQL Hotfix) Microsoft distributes Microsoft SQL Server 2000 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2000 fix release. On This PageSUMMARYThis article describes the following about this hotfix
release:
SYMPTOMSWhen you use the bcp utility or the Bulk Insert Transact-SQL command to import data in Microsoft SQL Server 2000, you may receive an assertion. Or, database corruption may occur. Additionally, you may receive the following error message: Server: Msg 823, Level 24, State 2, Procedure gfspTMAppendText, Line 20
I/O error (bad page ID) detected during read at offset 0x0000000024e000 in file 'C:\Program Files (x86)\Microsoft SQL Server\MSSQL\data\REPRO.mdf'.
You receive the following error messages in the SQL Server error log: Error message 1 DateTime spid53 SQL Server Assertion: File: <SpcAlloc.cpp>, line=466
Failed Assertion = '0'.
Error message 2 DateTime spid53 Error: 3624, Severity: 20, State: 1.
When you run the DBCC Checkdb command, you receive messages that resemble the following:Error message 1 Server: Msg 8909, Level 16, State 1, Line 1 Table error: Object ID 0, index ID 0, page ID (1:105). The PageId in the page header = (0:0). Error message 2
Server: Msg 8928, Level 16, State 1, Line 1 Object ID 2009058193, index ID 255: Page (1:105) could not be processed. See other errors for details.
This problem occurs if the following conditions are true:
894905 (http://support.microsoft.com/kb/894905/) Cumulative list of the hotfixes that are available for SQL Server 2000 SP4
RESOLUTIONHotfix informationA supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft SQL Server 2000 service pack that contains this hotfix.To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support) Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.PrerequisitesTo apply this hotfix, you must have SQL Server 2000 Service Pack 4 (SP4) installed on the computer. For more information about how to obtain SQL Server 2000 Service Pack 4, click the following article numberHow to obtain the latest SQL Server 2000 service pack to view the articleHow to obtain the latest SQL Server 2000 service pack in the Microsoft Knowledge Base:290211 (http://support.microsoft.com/kb/290211/) Restart informationYou do not have to restart the computer after you apply this hotfix.Registry informationYou do not have change the registry.Hotfix file informationThis hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of 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 item in Control Panel.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATION
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 (http://support.microsoft.com/kb/824684/)
Description of the standard terminology that is used to describe Microsoft software updates
APPLIES TO
| Article Translations
|
| United States | Change | | | All Microsoft Sites |
Help and Support
Back to the top
|
