FIX: Load and Recovery of a Read-Only Database May Cause AV (163047)
The information in this article applies to:
- Microsoft SQL Server 6.0
- Microsoft SQL Server 6.5
This article was previously published under Q163047
BUG #: 15671 (Windows NT: 6.0)
SYMPTOMS
When you run either a LOAD DATABASE or a LOAD TRANSACTION command on a read-
only database after restarting the SQL Server, you may receive a handled
access violation (AV) or SQL Server may stop responding. You may also find
the following errors in the SQL Server errorlog:
bufdiscard: warning, page 8448 (bp 0x945000) is hashed stat0x1064/0,
bhash=0x942d80
getindex: bp not special, ipageno = 0, bpageno = 0x18, stat = 0/0
kernel WARNING: Process being freed while holding Dataserver semaphore
WORKAROUND
Do not use the read-only option when loading a database or transaction log
dump. Note that simply disabling this option before loading does not
resolve the problem. If a database has been marked read-only and you need
to load a database dump, you must first drop and re-create that database.
STATUS
Microsoft has confirmed this to be a problem in Microsoft SQL Server
versionS 6.0 and 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.
Modification Type: | Major | Last Reviewed: | 10/16/2003 |
---|
Keywords: | kbBug kbenv kbfix kbusage KB163047 |
---|
|