Default Character sets on Windows

[DaPi]

Originally posted by akhadar
Since both are supersets . . .

Two sets can't be supersets of each other unless they are identical!

Originally posted by JMac
. . . both have apparently compatible character sets?

I suspect not - my guess is that neither is a superset of the other. If the WIN charset was a superset of the ISO one, Oracle wouldn't give the warning.

Does any one have a good reference showing the actual code tables?

[thomasp]

have you checked the client side settings from where you are accessing this character

Open up regedit->HKEY_LOCAL_MACHINE->SOFTWARE->ORACLE->HOME0 and check the value for NLS_LANG.

[akhadar]

sorry for the trash which i posted early.
After lettle bit search i found some useful information which deals with WI8MSWIN1252 and WE8ISO8859P1 character sets on two databases and what u can do to correct the data which is shows as ? after import.
you can run csscan (oracle util) to scan the datafiles for characters which may not map cleanly from 1252 to ISO-1. To fix those, you may need to run a replace() on the data and then export it.

Try setting the NLS_LANG=american_america.WE8ISO8859P1 on windows before exporting. That way the export file will contain WE8ISO8859P1 data.
Isolate the � using substr() and get it's decimal value using dump(). It seems to be Ox93 (using windows Character Map for Windows:Western). The right hand one seems to be 0x94. The regular " is Ox22.

update my_tab set mycol = replace(mycol, chr(123), chr(234))
where mycol != replace(mycol, chr(123), chr(234));

Also check this link
http://metalink.oracle.com/metalink/...&p_id=137127.1