How to perform a file table integrity check of the entire main.db3 database file

SYMPTOMS

How to perform a file table integrity check of the entire main.db3 database file. This article describes a required integrity check on the entire main.db3 database file. Look for out-of-order records, missing pages, malformed records, missing index entries, and UNIQUE and NOT NULL constraint errors.

CAUSE

ZyTimer Service is stopped when there are problems reading the main.db3 file (document-provider database).

RESOLUTION

• Open the main.db3 database in an SQLite tool.
• The main.db3 can be found on this location. Open the path: .\ZyLAB Data\Indexes\Myindex\Configuration\
• Change the Myindex name applicable to your index name reference.
• Run the SQLLite PRAGMA integrity check in your SQLite tool.
• Perform the PRAGMA database.integrity_check;
  This pragma does an integrity check of the entire database.
• Example command on the main.db3: PRAGMA main.integrity_check

The PRAGMA statement is an SQL extension specific to SQLite and used to modify the operation of the SQLite library or to query the SQLite library for internal (non-table) data.

The integrity_check pragma looks for out-of-order records, missing pages, malformed records, missing index entries, and UNIQUE and NOT NULL constraint errors.
If the integrity_check pragma finds problems, strings are returned (as multiple rows with a single column per row) which describe the problems.

APPLIES TO

6.4; 6.4 Service Pack 1; 6.5