Repairing a CRC mismatch error
- Last Updated: December 12, 2014
- 1 minute read
- OpenEdge
- Version 13.0
- Documentation
Repairing a CRC mismatch error
Syntax
The following special syntax is for Database Administrators who handle problems while
migrating database tables from an older release database to a newer release database. In
some cases, there may be a CRC mismatch error (when dumping and loading data using
BINARY DUMP/LOAD.).
|
PRO_FIELD_INFO attribute indicates that the incorrect
values in the_Field table, corresponding to the given table name, need to
be updated. The PRO_SCHEMA_REPAIR attribute provides additional
authorization to DBAs that is required to perform the necessary updates to CRC specific
rows in system tables.Using the above statement for a particular table automatically repairs all the known schema
errors in the table that are causing the CRC mismatch. If the error persists even after
running this statement, report the problem to Progress Customer Support with the
_Field system table information in the old and new databases.
Execution of the above statement sets _DB-lang to its default value (0)
and updates the following data type names as shown below:
-
TIMESTAMPtoDATETIME -
LVARBINARYtoBLOB -
LVARCHARtoCLOB
Executing the above statement also sets the case sensitivity value of the non-character type columns to 0.
Example
|
In the above example, the Customer table belongs to an old database. When
you execute the above statement, the inconsistent field information is corrected and the
table is updated with the new CRC.