Kbase P11543: Workaround for migration errors 138, 375 and 4957 with Oracle DataServer 9.1B
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
1/27/2006 |
|
Status: Verified
FACT(s) (Environment):
Progress 9.1B
Oracle 8i
Oracle DataServer
SYMPTOM(s):
** <file-name> record not on file. (138)
** You cannot add an Index-Field to an existing Index. (375)
Invalid encoded representation of RAW data. (4957)
Error occurs when creating/updating/adding records in ORACLE
Errors occur when running Pro-to-ORA (migration) from Progress to ORACLE
Descending indexes are present within Progress database
CAUSE:
Bug# 20000515-024
CAUSE:
In Progress 8.x, 9.0x, & 9.1A when descending indexes existed within a Progress database, during the migration, Progress created ASCENDING indexes within ORACLE and DESCENDING within the Progress schema holder. ASCENDING indexes were created within ORACLE because at that time, ORACLE did not support DESCENDING indexes. This was true for all versions prior to ORACLE 8i.
Starting in ORACLE 8i, ORACLE introduced DESCENDING indexes as a function-based index. Upon this introduction by ORACLE, during the migration (Pro-to-ORA), the DataServer not only created DESCENDING indexes within the schema holder, but also DESCENDING indexes within within ORACLE.
FIX:
Upgrade to 9.1B patch or higher.
If unable to upgrade then this workaround will create the indexes in ASCENDING order within ORACLE and DESCENDING within the schema holder, thus keeping in line with previous behavior of Progress 8.x, 9.0x and 9.1A.
1. Run the migration and then wait until message 'Output Completed' appears.
2. Check the migration log for the name of the sql file that is produced.
3. Edit the .sql file generated by the migration by deleting all DESC keywords from the index definitions.
4. Save file
5. Click on the OK button for the Migration tool.