To improve DBTOOL data integrity verification operation times:
1. Run DBTOOL online in order to use threads.
- Having more threads to do the work will be faster than using single thread
2. Use default DBTOOL Verbose levels
- More detailed verbosity creates larger output.
- Use higher verbosity levels for explicit focus at finer granularity
Example: dbtool.out file sizes based on the verbose level used against a single table with 9418 records,
without errors
- Verbose logging 0, size 67 bytes
- Verbose logging 1, size 433,205 bytes
- Verbose logging 2, size 800,505 bytes
- Verbose logging 3, size 12,566,070 bytes
3. DBTOOL does a sequential scan one Area at a time.
- If all tables are in the same area , choosing "all tables" in the area will be faster that choosing one table at a time and repeating for each table.
- If tables in different Areas , start multiple DBTOOL sessions each running on a different Area
