Microsoft KB Archive/97901

{|
 * width="100%"|

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

  Drop each database which had space allocated on the device(s). If any of those databases are marked &quot;suspect,&quot; use the following command to drop each database: dbcc dbrepair (, dropdb)  Issue an &quot;sp_dropdevice &quot; for each deleted device. Quit and restart SQL Server. Re-create the device(s) and the database(s). 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.
 * }

-

Last reviewed: April 28, 1997

© 1998 Microsoft Corporation. All rights reserved. Terms of Use.