Knowledge Base

BUG: You may receive the "Server: Msg 8929" error message or the "Server: Msg 8968" error message when you run a maintenance plan or a command that examines the integrity of the database in SQL Server 2000

Article ID: 892803

Article Last Modified on 11/2/2007

APPLIES TO

Microsoft SQL Server 2000 Developer Edition
Microsoft SQL Server 2000 Enterprise Edition
Microsoft SQL Server 2000 Personal Edition
Microsoft SQL Server 2000 Standard Edition

SQL Server 8.0: 362568

SYMPTOMS

In Microsoft SQL Server 2000, you may receive error messages when you use one of the following procedures:

You run a maintenance plan that examines the integrity of the database.
You manually run the DBCC CHECKALLOC command or the DBCC CHECKDB command.

The error messages that you may receive are similar to the following:

Server: Msg 8929, Level 16, State 1, Line 2 Object ID 2: Errors found in text ID 1409482752 owned by data record identified by RID = (1:24:0) id = 1 and indid = 1.

Server: Msg 8968, Level 16, State 10, Line 1 Table error: IAM page (1:48271) (object ID 2, index ID 255) is out of the range of this database.

Note In these error messages, object ID 2 is the object ID of the sysindexes table.

Note You may not receive error message 8968 if the maintenance plan, the DBCC CHECKALLOC command, or the DBCC CHECKDB command report more than 200 errors. If you do not receive error message 8968, run the following statement in Query Analyzer:

DBCC CHECKDB (DatabaseName) WITH ALL_ERRORMSGS, NO_INFOMSGS

If error message 8968 appears in the complete list of errors that this statement generates, you may have encountered the problem that is described in this article.

CAUSE

This error occurs rarely when you enable the option to remove unused space from your database files to update data optimization information in your maintenance plan. This option runs the DBCC SHRINKDATABASE command to reduce the size of the database.

Note You may also receive these errors when you manually run the DBCC SHRINKDATABASE command or the DBCC SHRINKFILE command.

WORKAROUND

To prevent this problem, use both of the following methods:

Method 1: Disable the Remove unused space from database files option in your maintenance plan. To disable this option, follow these steps:
1. Start SQL Server Enterprise Manager.
2. Expand your instance of SQL Server, expand Management, and then expand Database Maintenance Plans.
3. In the right panel, right-click your maintenance plan, and then click Properties.
4. Click the Optimizations tab, click to clear the Remove unused space from database files check box, and then click OK.
Method 2: Avoid manually running the DBCC SHRINKDATABASE command or the DBCC SHRINKFILE command.

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

To prevent the errors that are mentioned in the "Symptoms" section, increase the size of the database file. To do this, follow these steps:

Start SQL Server Enterprise Manager.
Expand your instance of SQL Server, and then expand Database.
Right-click your database, and then click Properties.
Click the Data Files tab, and then enter a larger size for your database file in the Space allocated (MB) column
Click OK.

Note These errors do not cause problems with the operations of SQL Server 2000. They do not cause access violations or a loss of the connection to the server.

Note You cannot fix these errors by running the repair options of the CHECKALLOC command or of the DBCC CHECKDB command.

REFERENCES

For additional information about the Index Allocation Map (IAM), see the "Managing Space Used by Objects" topic in SQL Server Books Online: For additional information about autogrow and autoshrink configuration, click the following article number to view the article in the Microsoft Knowledge Base:

315512 Considerations for autogrow and autoshrink configuration

Keywords: kbbug KB892803

Microsoft KB Archive/892803

Contents