Try OpenEdge Now
skip to main content
SQL Reference
SQL Reference : OpenEdge SQL Statements : ALTER TABLE : Repairing a CRC mismatch error
 
Repairing a CRC mismatch error
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.).

Syntax

ALTER TABLE table_name SET PRO_FIELD_INFO PRO_SCHEMA_REPAIR
Note: The 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:
*TIMESTAMP to DATETIME
*LVARBINARY to BLOB
*LVARCHAR to CLOB
Executing the above statement also sets the case sensitivity value of the non-character type columns to 0.

Example

The following example repairs the CRC mismatch error:
ALTER TABLE Customer SET PRO_FIELD_INFO PRO_SCHEMA_REPAIR;
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.