BUG: Logging in After DISK REFIT Causes GP Fault

• Microsoft SQL Server version 4.2 for OS/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)

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.