Kbase P25107: Workaround: Error 1461 while compiling the code after updating the SQL Server schema holder
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
22/06/2009 |
|
Status: Verified
SYMPTOM(s):
Workaround: Error 1461 while compiling the code after updating the SQL Server schema holder
Schema holder does not match database schema --file <DB_Name>.<Owner_Name>.Table_Name> field <Field_Name> (1461)
Schema holder does not match database schema -- file field . (1461)
FACT(s) (Environment):
Fields were added after the PROGRESS_RECID_IDENT_ field in a MS SQL Server table
Cannot upgrade to Progress 9.1D or higher
Progress 9.1C
Windows NT 32 Intel/Windows 2000
MS SQL DataServer
ODBC DataServer
CAUSE:
Bug# OE00075041
CAUSE:
The bug was from assuming the Progress_Recid_ident field being at the end of all other columns in the MSS Database for each table. Therefore, the last foreign position is reserved for the Progress_recid column which is hidden in the schema holder. When a new field is added in the MSS Database and updated in the schema holder, it assigns the last value that was reserved for progress_recid to the new field in the schema holder by the DataServer. Being the same foreign position for both progress_recid value and one of the newly added fields in the DataServer schema holder causes the error to be displayed.
FIX:
Workaround:
- Dump the table from the Data Administration
- Delete the table in the schema holder
- In the .df file modify the FOREIGN-POS value of the new field and increase by 1. Repeat this for each subsequent newly added field.
- Remove the 1st lines that add the database
- Load the .df file from the data Administration