Kbase 20036: Migration errors 138, 375 and 4957 occur with Oracle DataServer 9.1B
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/15/2008 |
|
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 during migration
Errors 138 and 4857 occur when doing a schema pull against Oracle 8i database
WARNING: Field not found for Index-Field (Object#: xxxxx Field#: 1).
Warning message existing in .e file
Decending index existing in Oracle database during schema pull
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.
Unforutunately, this new implementation failed.
FIX:
This new feature is fixed in the following Progress 9.1B patches and thereafter (9.1C etc..).
Win32 = 9.1B12
IBM AIX = 9.1B12
HP/UX 11 = 9.1B08
HP/UX 64-bit = 9.1B05
Compaq True64 = 9.1B08
UNIX V.4 = 9.1B04
Linux = 9.1B03
Sun SPARC = 9.1B09
Sun Intel = 9.1B08