Kbase P80569: Dynamics: Corruption of ICFDB database
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/08/2004 |
|
Status: Unverified
FACT(s) (Environment):
Dynamics
SYMPTOM(s):
Corruption of Dynamics repository database
idxbuild operation fails with errors on ICFDB
SYSTEM ERROR: Failed to extract field <field-num> from <file-name> record (table <table-num>) with recid <RECID>. (3191)
SYSTEM ERROR: SYSTEM ERROR: memory violation (49)
dbrpr session crashes with memory violation (49)
SYSTEM ERROR: Cannot read field <num> from record, not enough fields. (450)
File-name in error 1127 is a metaschema table
Fix RECID <recid>, <file-name> already exists with <field value>. (1127)
Fix RECID <recid>, _File already exists with File-Name "P" Owner "". (1127)
SYSTEM ERROR: RECID <recid> in _File could not be found. (1645)
CAUSE:
Metaschema corruption on the ICFDB Database are resulting from copying binary Database files betweeen Linux and Windows and back again.
FIX:
There are two ways that updates to the ICFDB should be undertaken:
1.) The icfdb needs to be manually created on Linux and then connect the DCU to it and perform the necessary updates, which may be time consuming.
2.) Create the ICFDB locally (on Windows) perform all the necessary actions to it and then dump and load between platform changes.
To update an existing repository on Linux - you can connect with the DCU and load the schema and data, but again - it may be faster to dump the existing Linux db, create a new one on Windows, update through the DCU, and dump / load back to Linux new database.
The ICFDB schema is and should stay untouched. The only time you would normally need to do this is when there are new Dynamics service packs and that's not so often.