User Tools

Site Tools


Sidebar

Announcement

Ahsay Backup Software

Backup Set Types

Supported Storage

Features in OBM / ACB

Features in CBS

Brand and Customize

License

Documentation

Performance Testing

FAQs and Known Issues

Can't Find What You Need?

public:8088_issue:sqlite_corrupt_the_database_disk_image_is_malformed

ISSUE: [SQLITE_CORRUPT] The database disk image is malformed (database disk image is malformed)

Article ID: 8088
Reviewed: 21/10/2020

Product Version:
AhsayACB / AhsayOBM: 8.3.0.30 or above
OS: All

Problem Description

When performing a backup job of any type on the AhsayOBM / ACB client application, the following error message is received in the backup report :

No. Type Timestamp Log
* info YYYY/MM/DD hh:mm:ss ....
* erro YYYY/MM/DD hh:mm:ss [SQLITE_CORRUPT] The database disk image is malformed (database disk image is malformed)
* ... ... ...

Cause

This issue can occurs if there is a corrupted index file on the backup set.

These are many factors that could trigger a backup set index corruption:

  • The machine where the backup job is running was previously shutdown / rebooted when a backup job was still running.
  • Disk issue on the computer where the backup is performed.
  • Unstable network connection between the backup computer and network temp folder.
  • Backup client application crashed during a previous backup.
  • Backup client application encountered an out of memory or "Java Heap Size" error during a previous backup.

Resolution

To workaround this issue, it is recommended to:

First, try deleting the current index files from the temporary folder on the backup machine.

  • Make sure there is no backup / restore job running.
  • Browse to the folder %temp_folder_path%\%backupSetID%\
  • Delete all contents in the folder
  • Perform the backup job again
If the SQLITE_CORRUPT error persist, then it is recommended to use the following workaround:

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.

Example:
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"

Copy the index files from:

${User_Home}\username\1595563417075\blocks\2020-10-19-15-00-28\index.db.8d000.1754aa9d758.cgz
${User_Home}\username\1595563417075\blocks\2020-10-19-15-00-28\index.db.id229637a.115b0i.8d000.1754aa9d758.cgz

To

${User_Home}\username\1595563417075\blocks\

Keywords

index corrupted, java, heap, size, disk, corrupt, issue, crash

public/8088_issue/sqlite_corrupt_the_database_disk_image_is_malformed.txt · Last modified: 2020/11/18 17:49 by edward.chan