✎ [V7] ISSUE: No database file found (MS SQL database backup) [Ahsay Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
===== [V7] ISSUE: No database file found (MS SQL database backup) =====

<html>
 <b>
  Article ID:
 </b>
 5318
 <br/>
 <b>
  Reviewed:
 </b>
 2018-03-13
 <br/>
 <br/>
 <b>
  Product Version:
 </b>
 <br/>
 AhsayOBM: 7.3.0.0 to 7.x 
 <br/>
 OS: Windows
</html>

<html>
<FONT COLOR=red SIZE=+1>
<B>ATTENTION</B>
1st January, 2022: v7 officially End-of-Life [<A HREF=https://wiki.ahsay.com/doku.php?id=public:announcement:ahsay_v7_eol>details</A>]
</FONT>
</html>
===== Problem Description =====
<html>
When performing a MS SQL database backup (ODBC backup mode), the following error message is received in the backup report:
 <br>
 <table border="0" cellpadding="0" cellspacing="0" width="850">
  <tr>
   <td bgcolor="#E8E8E8" style="BORDER-LEFT: #C0C0C0 1px solid; BORDER-TOP: #C0C0C0  1px solid; BORDER-BOTTOM: #C0C0C0 1px solid" valign="middle">
    No.
   </td>
   <td bgcolor="#E8E8E8" style="BORDER-LEFT: #C0C0C0 1px solid; BORDER-TOP: #C0C0C0  1px solid; BORDER-BOTTOM: #C0C0C0 1px solid" valign="middle">
    Type
   </td>
   <td bgcolor="#E8E8E8" style="BORDER-LEFT: #C0C0C0 1px solid; BORDER-TOP: #C0C0C0  1px solid; BORDER-BOTTOM: #C0C0C0 1px solid" valign="middle">
    Timestamp
   </td>
   <td bgcolor="#E8E8E8" style="BORDER-LEFT: #C0C0C0 1px solid; BORDER-TOP: #C0C0C0 1px solid; BORDER-RIGHT: #C0C0C0 1px solid; BORDER-BOTTOM: #C0C0C0 1px solid" valign="middle">
    Log
   </td>
  </tr>
  <tr>
   <td bgcolor="#ffffff" style="BORDER-LEFT: #C0C0C0 1px solid; BORDER-BOTTOM: #C0C0C0 1px solid" valign="top">
    *
   </td>
   <td bgcolor="#ffffff" style="BORDER-LEFT: #C0C0C0 1px solid; BORDER-BOTTOM: #C0C0C0 1px solid" valign="top">
    ...
   </td>
   <td bgcolor="#ffffff" style="BORDER-LEFT: #C0C0C0 1px solid; BORDER-BOTTOM: #C0C0C0 1px solid" valign="top">
    ...
   </td>
   <td bgcolor="#ffffff" style="BORDER-LEFT: #C0C0C0 1px solid; BORDER-RIGHT: #C0C0C0 1px solid; BORDER-BOTTOM: #C0C0C0 1px solid" valign="middle">
    ...
   </td>
  </tr>
    </tr>
    <tr>
   <td bgcolor="#ffffff" style="BORDER-LEFT: #C0C0C0 1px solid; BORDER-BOTTOM: #C0C0C0 1px solid" valign="top">
    *
   </td>
   <td bgcolor="#ffffff" style="BORDER-LEFT: #C0C0C0 1px solid; BORDER-BOTTOM: #C0C0C0 1px solid" valign="top">
    info
   </td>
   <td bgcolor="#ffffff" style="BORDER-LEFT: #C0C0C0 1px solid; BORDER-BOTTOM: #C0C0C0 1px solid" valign="top">
    ...
   </td>
   <td bgcolor="#ffffff" style="BORDER-LEFT: #C0C0C0 1px solid; BORDER-RIGHT: #C0C0C0 1px solid; BORDER-BOTTOM: #C0C0C0 1px solid" valign="middle">
    No full file found for in-file delta backup files. Path="SQL_hostname\...\db_name.bak".
   </td>
  </tr>
  <tr>
   <td bgcolor="#ffffff" style="BORDER-LEFT: #C0C0C0 1px solid; BORDER-BOTTOM: #C0C0C0 1px solid" valign="top">
    *
   </td>
   <td bgcolor="#ffffff" style="BORDER-LEFT: #C0C0C0 1px solid; BORDER-BOTTOM: #C0C0C0 1px solid" valign="top">
     <font color=red>erro</font>
   </td>
   <td bgcolor="#ffffff" style="BORDER-LEFT: #C0C0C0 1px solid; BORDER-BOTTOM: #C0C0C0 1px solid" valign="top">
     <font color=red>YYYY/MM/DD hh:mm:ss</font>
   </td>
   <td bgcolor="#ffffff" style="BORDER-LEFT: #C0C0C0 1px solid; BORDER-RIGHT: #C0C0C0 1px solid; BORDER-BOTTOM: #C0C0C0 1px solid" valign="middle">
   <font color=red>No database file found for "SQL_hostname\...\db_name"</font>
   </td>
  </tr>   
  <tr>
   <td bgcolor="#ffffff" style="BORDER-LEFT: #C0C0C0 1px solid; BORDER-BOTTOM: #C0C0C0 1px solid" valign="top">
    *
   </td>
   <td bgcolor="#ffffff" style="BORDER-LEFT: #C0C0C0 1px solid; BORDER-BOTTOM: #C0C0C0 1px solid" valign="top">
    ...
   </td>
   <td bgcolor="#ffffff" style="BORDER-LEFT: #C0C0C0 1px solid; BORDER-BOTTOM: #C0C0C0 1px solid" valign="top">
    ...
   </td>
   <td bgcolor="#ffffff" style="BORDER-LEFT: #C0C0C0 1px solid; BORDER-RIGHT: #C0C0C0 1px solid; BORDER-BOTTOM: #C0C0C0 1px solid" valign="middle">
    ...
   </td>
  </tr>
 </table>
</html>

===== Cause =====
<html>
The message suggests that the database file of the corresponding database cannot be found in the backup destination, possible cause may be:
<br>
<ul>
<li><font color=black>Data corruption in the backup destination
<br>Corrupted file (data blocks of the database file) deleted by the data integrity check.</font></li><br>
<li><font color=black>Backup issue during a previous backup job
<br>Database file was not properly uploaded to the backup destination during a previous backup.</font></li>
</ul>
</html>


===== Resolution =====
<html>
To resolve the issue, refer to the following steps:

<ul>
<li><font color=black>Data corruption:
<br>
<br>
Check if there is hardware or I/O issue with the corresponding backup destination.
<br>
<br>
<font size=2>
<ul>
<li><font color=black><u>Windows</u>
<br>
For backup destination that are located on a Windows computer, check in the Event Viewer to confirm if there is any error. &nbsp;If a disk error is found, perform a check disk on the affected partition by entering the following command in command prompt.
<br>
<br>
<table border="0" cellpadding="0" cellspacing="0" width="600">
  <tr>
   <td bgcolor="#00000" valign="top">
    <font color=#FFFFFF>chkdsk /f</font>
   </td>
  </tr>
</table>
</font>
</li>

<li><font color=black><u>Linux</u>
<br>
For backup destination that are located on a Linux computer, confirm if there is any error found: 
<br>
<br>
<table border="0" cellpadding="0" cellspacing="0" width="600">
  <tr>
   <td bgcolor="#00000" valign="top">
    <font color=#FFFFFF>cat /var/log/messages</font>
   </td>
  </tr>
</table>

If a disk error is found, perform a check disk on the affected partition by enter the following commands with the partition un-mount. 

<br>
<br>
<table border="0" cellpadding="0" cellspacing="0" width="600">
  <tr>
   <td bgcolor="#00000" valign="top">
    <font color=#FFFFFF>/sbin/fsck</font>
   </td>
  </tr>
</table>

<table border="0" cellpadding="0" cellspacing="0" width="600">
  <tr>
   <td bgcolor="#00000" valign="top">
    <font color=#FFFFFF>/sbin/e2fsck</font>
   </td>
  </tr>
</table>

</font>
</li>
<li><font color=black><u>Network volume</u>
<br>
For backup destination on a network volume, ensure that a stable connection can be established between the backup client and destination for the duration of a backup.</font></li>
</ul>
</font>
<br>
</li>
<li><font color=black>Backup issue during a previous backup job:
<br>
<br>
Check on the previous backup reports for any error, or contact <a href="https://www.ahsay.com/jsp/en/contact/kbQuestion.jsp">Ahsay support representatives</a> for further assistance.</li>
</ul>
For both cases, perform a Data Integrity Check for the affected backup set (<a href="http://wiki.ahsay.com/doku.php?id=public:5004_how_to_run_a_data_integrity_check
">Instruction</a>), then perform a <b>Full</b> database backup afterward.
<br>
<br>
   <div class="inline-attachment">
    <dl>
     <dt class="attach-image">
      <img style="width:80%" src="http://wiki.ahsay.com/lib/exe/fetch.php?media=public:SQL_full_backup.png">
     </dt>
    </dl>
   </div>


<b><font color=red>Important:</font></b>
<br>
The same error will still be displayed during the next Full database backup job, the problem will be resolved after the database file is uploaded properly. Do not interrupt the database backup job when an error is displayed.


</html>
===== Keywords =====
sql, odbc, require, required, miss, missed, missing
User Tools

Site Tools

Page Tools
