Kbase P115568: Error 54 during the loading of .df to an empty schema holder
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
26/04/2006 |
|
Status: Unverified
FACT(s) (Environment):
Oracle DataServer
SYMPTOM(s):
Error 54 during the loading of .df to an empty schema holder
SYSTEM ERROR: fmu -- bad data type. (54)
The .df was dumped from 9.1x and loading into OpenEdge 10.x schema holder for upgrade
CHANGE:
Changed the data type mapping of the Oracle's LONRRAW from Progress RAW data type to Progress CHARACTER data type in the 9.1x data dictionary
CAUSE:
The original data type map was forced changed into the 9.1x schema holder from the RAW to CHARACTER. The LONGRAW of the Oracle data type should be maps to Progress RAW data type.
FIX:
Change the CHARACTER data type in the .df for the progress field to RAW and save the .df file. Then load the .df file into the schema holder.
Example:
The .df had the following:
ADD FIELD "FIELD1" OF "TABLE1" AS character
DESCRIPTION "This is an example"
FORMAT "X(4000)"
INITIAL ""
LABEL "Transaction Raw Data"
POSITION 19
HELP "Transaction Raw Data"
LENGTH 0
ORDER 1000
FOREIGN-POS 25
FOREIGN-NAME "FIELD1"
FOREIGN-TYPE "LONGRAW"
FIELD-MISC13 0
FIELD-MISC14 1
Change the above add field definition to the following:
ADD FIELD "FIELD1" OF "TABLE1" AS raw
DESCRIPTION "This is an example"
FORMAT "X(4000)"
INITIAL ""
LABEL "Transaction Raw Data"
POSITION 19
HELP "Transaction Raw Data"
LENGTH 0
ORDER 1000
FOREIGN-POS 25
FOREIGN-NAME "FIELD1"
FOREIGN-TYPE "LONGRAW"
FIELD-MISC13 0
FIELD-MISC14 1