BUG: Logging in After DISK REFIT Causes GP FaultLast reviewed: April 28, 1997Article ID: Q97901 |
The information in this article applies to:
SYMPTOMSIf a database device file has been deleted or is otherwise inaccessible, and the SA issues a DISK REFIT command, SQL Server may return the following two errors:
Could not find row in Sysdatabases with database id <db id>. Run DBCC CHECKTABLE on Sysdatabases (Msg 913, Sev 22, State 1) Could not start I/O for request (Msg 822, Sev 21, State 1)The user connection is then terminated. With SQL Server 1.11, attempting to re-establish the connection to SQL Server may cause the front-end (such as ISQL or SAF) to general protection fault (GP fault). With SQL Server 4.2, attempting to re-establish the connection may cause SQL Server to GP fault.
CAUSESQL Server incorrectly handles the DISK REFIT command when a database resides on a device that is no longer accessible.
WORKAROUNDIf one or more device files have been deleted, do the following to restore the affected database(s):
STATUSMicrosoft has confirmed this to be a problem in SQL Server version 4.2 for OS/2. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
|
Additional query words:
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |