Kbase P116549: CRC errors when running r-code against a schema holder created with "Create DataServer Schema" utili
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
6/6/2006 |
|
Status: Unverified
FACT(s) (Environment):
MS SQL DataServer
Windows
SYMPTOM(s):
Trying to run compiled code against a new schema holder database
Error 1896 is generated
** CRC for <filn> does not match CRC in <procedure>. Try recompiling. (1896)
Code was compiled against the schema holder only; MS SQL database was not connected
Code runs against the original schema holder
Logical names (schema holder/MS SQL database) are the same for both schema holders
Original schema holder was created using the Progress DB to MS SQL Server utility
New schema holder created using Create DataServer Schema utility
MS SQL database structure has not changed
CAUSE:
This is expected behaviour. The Progress DB to MS SQL Server utility and Create DataServer Schema utility do not result in schema holders that are the same despite being created from the same MS SQL database.
When using the Progress DB to MS SQL Server (PRO2MSS), there is an extra step involved which is not present when using Create DataServer Schema (CDS). When using PRO2MSS, Progress does the following:
1) Create an SQL script based upon the structure of the Progress database
2) The SQL script creates the structure of the SQL database, adding tables, fields etc.
3) The Progress Schema Holder is created from the SQL database
4) The utility modifies schema holder to ensure that it matches the Progress database.
When using CDS, step 4 does not happen so there can be differences between the schema holders. For example, field names may be different if they have dashes in their names; Cust-num gets migrated as cust_num, and it gets pulled as cust_num. In step 4, the utility changes cust_num to cust-num in the schema holder so that it matches the definition in the Progress database again.
FIX:
Option #1
After creating the schema holder with Create DataServer Schema, run the Adjust Schema utility against it.
Option #2
Deploy a backup of the original schema holder (created with Progress DB to MS SQL Server).
If the name of the MS SQL database has changed, refer to solution P101811 for more information.