Kbase P98559: Application receives Cyclic Redundancy Check (crc) error after applying a manually created data defi
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
02/01/2009 |
|
Status: Verified
SYMPTOM(s):
Application receives Cyclic Redundancy Check (CRC) error
** CRC for <table-name> does not match CRC in <procedure>. Try recompiling. (1896)
Manually created df file added to development database
Code compiled against the development database
Same df file added to production databases (a copy of the development database) at several sites
Application returns CRC error at one production site
Table where two fields and and an index were added is the source of the CRC error
The manually constructed df file does not contain the relative position (rpos) for two fields in one table
The relative position of the fields at the problem production site are in reverse order from the development site
FACT(s) (Environment):
Windows
Progress 9.1D
OpenEdge Category: Database
CAUSE:
The relative position of a field is part of the CRC check, thus the CRC for a table will be different, if the rpos for a single field is different
FIX:
The recommended method to move schema changes from development to production is via incremental (delta) df files, then the position value will be included in the df file by default.