DBTOOL Option 3 reports inconsistent for single table vs all table validation

DBTOOL Option 3 Record Validation returns inconsistent results when a single table is validated vs all tables being validated. 
A single table validation returned a validation problem with the table where a validation on all tables does not report any errors
DBTOOL Option 3 does not report errors when all tables are validated

When a specific table (number) is selected:

• DBTOOL will ignore the records that don't belong to the table, so the corrupt records with an invalid table number (-1 or 0) are skipped.
• DBTOOL will report on all records that do belong to the table (number), so negative record length and corrupt fields will be reported

When all tables are selected: 

• DBTOOL processes all corrupt records, including those with invalid table numbers and can crash due to unexpected corruption. 
• DBTOOL is not coded to handle the pattern of corruption and further processing on the corrupt fields can lead to unexpected errors.

Upgrade to OpenEdge 11.7.0. Where DBTOOL Option 3 has been updated to report common errors like invalid record size and invalid table number and then stop further processing on the corrupt fields.

While DBTOOL Option 6 can fix corruption like: a mismatched record field number in record header, or small record fragments that might cause a problem when update on the fragment results to size of rowid of its next fragment (32->64 bit), it cannot fix all record corruption specifically invalid record size, invalid table numbers and corrupt fields.  The next corrective action is to dump the available content of the affected Storage Areas, remove the Area and load into a new Storage Area.

Dump the available content of the affected Storage Areas, remove the Area and load into a new Storage Area

Progress Articles:

dbtool option 3 causes the database to crash   
 DBTool and Promon concurrently cause Error49