You can't change to UTF8 from WE8ISO8859P1, since the latter is not a subset
of UTF8.
If you were on US7ASCII, the story would be different.
You have to go with export/import.
Tanel.
- Original Message -
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Sent: Sunday, December
Oracle has an internal utility to do this in place named csconv. You
have to get this from Oracle consulting. In any event, there is a
utility named csscan in your oracle home. Run it against your database
and it will tell what data if any needs to be changed. Look for UTF8
conversion docs on
I have upgraded the database from 8.0.5/8.1.7 to 9.2.0.4 and changed
character set using alter database character set.
It will work without any problem. Go for it.
-Original Message-
Sent: Saturday, December 13, 2003 9:39 PM
To: Multiple recipients of list ORACLE-L
I am in the process
There's a whole spread of stuff on MetalLink about changing
character sets. There is even a utility program called 'csscan'
that scans the DB to find potential trouble spots.
In short, though, if this DB only has 7-bit ASCII characters in
in, then a switch to UTF-8 will have no immediate effect.
Gerardo,
The trick works for me also but when i try to export it shows as:
Connected to: Oracle8i Enterprise Edition Release 8.1.7.0.0 - Production
With the Partitioning option
JServer Release 8.1.7.0.0 - Production
Export done in US7ASCII character set and US7ASCII NCHAR character set
server
Harvinder,
try setting NLS_LANG=AMERICAN_AMERICA.UTF8, then doing the export.
If NLS_LANG is not set, the default is US7ASCII as you experienced.
Refer to MetaLink Note 48644.1 and Note 15095.1
Gerardo
-Original Message-
Sent: Thursday, November 01, 2001 7:30 AM
To: Multiple
NLS_LANG should be set on client, either UNIX environment variable or NT
registry entry.
I don't think there's a way to force client to use a particular character
set. This is the whole point of NLS, I think. Server should not care what
language/character set client uses, and vice versa.
Try this procedure:
The extra db bounce did the trick for me. Don't ask me why. I think I
found it on MetaLink or opened a TAR.
HTH
Gerardo
SVRMGR SHUTDOWN IMMEDIATE; -- or NORMAL
do a full database backup
SVRMGR STARTUP MOUNT;
SVRMGR ALTER SYSTEM ENABLE RESTRICTED SESSION;
SVRMGR
