Kbase P10944: Running mkschema fails after migrating database with conv89
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/2/2004 |
|
Status: Verified
SYMPTOM(s):
Running mkschema after migrating Progress 8.x database with conv89
mkschema loops through messages
The following message repeats after running: mkschema -v dbname
Unaligned access pid=22630 <mkschema> va=0x1403baa62 pc=0x120748290
ra=0x1207486d8 inst=0xa1ea0000
Unaligned access pid=22630 <mkschema> va=0x1403baa62 pc=0x12074a654
ra=0x1207484b0 inst=0xa02a0000
Unaligned access pid=22630 <mkschema> va=0x1403baa62 pc=0x1207484ec
ra=0x1207484e4 inst=0xa1ea0000
[MERANT][ODBC PROGRESS driver][PROGRESS]No SQL schema found in database (run mkschema)
CAUSE:
The ODBC error indicates that there is no SQL schema found, although the database was converted with conv89 and mkschema should have been run in that process. The reason for this failure is that the original database was corrupt before the conversion.
FIX:
Run the Progress Database Repair Utility (dbrpr) as referred to in Progress Solution 2077 "How to Run dbscan With Database Repair Utility (dbrpr)" to determine if the original database has corruption. Please call Technical Support for assistance with recovering the database. Restoring from backup may be necessary.