Home » RDBMS Server » Server Utilities » problem with migration to AL32UTF8
problem with migration to AL32UTF8 [message #544239] Mon, 20 February 2012 18:25 Go to next message
globek
Messages: 2
Registered: February 2012
Junior Member
Hi,
I have a problem with character set migration to AL32UTF8 in Oracle database. My database version is 11.2.0.3 and I'm using Database Migration Utility to Unicode. The most problematic thing is that I have two different chararacter sets in database. NLS_CHARSET is EE8ISO8859P2 and system data is in this charset, the second one is EE8MSWIN1250 and all application data is in that one because it was imported without conversion to ISO. I set in DMU that current charset is ISO, assumed is MSWIN and target is AL32UTF8. I managed to resolve all conflicts except for one data in table SYS.SOURCE$ need conversion. I don't know what to do with this one. Could someone help me with that? Is there another way to migrate database to UTF? Oracle support told me that using DMU tool is the only supported method.
Re: problem with migration to AL32UTF8 [message #544255 is a reply to message #544239] Mon, 20 February 2012 23:16 Go to previous messageGo to next message
Michel Cadot
Messages: 59296
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Quote:
the second one is EE8MSWIN1250 and all application data is in that one because it was imported without conversion to ISO.

Whar does this mean?
Do you insert EE8MSWIN1250 characters into EE8ISO8859P2 strings?
If yes, you have to first know what is the differences between these two character sets.
Then, depending on these differences, you may be able to do it directly or not.

On the other point, about SYS.SOURCE$, it is a real problem or not depending if the interested characters are in the above list or not.

Regards
Michel
Re: problem with migration to AL32UTF8 [message #544324 is a reply to message #544255] Tue, 21 February 2012 04:17 Go to previous messageGo to next message
globek
Messages: 2
Registered: February 2012
Junior Member
Hi,
yes, EE8MSWIN1250 characters data was inserted into EE8ISO8859P2 strings. 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 (ie sql file), truncate it, make migration to UTF using DMU and after migration import exported data to SOURCE$ table in new charset. Is it good idea?
Re: problem with migration to AL32UTF8 [message #544328 is a reply to message #544324] Tue, 21 February 2012 04:33 Go to previous message
Michel Cadot
Messages: 59296
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
It is a very BAD idea.
Do NOT play with SYS objects.

Regards
Michel
Previous Topic: Netca and netmgr utilities
Next Topic: Privs on logical backup
Goto Forum:
  


Current Time: Thu Oct 02 09:48:18 CDT 2014

Total time taken to generate the page: 0.10989 seconds