BUG: DUMP TRAN May Fail with No Error to the User

 Last reviewed: April 29, 1997
Article ID: Q111959

The information in this article applies to:
  • Microsoft SQL Server version 4.2 for OS/2
  • Microsoft SQL Server, version 4.2
BUG# OS/2: 1832(4.2) 
       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 SQL Server version 4.2 for OS/2 and 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 TRAN
Keywords : kbbug4.20 kbprg SSrvGen SSrvServer SSrvWinNT
Version : 4.2 | 4.2
Platform : OS/2 WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 29, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.