we can't migrate entire database this way because it is too large (almost 1TB). DMU has problem only with SOURCE$ table. I have got one idea to solve our problem but don't know if it works. I was planning to export data from SOURCE$ table (to sql file or as You say with vanilla SQL), truncate it, make migration to UTF using DMU and after migration import exported data to SOURCE$ table in new charset. Is it good idea?
QUOTE (burleson @ Feb 21 2012, 02:04 AM)
>> Is there another way to migrate database to UTF?
Well, one sure-fire way is to export the data with vanilla SQL.
select col1||','||col2 from mytab;
At that point, it's just a plain flat file.
At that point it can be imported into a new table with a different NLS using SQL*Loader. . . .