KB - Fixing corrupted Private Local databases

Fixing corrupted Private Local databases

Article was last updated on April 18, 2018. View products that this article applies to.

To repair a corrupted database file, follow the steps below:

  1. Start the Administration Tool and connect to the local or remote ORF instance
  2. Navigate to the page of the related test (Whitelists / Auto Sender Whitelist, or Blacklists / Greylisting, or Blacklists / Honeypot Test, or Blacklists / DHA Protection Test)
  3. Click the Database button, then Manage
  4. Attempt to Repair the database

If the above does not help and you still receiving database related error messages, delete the related .abs file from the ORF directory (Program Files (x86)\ORF Fusion by default). Note that this requires the ORF Service to be stopped first, as it locks the database file. The embedded database engine will recreate the database file when the first entry needs to be added to it.

To solve the problem permanently, it is strongly recommended to switch to an External SQL database: setup instructions can be found in our guides. Once the SQL database is set up, you can migrate all data from the Private Local Database files using the Database Converter Tool.

Applies To

The article above applies to the following products and versions:

  • ORF 5.4.1
  • ORF 5.4
  • ORF 5.3
  • ORF 5.2
  • ORF 5.1
  • ORF 5.0
hnp1 | hnp2