BUG: Loading Database Dumps Spanning Tapes Fails

Last reviewed: April 9, 1997
Article ID: Q158328
The information in this article applies to:
  • Microsoft SQL Server, version 6.5
BUG #: 16147 (6.5)

SYMPTOMS

When you attempt to load a dump that spans tapes, the load may fail, and you may receive the following errors:

   Msg 4032, Level 16, State 2
   Cannot find file 10 on tape 'SS0001'.

   Msg 3203, Level 16, State 2
   Read on dump device '\\.\TAPE0' failed, vsn=0 return=-2 status=-2.
   Please consult the SQL Server error log for more details.

   Msg 3103, Level 16, State 1
   Unexpected end-of-dump while loading database, attempting to continue.
   Please verify database integrity.

This problem occurs if both of the following are true:
  • One of the tapes that the dump continued or spanned onto already contains a SQL Server dump.
  • The NOINIT option (the default option) was used on the dump that created the tapes.

WORKAROUND

To work around this problem, do one of the following:

  • Always make sure that the tapes you are using are blank.
  • Use the INIT option on the DUMP DATABASE command, so that the spanned tapes are overwritten.
  • Use tapes that supply more backup capacity than you require, so that spanning is not necessary.
  • Use stripe dumps to multiple tape devices, so that spanning is not necessary.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.5. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.


Additional query words: continue console mount 4028
Keywords : kbbug6.50 kbother SSrvAdmin SSrvGen
Version : 6.5
Platform : 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 9, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.