BUG: DUMP TRAN May Fail with No Error to the User |
Q111959
The information in this article applies to:
- Microsoft SQL Server version 4.2x
BUG# NT: 680(4.2)
SYMPTOMS
The DUMP TRAN <dbname> TO <dumpdevice> command may fail due to some hardware device related error; however, no error is returned to the user. There may or may not be entries made in the errorlog, but the entries usually indicate only that there are device problems, not DUMP TRAN problems.
For instance, if a drive is full, these entries might appear as:
dbsspacket: cannot flush buffer
dbsclose: cannot flush buffer
on a networked disk device, or on a local disk as:
dbswrite: Write failure on backup device '...' returned
operating system error ...
Additionally, if this problem occurs, transaction log dumps performed after the failed one will succeed normally, but will be prevented from being loaded because they are out of sequence; therefore, they are useless.
STATUS
Microsoft has confirmed this to be a problem in Microsoft SQL Server version 4.2. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
Additional query words: DUMP TRAN LOAD
Keywords : kbprogramming
Issue type :
Technology : kbSQLServSearch kbAudDeveloper kbSQLServ420OS2
Last Reviewed: March 7, 2000 |
