Information Management Platform TBIE engine leverages SQLite databases to store information about the documents in the index. This article describes the configuration parameters involved in enabling SQLite features that prevent corruption. Once corrupted, some databases can be repaired or created again, while the main database may need to be retrieved from a backup copy.
If the network connection to the storage is not solid, the operating system or the application malfunction, or a power failure occurs while indexes are being built, database corruption may occur.
The following SQLite extensions can be used to ensure that an Operating System crash or a Power failure will not corrupt the databases. Full Synchronous mode suggested below is very safe, but it is also up to fifty times slower than the default configuration.
To avoid corruption for the main database in a TBIE index (main.db3), please refer to the steps referenced in the "Enable failsafe to rollback the TBIE index SQLite databases in case of corruption" Knowledgebase article.
To avoid corruption of other databases in a TBIE index (i.e. fields-fields-db.bin), the configuration of the "ZyLAB Information Management Service x64" service can be modified. Please follow the steps below during an administrative time frame to not disrupt Legal Processing or Legal Review normal operations.
- Stop the ZyLAB Information Management Service x64 service.
- Open the "C:\Program Files\ZyLAB\Information Management Platform\Services\Bin\ZyLAB.Platform.WinService.exe.config" configuration file in a Text Editor.
- Within the "appSettings" section, add the following key: <add key="SQLiteSettings" value="JOURNAL_DELETE|SYNCHRONOUS_FULL" />
- Start the ZyLAB Information Management Service x64 service.
An example of the suggested configuration is as follows.'
<add key="SQLiteSettings" value="JOURNAL_DELETE|SYNCHRONOUS_FULL" />
6.2 Service Pack 1; 6.2 Service Pack 2; 6.3; 6.4
Article is closed for comments.