This content has been marked as final. Show 5 replies
the national charsets is for column types like nvarchar not for normal varchar data types. So if your dump file contains such column types you will also need to set it. The charset is for the normal column types like varchar. The use of unicode is best pratice if you use multiel language, but keep in mind that multibyte charset can be a problem during the import because varchar2(10) means 10byte and not 10 chars, so errors like identifier to long can occur during import.
You can create the database.
Check this documentation:
You can use a charset like WE8MSWIN1252 which covers spanish also (as far i know) and is a superset to us7ascii
Million Thanks Peter for the advice, I have never done this before and confused on the documentation- this is new to me.
You are correct in that I am only using VARCHAR2 types, no NCHAR types.
The database does not have any data in it yet, only a template.
So I would change the CHARACTER SET section of my build script to WE8MSWIN1252 and it should work, seems too easy thankfully.
I was wondering if WE8ISO8859P1 would work?
Hi,1 person found this helpful
The WE8ISO8859P1 Charset is a very Old Charset. I did not like it to use (but some of my customers use it). We in Europe have Euro € Sign which is not supported by this charset. So try to avoid it to use.
Yes it should work. If you look at [url http://docs.oracle.com/cd/E11882_01/server.112/e10729/ch2charset.htm#NLSPG165]Table 2-3 lSO 8859 Character Sets it specifies Western European supports spainish characters.1 person found this helpful
Edited by: NC on Nov 1, 2012 6:54 PM
Oracle recommends using the AL32UTF8 characterset - http://docs.oracle.com/cd/E11882_01/server.112/e25494/create001.htm#ADMIN133431 person found this helpful