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?