BUG: DBCC DBREINDEX Can Fail With Msg 603 After Msg 1105

ID: Q225536

The information in this article applies to:

Microsoft SQL Server version 6.5

BUG #: 17876 (SQLBUG_65)

SYMPTOMS

If DBCC DBREINDEX fails with error 1105 on a data segment it can encounter message 603 in a endless loop. Even if the client is disconnected, the server continues to raise message 603 until the Sqlservr.exe process is terminated (you will not be allowed to shutdown the server normally). The ERRORLOG continually shows message 603 like this:

Error: 603, Severity: 19, State: 1
Error: 603, Severity: 19, State: 1
Error: 603, Severity: 19, State: 1
Error: 603, Severity: 19, State: 1
Error: 603, Severity: 19, State: 1

This problem does not occur if DBCC DBREINDEX fails with error 1105 on the log segment.

WORKAROUND

Make sure that adequate database space exists before executing DBCC DBREINDEX.

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 6.5.

MORE INFORMATION

No text for the message 603 is written to the ERRORLOG. The standard text for message 603 should be as follows:

There are not enough system session descriptors available to run this query. The maximum number available to a process is %d. Split query and rerun.

Additional query words:

Keywords : kbbug6.50 kbSQLServ650bug
Version : winnt:6.5
Platform : winnt
Issue type : kbbug