PRB: Dumping to a New Dump Device Using INIT Option Causes a Dbsvolopen Error
Article ID: 176726
Article Last Modified on 10/3/2003
APPLIES TO
- Microsoft SQL Server 6.5 Standard Edition
This article was previously published under Q176726
SYMPTOMS
If you create a new disk dump device and then dump to the new disk dump
device using the INIT option, a dbsvolopen error may be written to the SQL
Server error log.
The dump completes successfully, however, the following entry is written to
the error log:
97/10/17 11:00:39.73 kernel dbsvolopen: Backup device
'C:\MSSQL\BACKUP\rajbak.DAT' failed to open, operating system error =
2(The system cannot find the file specified.)
CAUSE
Microsoft SQL Enterprise Manager issues a LOAD HEADERONLY statement every
time a database dump is initiated with the Initialize Device option
selected. This is done to check whether the dump device has previous dumps
which might be erased. However, because a new disk dump device does not
exist until the first dump is completed, the dbsvolopen error is written
into the error log.
WORKAROUND
No action is required. This error message can safely be ignored.
Additional query words: SEM backup
Keywords: kberrmsg kbprb KB176726