Kbase P52620: Error 132 and 188 updating definitions for Oracle DataServer schema
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/31/2005 |
|
Status: Unverified
FACT(s) (Environment):
Oracle DataServer
Progress 9.1C
Progress 9.1D
SYMPTOM(s):
Error 132 updating definitions for Oracle DataServer schema
**s_ttb_flb already exists with <value>. (132)
Data type must be character, integer, decimal, logical, date, or recid. (188)
**<file> already exists with . (132)
Have an Oracle Index was defined as descending
CHANGE:
Add a new field to the table
CAUSE:
Bug# 20031106-066
FIX:
1. Move to 9.1D and apply Service Pack 7.
WARNING: The installation of the Service Pack 7 is mandatory in order have the step below to work.
2. Remove the descendent index from the Oracle within ORACLE.
3. Recreate the indexes in ASCENDING order within ORACLE making sure that there is no DESC keywords into the index definitions
4. Run schema update again to apply the changes.
5. Change the index definition into the schema holder only, defining the index as as DESCENDING within the schema holder.