BUG: Logging in After DISK REFIT Causes GP Fault

Last reviewed: April 28, 1997
Article ID: Q97901

The information in this article applies to:
  • Microsoft SQL Server version 4.2 for OS/2
BUG# OS/2: 1634 (4.2)

SYMPTOMS

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

CAUSE

SQL Server incorrectly handles the DISK REFIT command when a database resides on a device that is no longer accessible.

WORKAROUND

If one or more device files have been deleted, do the following to restore the affected database(s):

  1. Drop each database which had space allocated on the device(s). If any of those databases are marked "suspect," use the following command to drop each database:

          dbcc dbrepair (<db name>, dropdb)
    

  2. Issue an "sp_dropdevice <device name>" for each deleted device.

  3. Quit and restart SQL Server.

  4. Re-create the device(s) and the database(s).

  5. Load the database(s) from dumps.

STATUS

Microsoft 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:
Keywords : kbother SSrvServer
Version : 4.2
Platform : OS/2
Issue type : kberrmsg


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 28, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.