Migrating Oracle Schema to AL32UTF8 Character Set
What do I need to when exporting from a single byte character set database and importing into a UTF-8 database?
The Oracle export and import utilities (both data pump and old exp/imp) will handle the character translation from the single byte character set (usually WE8ISO8859P1 or P15) to AL32UTF8. The key to successful migration is to ensure that the tables are created with CHAR semantics in the target database.
- Ensure that the target database has the parameter NLS_LENGTH_SEMANTICS set to CHAR
2. Use Oracle Navigator or similar interactive tool to extract table create DDL into a file that you can use to pre create the tables in the target database. Only the CREATE TABLE statements are needed. The import process will create everything else. Only the Maximo tables are needed. The Oracle Text indexes are made up of tables named DR$xxxx, which should be excluded.
3. Edit the script and change all references to BYTE in varchar2 column definitions to CHAR. For example:
CREATE TABLE ABC (COL1 VARCHAR2(10 BYTE), COL2 NUMBER(10,2)...
Should be changed to:
CREATE TABLE ABC (COL1 VARCHAR2(10 CHAR), COL2 NUMBER(10,2)...
4. Run the script on the target database to create the tables before the import.
5. Now import the remaining objects and data.
More support for:
Maximo Asset Management
Software version: 6.2.1, 6.2.2, 6.2.3, 6.2.4, 6.2.5, 6.2.6, 6.2.7, 6.2.8, 7.1, 7.1.1, 7.5, 7.6
Operating system(s): Platform Independent
Software edition: All Editions
Reference #: 1622335
Modified date: 14 January 2013
Translate this page: