Page 1 of 1
Posted: Wed Aug 19, 2009 10:36 am
by chulett
I don't think 'plain' UTF-8 supports the Euro symbol. However Unicode UTF-8 does, I believe, and there seems to be a 'Greek UTF-8' as well:
http://docs.hp.com/en/5187-0701/ch09s08.html
A google of "utf-8 euro symbol" turned up alot of chatter on the subject.
Posted: Wed Aug 19, 2009 12:56 pm
by rcanaran
Check with support, but I beleive you have to have NLS support turned on in your installation of DS and then install multiple CODEPAGES. Fromt here, i beleive you select a default codepage for the installation, as wella project, but can choose codepage for a particular job as well.
This was the way the documentation described the workings for DS 7.5.? Its supposed to work if the DS Server is on a Unix platform, but not if on a WIN DOZE paltform. I believe this was suposed to be fixed for DS 8.
Posted: Thu Aug 20, 2009 2:23 am
by kjaouhari
Thanks all ,
I'm using NLS map ISO8859-7-CS
Seems to work fine.
Posted: Thu Aug 20, 2009 1:51 pm
by rcanaran
kjaouhari wrote:Thanks all , I'm using NLS map ISO8859-7-CS Seems to work fine.
So this topic is resolved?
Posted: Fri Aug 21, 2009 2:41 am
by kjaouhari
Not really, actually I still have some issues.
The source database is sql server and is using SQL_Latin1_General_CP1_CI_AI
Any document where to check the most suitable NLS for this ?
Posted: Fri Aug 21, 2009 2:42 am
by kjaouhari
Not really, actually I still have some issues.
The source database is sql server and is using SQL_Latin1_General_CP1_CI_AI
Any document where to check the most suitable NLS for this ?
Posted: Fri Aug 21, 2009 3:06 am
by kjaouhari
Here is the error message I get :
nls_map_buffer_out() - NLS mapping error, row 1599 (approx), row = "19556,3,18,"
Don't really understand why cause it is like in the source table.
Posted: Fri Aug 21, 2009 5:30 am
by chulett
Do you actually have data like "19556,3,18," in the source? What kind of field are you loading it into?
Posted: Fri Aug 21, 2009 5:57 am
by ArndW
I doubt that the characters are "?", just that the tool you are using to display the data doesn't handle NLS correctly. Can you check the binary/hex values?
Posted: Fri Aug 21, 2009 7:36 am
by kjaouhari
Here is the Hex :
Code: Select all
00000000:2d 32 37 36 36 32 2c 35 2c 35 2c 22 46 4c 41 43 -27662,5,5,"FLAC
00000010:4f 4e 20 50 45 54 49 54 20 28 36 30 20 3f 22 2c ON PETIT (60 ?",
00000020:2c 22 30 22 2c 2c 2c 2c 2c 2c 2c 2c 2c 2c 0d 0a ,"0",,,,,,,,,,..
00000030:2d 32 37 36 36 31 2c 35 2c 35 2c 22 46 4c 41 43 -27661,5,5,"FLAC
00000040:4f 4e 20 53 49 4d 50 4c 45 20 28 32 35 30 22 2c ON SIMPLE (250",
00000050:2c 22 30 22 2c 2c 2c 2c 2c 2c 2c 2c 2c 2c 0d 0a ,"0",,,,,,,,,,..
00000060:2d 32 37 36 35 38 2c 37 2c 31 33 2c 2c 2c 22 2d -27658,7,13,,,"-
[code]
Posted: Fri Aug 21, 2009 8:50 am
by kjaouhari
Can't read you after the second line, but even though I can display charactere with accent I still get the same error message.
So you right the error is not due to the accent but something else.
Posted: Fri Aug 21, 2009 9:34 am
by kjaouhari
here we are :
Latin1-General, case-insensitive, accent-insensitive, kanatype-insensitive, width-insensitive for Unicode Data, SQL Server Sort Order 54 on Code Page 1252 for non-Unicode Data
Posted: Fri Aug 28, 2009 1:52 am
by kjaouhari
Hi,
I get the solution, problem is ODBC stage, using now MSOLEDB fixed the issue.
Everything is fine now, thanks for your contributions.