This content has been marked as final. Show 2 replies
Both UTF8 and AL32UTF8 support the full character repertoire of Unicode. They only differ in the way of how supplementary characters (characters with Unicode codepoints above U+FFFF) are encoded. Assuming the original UTF8 data is valid, there should be no data loss when moving from UTF8 to AL32UTF8. If you upgrade the database to 10.2.0.4/10.2.0.5 first, you can use DMU to perform this character set migration and ensure any invalid data is detected and handled properly along the process.