Microsoft KB Archive/225536

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

Article ID: 225536

Article Last Modified on 9/25/2003

-

APPLIES TO


 * Microsoft SQL Server 6.5 Standard Edition

-



This article was previously published under Q225536



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 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.

Keywords: kbbug kbpending KB225536

-

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

© Microsoft Corporation. All rights reserved.