FIX: Unable to Reload Master DB After Upgrading SQL Server

ID: Q158684

The information in this article applies to:

Microsoft SQL Server version 6.5

BUG #: 16103 (6.5)

SYMPTOMS

In certain environments, a dump of the master database created after an upgrade from SQL Server version 6.0 to SQL Server 6.5 cannot be used to re-create the master database after a system failure. In such a case, rebuilding the master device and loading the latest master dump will shut down the server as expected, however, a subsequent restart of the server will fail. At the end of the errorlog, you will find the following message:


   Getpage: bstat=0x1008/0, sstat=0x80000000, disk
      pageno is/should be: objid is/should be:
      0x211(529)      0x1(1)
      0x211(529)      0x2d(45)
   ... extent objid 0x1, mask 0xff/0, next/prev=0x210/0x210

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.5. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server version 6.5. For more information, contact your primary support provider.

MORE INFORMATION

This problem occurs if SQL Server was installed with the default values for the sort order and code page (nocase/iso_1). To check this, run the following statements in the master database:


   select substring(textptr(definition),1,4)
   from syscharsets where name = 'nocase'

If the result of this statement is not 0x11020000, you will likely have the problem described when reloading the master database.

This problem does not occur with sort order bin_cp850. Other combinations have not been verified.

Additional query words: fail cannot load


Keywords          : kbsetup SSrvInst kbbug6.50 
Version           : 6.5
Platform          : WINDOWS 
Issue type        : kbbug

Last Reviewed: April 4, 1999