✎ [V8] ISSUE: [SQLITE_CORRUPT] The database disk image is malformed (database disk image is malformed) [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.
===== [V8] ISSUE:  [SQLITE_CORRUPT] The database disk image is malformed (database disk image is malformed)  =====

<html>
 <b>
  Article ID:
 </b>
 8088
 <br/>
 <b>
  Reviewed:
 </b>
 2020-10-21
 <br>
<br>
 <b>
  Product Version:
 </b>
 <br/>
 AhsayACB / AhsayOBM: 8.3.0.30 to 8.x 
 <br/>
 OS: All
</html>
===== Problem Description =====
<html>
When performing a backup job of any type on the AhsayOBM / ACB client application, 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>
  <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">
    YYYY/MM/DD
     hh:mm:ss
   </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>
   <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>
      [SQLITE_CORRUPT]  The database disk image is malformed (database disk image is malformed)
    </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>
This issue can occurs if there is a corrupted index file on the backup set.</br>
</br>
These are many factors that could trigger a backup set index corruption:
</br>
<ul>
<li><font color=black>The machine where the backup job is running was previously shutdown / rebooted when a backup job was still running.</li>
<li><font color=black>Disk issue on the computer where the backup is performed.</li>
<li><font color=black>Unstable network connection between the backup computer and network temp folder.</li>
<li><font color=black>Backup client application crashed during a previous backup.</li> 
<li><font color=black>Backup client application encountered an out of memory or "Java Heap Size" error during a previous backup.</li>
</ul>
</html>

===== Resolution =====
<html>
To workaround this issue, it is recommended to: 
</br></br>
First, try deleting the current index files from the temporary folder on the backup machine.</br>
<ul>
<li><font color=black>Make sure there is no backup / restore job running.</li>
<li><font color=black>Browse to the folder %temp_folder_path%\%backupSetID%\</li>
<li><font color=black>Delete all contents in the folder</li>
<li><font color=black>Perform the backup job again</li> 
</ul>
If the SQLITE_CORRUPT error persist, then it is recommended to use the following workaround:
</br>
<br>
Revert the set of index files on the affected backup set to a previous healthy version (e.g. check on the backup report to locate the last successful backup). &nbsp;The version should be no more than two days from the last occurrence of the SQLITE_CORRUPT error.
<br>
<br>
Example:</br> 
If the destination is on an AhsayCBS backup server, and you would like to revert to a previous good snapshot on "2020-10-19-15-00-28" for backup set with ID "1595563417075"
<br>
<br>
Copy the index files from:
<br>
<br>
${User_Home}\username\1595563417075\blocks\2020-10-19-15-00-28\<font color=red>index.db.8d000.1754aa9d758.cgz</font></br>
${User_Home}\username\1595563417075\blocks\2020-10-19-15-00-28\<font color=red>index.db.id229637a.115b0i.8d000.1754aa9d758.cgz</font></br>
<br>
To 
<br>
<br>
${User_Home}\username\1595563417075\blocks\


</html>

===== Keywords =====
index corrupted, java, heap, size, disk, corrupt, issue, crash
User Tools

Site Tools

Page Tools
