Kbase P95612: Character field with default display format x(8) is migrated to Oracle as varchar2(30)
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
28/09/2005 |
|
Status: Unverified
FACT(s) (Environment):
DataServers
SYMPTOM(s):
Character field with default display format x(8) is migrated to Oracle as varchar2(30)
Character field with default display format x(8) is migrated to MS SQL as varchar2(30)
Character field with default display format x(8) is migrated to ODBC database as varchar2(30)
Character fields with display format other than x(8) are migrated to Oracle as varchar2 with corresponding length
Character fields with display format other than x(8) are migrated to MS SQL as varchar2 with corresponding length
Character fields with display format other than x(8) are migrated to ODBC db as varchar2 with corresponding length
The symptoms apply to both migration utility and delta SQL utility
CAUSE:
The corresponding data server product is designed to do so. Since x(8) is the default display format, the DataServer is designed to make this field a varchar2(30) in Oracle. If the format is a value other than x(8), the utilities will convert the format to char length accordingly.
Following is information from DataServer for Oracle Guide
The Progress-to-ORACLE (or migration utilities) utility uses a field's format information when it defines the field as an column in foreign databases. Since Progress allows a field to hold more data than the field's format will display, the utility might instruct foreign database to create a column that is wider than the format indicates. For those fields with a display format of x(8), the utility automatically generates a VARCHAR(30) column.
FIX:
None. Expected behavior