Kbase P82957: The delta.sql utility is converting character data type of an extent field to a Oracle's long data t
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
4/24/2009 |
|
Status: Unverified
SYMPTOM(s):
The delta.sql utility is converting character data type of an extent field to a Oracle's long data type
A table with an extent field is commented out on the delta.sql file generated by Oracle DataServer utility
The same table is missing from the <schema holder name>.df file generated by the same utility.
The "Use SQL Width" option is checked when the "Generate Delta.sql Progress to Oracle..." Oracle DataServer utility is run.
FACT(s) (Environment):
Oracle DataServer
CAUSE:
This issue is currently known by the development. This issue is caused by not calculating the SQL-WIDTH for extent field. This problem exists when the accumulated total length for the extent field's SQL-WIDTH is more then 4000. However, there are three workarounds exists to fix this issue.
FIX:
The three options for the workaround are:
1. Change the SQL width for the extent field in the data dictionary > options > SQL Properties > Adjust SQL width to the desired SQL width, i.e., if the display format for the field is x(300), make it 600 or any length you want. Perform the incremental .df between two Progress databases to generate the delta.df file. Then run the oracle DataServer's create delta.sql progress to oracle utility to generate oracle.sql and <schema holder name>.df files.
OR
2. Change the SQL-WIDTH (Progress 9.1x) or MAX-WIDTH (OpenEdge 10) to the desired length in the delta.df file. Then run the Oracle DataServer's create delta SQL utility to generate oracle.sql and <schema holder name>.df files.
OR
3. Change the oracle.sql created by the Oracle DataServer delta.sql utility and change all the field's datatype from long to varchar2(600) or the desired length and un-comment the SQL. Run the oracle.sql in the sql*plus and perform Update/Add Table definition utility from oracle DataServer menu. Then run the adjust schema to fix the table or field name or any progress triggers associated with the table in the schema holder.