Kbase P162223: Dbtool option 4 (Record Version Validation) reporting problems with number of fields in a table.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
4/18/2011 |
|
Status: Verified
SYMPTOM(s):
Dbtool option 4 (Record Version Validation) reporting problems with number of fields in a table.
There were 1 error(s) found in 181496 of tablename (tbl#).
Number of fields mismatch. Expected #, got #
FACT(s) (Environment):
Example of errors in dbtool output file:
Number of fields mismatch. Expected 18, got 17
There were 1 discrepancies found in 795 of tablename (1501).
Number of fields mismatch. Expected 28, got 21
There were 1 discrepancies found in 909 of tablename (1242).
Record can be accessed via the 4GL / ABL.
All records display properly without error.
DBRPR does not detect record or block level corruption in the database.
idxcheck does not detect index level corruption.
idxfix does not detect index level corruption.
All Supported Operating Systems
OpenEdge 10.x
CAUSE:
The error messages 1501 and 1242 do not indicate record level corruption. This is expected behavior.
FIX:
The table being referenced has had fields that were added or purged. The fields still exist in the database even though they are no longer seen.
The message "field number mismatch" does not suggest an error in the record. It means that the there were record version changes and the record has not been upgraded to the latest version yet. This is especially true if dbtool reports 0 discrepancy after a record upgrade.
When we change a table by adding/deleting a field, we only change the schema of the table, data records of the table are not upgraded alone with the change, a record that has old schema version will be physically upgraded to the current version where there is committed change to the record. This is done for performance.