PRB: LOAD HEADERONLY May Fail to Return All Rows

Last reviewed: June 24, 1997
Article ID: Q158786
The information in this article applies to:
  • Microsoft SQL Server, version 6.5

SYMPTOMS

A LOAD HEADERONLY operation directed against a tape drive may fail to return any rows, or the correct number of rows, for the dumps on a tape device.

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.

MORE INFORMATION

The following error will be seen in the SQL Server errorlog:

   read_db_hdr: Read failure on backup device '\\.\tape0',
   returned operating system error 1106 (When accessing a
   new tape of a multivolume partition, the current
   blocksize is incorrect.)

If there is only a single dump on the tape, the LOAD HEADERONLY will return zero rows. If there are subsequent dumps on the tape, the LOAD HEADERONLY operation will find the dumps, as can be seen by looking at the sequence number. The dump can still be loaded if the file number is known.

The problem appears to be specific to quarter-inch cartridge (QIC) tape drives.


Keywords : kbhw kbother kbusage SSrvAdmin
Version : 6.5
Platform : WINDOWS
Issue type : kbprb
Resolution Type : kbpending


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: June 24, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.