| Author |
Message |
Francesco M.
*nix forums beginner
Joined: 01 Apr 2005
Posts: 36
|
 Posted: Tue Feb 08, 2005 7:01 am Post subject:
Re: Import character set issue:
|
|
|
Sybrand Bakker wrote:
| Quote: | On 7 Feb 2005 06:22:16 -0800, fmarchioni@libero.it (Francesco M.)
wrote:
Should I set NLS_LANG with a code that identifies US7ASCII ??
where am I wrong ?
The syntax for NLS_LANG=<Territory>_<Country>.<charset
so
American_America.US7ASCII
not US7ASCII alone.
--
Sybrand Bakker, Senior Oracle DBA
|
ok thanks for your kind reply. Now imp doesn't complain
anymore about NLS_LANG settings.
Regards
Francesco |
|
| Back to top |
|
 |
Rauf Sarwar
*nix forums Guru
Joined: 03 May 2005
Posts: 353
|
| Posted: Mon Feb 07, 2005 2:43 pm Post subject:
Re: Import character set issue:
|
|
|
Sybrand Bakker wrote:
| Quote: | On 7 Feb 2005 06:22:16 -0800, fmarchioni@libero.it (Francesco M.)
wrote:
Should I set NLS_LANG with a code that identifies US7ASCII ??
where am I wrong ?
The syntax for NLS_LANG=<Territory>_<Country>.<charset
so
American_America.US7ASCII
not US7ASCII alone.
|
To add to above,
If your client NLS_LANG is already set to same as your target database
then you don't need to change the NLS_LANG. You are OK as long as your
client NLS_LANG is either same as your export file OR same as your
target database.
Regards
/Rauf |
|
| Back to top |
|
|
Sybrand Bakker
*nix forums Guru
Joined: 03 Apr 2005
Posts: 1766
|
| Posted: Mon Feb 07, 2005 2:15 pm Post subject:
Re: Import character set issue:
|
|
|
On 7 Feb 2005 06:22:16 -0800, fmarchioni@libero.it (Francesco M.)
wrote:
| Quote: | Should I set NLS_LANG with a code that identifies US7ASCII ??
where am I wrong ?
|
The syntax for NLS_LANG=<Territory>_<Country>.<charset>
so
American_America.US7ASCII
not US7ASCII alone.
--
Sybrand Bakker, Senior Oracle DBA |
|
| Back to top |
|
|
Francesco M.
*nix forums beginner
Joined: 01 Apr 2005
Posts: 36
|
| Posted: Mon Feb 07, 2005 1:22 pm Post subject:
Re: Import character set issue:
|
|
|
"Rauf Sarwar" <rs_arwar@hotmail.com> wrote in message news:<1107521752.633206.58330@o13g2000cwo.googlegroups.com>...
| Quote: | Francesco M. wrote:
Hi all,
I have exported on table from one DB to another. I have this issue:
import done in US7ASCII character set and AL16UTF16 NCHAR character
set
import server uses WE8ISO8859P1 character set (possible charset
conversion)
export server uses US7ASCII NCHAR character set (possible ncharset
conversion)
I have found an interesting article which explains how to indentify a
character set:
http://www.dbaoncall.net/references/ht_identify_charset.html
but I haven't found which are the right steps to avoid this issues.
Should I change NLS_LANG before import, should I let Oracle do the
conversion...or what else ?
Thanks a lot
Francesco
Try to minimize the number of characterset conversions done during
exp/imp. To do that, set your client NLS_LANG to exactly the same as
the source database characterset, this would gaurantee no conversions
during export. Then keep the same NLS_LANG setting while importing
which means there will be only one conversion done during the entire
process.
Remember, exp and imp are client tools thus they will use the
characterset from NLS_LANG environment variable and NOT the database
characterset. If either is different, conversion will take place.
Regards
/Rauf
|
Hi, thank you very much for your answers. Actually this is what I did:
At first I identified that the export was done with US7ASCII
0000000 0300 0145 5850 4f52 543a 5630 392e 3032 <---- US7ASCII
0000020 2e30 300a 4453 5953 5445 4d0a 5255 5345
0000040 5253 0a31 3032 340a 300a 3332 0a30 0a00
0000060 0100 1f07 d000 0100 0000 0000 0000 0000
0000100 0a00 2020 2020 2020 2020 2020 2020 2020
0000120 2020 2020 2020 2020 2020 2020 2020 2020
So before using imp:
$ export NLS_LANG=US7ASCII
Unfortunately when I launch the imp utility I get this error:
IMP-00058: ORACLE error 12705 encountered
ORA-12705: invalid or unknown NLS parameter value specified
Should I set NLS_LANG with a code that identifies US7ASCII ??
where am I wrong ?
Thanks again
Francesco |
|
| Back to top |
|
|
Joel Garry
*nix forums Guru
Joined: 24 Mar 2005
Posts: 1044
|
| Posted: Fri Feb 04, 2005 11:41 pm Post subject:
Re: Import character set issue:
|
|
|
Just one thing to add to Rauf's reply: Do you have any non-ASCII
characters (umlats or such) in your ASCII db? If not, nothing to worry
about. If so, a _lot_ to worry about, I would recommend you unload and
load rather than have imp be overly friendly to your data.
I did have a scare one time where some vendor had used character
variables to store their own version of a sequence. Going from 7bit to
8bit changed all the sequence numbers.
jg
--
@home.com is bogus.
http://story.news.yahoo.com/news?tmpl=story&cid=528&e=1&u=/ap/20050204/ap_on_hi_te/aol_spamming |
|
| Back to top |
|
|
Rauf Sarwar
*nix forums Guru
Joined: 03 May 2005
Posts: 353
|
| Posted: Fri Feb 04, 2005 11:55 am Post subject:
Re: Import character set issue:
|
|
|
Francesco M. wrote:
| Quote: | Hi all,
I have exported on table from one DB to another. I have this issue:
import done in US7ASCII character set and AL16UTF16 NCHAR character
set
import server uses WE8ISO8859P1 character set (possible charset
conversion)
export server uses US7ASCII NCHAR character set (possible ncharset
conversion)
I have found an interesting article which explains how to indentify a
character set:
http://www.dbaoncall.net/references/ht_identify_charset.html
but I haven't found which are the right steps to avoid this issues.
Should I change NLS_LANG before import, should I let Oracle do the
conversion...or what else ?
Thanks a lot
Francesco
|
Try to minimize the number of characterset conversions done during
exp/imp. To do that, set your client NLS_LANG to exactly the same as
the source database characterset, this would gaurantee no conversions
during export. Then keep the same NLS_LANG setting while importing
which means there will be only one conversion done during the entire
process.
Remember, exp and imp are client tools thus they will use the
characterset from NLS_LANG environment variable and NOT the database
characterset. If either is different, conversion will take place.
Regards
/Rauf |
|
| Back to top |
|
|
Francesco M.
*nix forums beginner
Joined: 01 Apr 2005
Posts: 36
|
| Posted: Fri Feb 04, 2005 8:41 am Post subject:
Import character set issue:
|
|
|
Hi all,
I have exported on table from one DB to another. I have this issue:
import done in US7ASCII character set and AL16UTF16 NCHAR character
set
import server uses WE8ISO8859P1 character set (possible charset
conversion)
export server uses US7ASCII NCHAR character set (possible ncharset
conversion)
I have found an interesting article which explains how to indentify a
character set:
http://www.dbaoncall.net/references/ht_identify_charset.html
but I haven't found which are the right steps to avoid this issues.
Should I change NLS_LANG before import, should I let Oracle do the
conversion...or what else ?
Thanks a lot
Francesco |
|
| Back to top |
|
|
Google
|
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
Forum index
»
Databases
»
Oracle
