Kbase P143263: DataServer PRO2*** utility creates an ISO8859-1 schema holder if "Use Unicode Types" is not selected
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
19/03/2009 |
|
Status: Unverified
SYMPTOM(s):
DataServer PRO2*** utility creates an ISO8859-1 schema holder if "Use Unicode Types" is not selected
DataServer PRO2MSS utility creates an ISO8859-1 schema holder if "Use Unicode Types" is not selected
DataServer PRO2ORA utility creates an ISO8859-1 schema holder if "Use Unicode Types" is not selected
FACT(s) (Environment):
Migrating an OpenEdge database to a foreign datasource ( Oracle or MS SQL Server )
Unicode support for DataServer requires a UTF-8 schema holder
Schema holder database has not been created before running the migration utility
Migration utility generates the schema holder database
"Codepage for Schema Image" is set to UTF-8 in PRO2ORA
"Codepage" is set to UTF-8 in PRO2MSS
Codepage is shown as UTF-8 when selecting the foreign image as the working database in Data Administration
UTF-8 schema holder is generated if "Use Unicode Types" is selected
OpenEdge DB to MS SQL Server... utility
OpenEdge DB to Oracle... utility
OpenEdge 10.1C
OpenEdge 10.2A
Windows
MS SQL DataServer
Oracle DataServer
CAUSE:
Bug# OE00182275
FIX:
Option #1
Create a UTF-8 schema holder manually.
Reference the manually created UTF-8 schema holder in the "Name of Schema holder Database" field in the PRO2*** utility.
Option #2
Convert the ISO8859-1 schema holder to UTF-8 via the PROUTIL CONVCHAR character conversion utility.