public:8088_issue:sqlite_corrupt_the_database_disk_image_is_malformed
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
public:8088_issue:sqlite_corrupt_the_database_disk_image_is_malformed [2020/10/21 18:49] yuk.cheng [Resolution] |
public:8088_issue:sqlite_corrupt_the_database_disk_image_is_malformed [2021/12/14 02:31] (current) anna.olalia |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ===== ISSUE: [SQLITE_CORRUPT] The database disk image is malformed (database disk image is malformed) ===== | + | ===== [V8] ISSUE: [SQLITE_CORRUPT] The database disk image is malformed (database disk image is malformed) ===== |
| <html> | <html> | ||
| Line 10: | Line 10: | ||
| Reviewed: | Reviewed: | ||
| </b> | </b> | ||
| - | 21/10/2020 | + | 2020-10-21 |
| - | <br/> | + | <br> |
| + | <br> | ||
| <b> | <b> | ||
| Product Version: | Product Version: | ||
| </b> | </b> | ||
| <br/> | <br/> | ||
| - | AhsayOBM/AhsayACB: 8.3.0.30 or above | + | AhsayACB / AhsayOBM: 8.3.0.30 to 8.x |
| <br/> | <br/> | ||
| OS: All | OS: All | ||
| Line 22: | Line 23: | ||
| ===== Problem Description ===== | ===== Problem Description ===== | ||
| <html> | <html> | ||
| - | When performing a backup job on AhsayOBM\AhsayACB. The following error message is received in the backup report : | + | 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/> | <br/> | ||
| <table border="0" cellpadding="0" cellspacing="0" width="850"> | <table border="0" cellpadding="0" cellspacing="0" width="850"> | ||
| Line 97: | Line 98: | ||
| ===== Cause ===== | ===== Cause ===== | ||
| <html> | <html> | ||
| - | This error is caused by a corrupted index file on the backup set.</br> | + | This issue can occurs if there is a corrupted index file on the backup set.</br> |
| </br> | </br> | ||
| These are many factors that could trigger a backup set index corruption: | These are many factors that could trigger a backup set index corruption: | ||
| </br> | </br> | ||
| <ul> | <ul> | ||
| - | <li><font color=black>The machine where the backup job is running was previously shutdown or rebooted when a backup was still in progress.</li> | + | <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>There is a disk issue on the machine where the backup is running.</li> | + | <li><font color=black>Disk issue on the computer where the backup is performed.</li> |
| - | <li><font color=black>If the temporary folder is on a network drive, an unstable network connection between the backup machine and network drive.</li> | + | <li><font color=black>Unstable network connection between the backup computer and network temp folder.</li> |
| - | <li><font color=black>AhsayOBM/AhsayACB application crashed during a previous backup job.</li> | + | <li><font color=black>Backup client application crashed during a previous backup.</li> |
| - | <li><font color=black>AhsayOBM/AhsayACB encountered an out of memory or "Java Heap Size" error during a previous backup job.</li> | + | <li><font color=black>Backup client application encountered an out of memory or "Java Heap Size" error during a previous backup.</li> |
| </ul> | </ul> | ||
| </html> | </html> | ||
| Line 112: | Line 113: | ||
| ===== Resolution ===== | ===== Resolution ===== | ||
| <html> | <html> | ||
| - | To workaround this issue it is recommended to: | + | To workaround this issue, it is recommended to: |
| </br></br> | </br></br> | ||
| First, try deleting the current index files from the temporary folder on the backup machine.</br> | First, try deleting the current index files from the temporary folder on the backup machine.</br> | ||
| <ul> | <ul> | ||
| - | <li><font color=black>Make sure there are no backup and restore jobs are running.</li> | + | <li><font color=black>Make sure there is no backup / restore job running.</li> |
| - | <li><font color=black>Go to the folder <b>%temporary_folder_path%\%BackupSetID%\</b></li> | + | <li><font color=black>Browse to the folder %temp_folder_path%\%backupSetID%\</li> |
| - | <li><font color=black>Delete all contents of the folder <b>%temporary_folder_path%\%BackupSetID%\</b></li> | + | <li><font color=black>Delete all contents in the folder</li> |
| - | <li><font color=black>Run the backup job again</li> | + | <li><font color=black>Perform the backup job again</li> |
| </ul> | </ul> | ||
| - | If the SQLITE_CORRUPT error continues after the backup job is run again, then it is recommended to use the second workaround: | + | If the SQLITE_CORRUPT error persist, then it is recommended to use the following workaround: |
| - | </br></br> | + | |
| - | Revert the index files on the affected backup set to a previous healthy version. <b>The version should be no more than two days from the last occurrence of the SQLITE_CORRUPT error.</b> | + | |
| - | </br></br> | + | |
| - | <u>For example:</u></br> | + | |
| - | If the destination is on an AhsayCBS backup server and you want to revert to a previous good snapshot on <b>2020-10-19-15-00-28</b> on backup set <b>1595563417075</b> | + | |
| - | </br></br> | + | |
| - | Copy the following index files from: | + | |
| - | </br></br> | + | |
| - | %CBS_USER_HOME%\username\1595563417075\blocks\2020-10-19-15-00-28\<b>index.db.8d000.1754aa9d758.cgz</b></br> | + | |
| - | %CBS_USER_HOME%\username\1595563417075\blocks\2020-10-19-15-00-28\<b>index.db.id229637a.115b0i.8d000.1754aa9d758.cgz</b></br> | + | |
| </br> | </br> | ||
| - | To the current folder: | + | <br> |
| - | </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).  The version should be no more than two days from the last occurrence of the SQLITE_CORRUPT error. |
| - | <b>%CBS_USER_HOME%\username\1595563417075\blocks\</b> | + | <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> | </html> | ||
| ===== Keywords ===== | ===== Keywords ===== | ||
| - | index corrupted, Java Heap Size, disk issue, AhsayOBM/AhsayACB application crash | + | index corrupted, java, heap, size, disk, corrupt, issue, crash |
public/8088_issue/sqlite_corrupt_the_database_disk_image_is_malformed.1603277386.txt.gz · Last modified: 2020/10/21 18:49 by yuk.cheng