OraFAQ Forum: Client Tools » Importing Hebrew, using ODBC from Excel

Home » Other » Client Tools » Importing Hebrew, using ODBC from Excel (SQL Developer, 4.0.2, Windows 7 Professional, 64-bit)

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

Importing Hebrew, using ODBC from Excel [message #626366]

Mon, 27 October 2014 06:41

Analyst
Messages: 45
Registered: June 2014

Member

Hello,

I am trying to import to my Oracle DB (using SQL Developer 4.0.2.15) an Excel file with text columns in Hebrew, Using. But instead Hebrew word "בדיקה", I'm seeing in Oracle the following: "áãé÷ä".

Some details:

1) Oracle DB version (SELECT * FROM V$VERSION):

Oracle Database 12c Release 12.1.0.1.0 - 64bit Production
PL/SQL Release 12.1.0.1.0 - Production
"CORE 12.1.0.1.0 Production"
TNS for 64-bit Windows: Version 12.1.0.1.0 - Production
NLSRTL Version 12.1.0.1.0 - Production

2) DB computer OS - Windows 7 Professional, 64 bit.

3) Running this Select * From nls_database_parameters gives me:

NLS_NCHAR_CHARACTERSET	AL16UTF16
NLS_CHARACTERSET	AL32UTF8

Any suggestions of how to see the Hebrew in a proper way would be very appreciated.
Thanks in advance.

Report message to a moderator

Re: Importing Hebrew, using ODBC from Excel [message #626367 is a reply to message #626366]

Mon, 27 October 2014 06:51

Michel Cadot
Messages: 68729
Registered: March 2007
Location: Saint-Maur, France, https...

Senior Member
Account Moderator

The first thing to know is: "have you Hebrew characters in your database or not?"
Post the result of:

select dump(col_with_hebrew_char) dmpval, asciistr(col_with_hebrew_char) ascstr
from mytable 
where rownum=1 and ...;

in order to have the content of a field with Hebrew characters.

Report message to a moderator

Re: Importing Hebrew, using ODBC from Excel [message #626369 is a reply to message #626367]

Mon, 27 October 2014 07:09

Analyst
Messages: 45
Registered: June 2014

Member

Yes, I have Hebrew characters in my db.

Running this:

Select distinct SENIORITY_INT,
                Dump(SENIORITY_INT) dmpval, 
                Asciistr(SENIORITY_INT) ascstr
From MY_TABLE

Gives me:

6-12 חודשים	Typ=1 Len=17: 54,45,49,50,32,215,151,215,149,215,147,215,169,215,153,215,157	6-12 \05D7\05D5\05D3\05E9\05D9\05DD
0-3 חודשים	Typ=1 Len=16: 48,45,51,32,215,151,215,149,215,147,215,169,215,153,215,157	0-3 \05D7\05D5\05D3\05E9\05D9\05DD
3-5 שנים	Typ=1 Len=12: 51,45,53,32,215,169,215,160,215,153,215,157	3-5 \05E9\05E0\05D9\05DD
מעל 5 שנים	Typ=1 Len=17: 215,158,215,162,215,156,32,53,32,215,169,215,160,215,153,215,157	\05DE\05E2\05DC 5 \05E9\05E0\05D9\05DD
3-6 חודשים	Typ=1 Len=16: 51,45,54,32,215,151,215,149,215,147,215,169,215,153,215,157	3-6 \05D7\05D5\05D3\05E9\05D9\05DD
1-2 שנים	Typ=1 Len=12: 49,45,50,32,215,169,215,160,215,153,215,157	1-2 \05E9\05E0\05D9\05DD
2-3 שנים	Typ=1 Len=12: 50,45,51,32,215,169,215,160,215,153,215,157	2-3 \05E9\05E0\05D9\05DD
אין מידע	Typ=1 Len=15: 215,144,215,153,215,159,32,215,158,215,153,215,147,215,162	\05D0\05D9\05DF \05DE\05D9\05D3\05E2

[Updated on: Mon, 27 October 2014 07:09]

Report message to a moderator

Re: Importing Hebrew, using ODBC from Excel [message #626370 is a reply to message #626369]

Mon, 27 October 2014 07:15

Michel Cadot
Messages: 68729
Registered: March 2007
Location: Saint-Maur, France, https...

Senior Member
Account Moderator

Quote:

Gives me:

Is not the first column what you want?

Report message to a moderator

Re: Importing Hebrew, using ODBC from Excel [message #626371 is a reply to message #626370]

Mon, 27 October 2014 07:18

Analyst
Messages: 45
Registered: June 2014

Member

My questions was about importing from Excel to Oracle. The Hebrew fields, imported via ODBC from Excel are not displayed correctly.
The Hebrew fields, which are in my Database now (like the one I pasted) - are displayed in a proper way.

Report message to a moderator

Re: Importing Hebrew, using ODBC from Excel [message #626372 is a reply to message #626371]

Mon, 27 October 2014 07:23

Analyst
Messages: 45
Registered: June 2014

Member

Maybe I misunderstood you.

If I run the command on my imported from Excel Hebrew column:

Select HEBREW_COLUMN,
       Dump(HEBREW_COLUMN) dmpval, 
       Asciistr(HEBREW_COLUMN) ascstr
From TEST_TABLE

I'm getting this:

áãé÷ä	Typ=1 Len=10: 195,161,195,163,195,169,195,183,195,164	\00E1\00E3\00E9\00F7\00E4

Report message to a moderator

Re: Importing Hebrew, using ODBC from Excel [message #626374 is a reply to message #626372]

Mon, 27 October 2014 07:27

Michel Cadot
Messages: 68729
Registered: March 2007
Location: Saint-Maur, France, https...

Senior Member
Account Moderator

So the problem comes from the way you imported them from Excel as you didn't imported Hebrew characters but their replacement ones.
You say you did it via ODBC but how and what was the driver (editor/version) and what were the parameters of your ODBC DSN?

Report message to a moderator

Re: Importing Hebrew, using ODBC from Excel [message #626380 is a reply to message #626374]

Mon, 27 October 2014 07:52

Analyst
Messages: 45
Registered: June 2014

Member

The ODBC driver I used - Microsoft Excel driver (*xls,*xlsx,*xlsm,*xlsb), version 14.00.7010.1000.

Creating the connection I made the following steps:

1) Using ODBC Microsoft Excel Setup dialog box, I created a system data source with name ODBC_IMPORT and chose there Version Excel 12.0.
2) I copied a file named 'inithsodbc.ora' in ORACLE_HOME\hs\admin, called it InitODBC_IMPORT.ora and substituted its content with this:

HS_FDS_CONNECT_INFO = ODBC_IMPORT
 HS_FDS_TRACE_LEVEL = 0

3) I added to the SID_LIST of the LISTENER.ORA file (in ORACLE_HOME\Network\admin) the following entry:

(SID_DESC=
(SID_NAME=ODBC_IMPORT)
(ORACLE_HOME=My ORACLE_HOME
(PROGRAM=hsodbc)
)
)

4) I added to the TNSNAMES.ORA file (in ORACLE_HOME\Network\admin) the following entry:

ODBC_IMPORT =
(DESCRIPTION=
(ADDRESS_LIST=
(ADDRESS=
(PROTOCOL=TCP)
(HOST=localhost)
(PORT=1521)
)
)
(CONNECT_DATA=(SID=ODBC_IMPORT))
(HS=OK)
)

5) Finally, I created a database link to the excel file with the following command:

Create Public Database Link ODBC_IMPORT_ANALYST
Connect to "home\tangt"
Identified by taktangspassword
Using 'ODBC_IMPORT';

This was a brief of a manual for creating ODBC connection from https://asktom.oracle.com Smile

Smile

Report message to a moderator

Re: Importing Hebrew, using ODBC from Excel [message #626381 is a reply to message #626380]

Mon, 27 October 2014 08:22

Michel Cadot
Messages: 68729
Registered: March 2007
Location: Saint-Maur, France, https...

Senior Member
Account Moderator

In your Windows registry, what is the value for: HKLM\Software\Oracl`\<your Oracle home name>\NLS_LANG?
In the environment of the account which has imported the data, is there any NLS_LANG or NLS_CHARACTERSET set? (If it is your account check Computer\Properties\Advanced system Properties\Environment variables.)

Report message to a moderator

Re: Importing Hebrew, using ODBC from Excel [message #626382 is a reply to message #626381]

Mon, 27 October 2014 08:34

Analyst
Messages: 45
Registered: June 2014

Member

I hope, I understood you right. I went to my Windows registry path HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\KEY_OraDB12Home1.
The value in NLS_LANG is AMERICAN_AMERICA.WE8MSWIN1252.

Should I change it to any other (Hebrew oriented)? If I change it, does it affect any other things in my computer?

Yes, it is my account on my work laptop. I checked Computer\Properties\Advanced system Settings\Advanced\Environment variables.
I don't see there any variables, named NLS_LANG or NLS_CHARACTERSET. Although, there is a variable named ORACLE_HOME.

Report message to a moderator

Re: Importing Hebrew, using ODBC from Excel [message #626384 is a reply to message #626382]

Mon, 27 October 2014 09:04

Michel Cadot
Messages: 68729
Registered: March 2007
Location: Saint-Maur, France, https...

Senior Member
Account Moderator

Quote:

The value in NLS_LANG is AMERICAN_AMERICA.WE8MSWIN1252.

This explains what you have. WE8MSWIN1252 does not support Hebrew characters so when you tried to import them they have been replaced by what Oracle calls a replacement character which is, if possible, the character the closest to the original one or, by default, a generic replacement character (which is ¿ in WE8MSWIN1252).

During the process of importing (and before starting your SQL*Plus that will load the Excel data) change this value to AMERICAN_AMERICA.AL16UTF16 (if this does work try AL32UTF8).

But first, do you see the Hebrew characters in your Excel sheet?

Report message to a moderator

Re: Importing Hebrew, using ODBC from Excel [message #626385 is a reply to message #626384]

Mon, 27 October 2014 09:15

Analyst
Messages: 45
Registered: June 2014

Member

Yes, of course. In Excel I see Hebrew in a good way.
I don't use SQL*Plus. I'm working with SQL Developer. As I posted before, my DB has the following parameters:

NLS_NCHAR_CHARACTERSET	AL16UTF16
NLS_CHARACTERSET	AL32UTF8

I'll try them both.

Should I add any new Environment variables as well?

Report message to a moderator

Re: Importing Hebrew, using ODBC from Excel [message #626389 is a reply to message #626385]

Mon, 27 October 2014 09:26

Michel Cadot
Messages: 68729
Registered: March 2007
Location: Saint-Maur, France, https...

Senior Member
Account Moderator

Here the important thing is to set the character set the client (program) will use, here SQL Developer.
I don't use it but modifying NLS_LANG in the registry before you launch SQL Developer should work.
As far as I remember, you can change SQL Developer encoding in Tools/Preferences/Environment box, try to use one of the UTF-16 or UTF-32 options.

Report message to a moderator

Re: Importing Hebrew, using ODBC from Excel [message #626393 is a reply to message #626366]

Mon, 27 October 2014 09:56

thatjeffsmith
Messages: 81
Registered: July 2009
Location: Raleigh, NC

Member

I don't think you're really using SQL Developer - except to look at the data once you've already brought it in, correct?

SQL Developer is 100% Unicode compatible - most display issues in the tool come down to not using the right display FONT.

You should be able to skip all the ODBC link to Oracle stuff, and just have SQL Developer read your Excel file directly and import it in.

Report message to a moderator

Re: Importing Hebrew, using ODBC from Excel [message #626394 is a reply to message #626389]

Mon, 27 October 2014 09:58

Analyst
Messages: 45
Registered: June 2014

Member

I changed the NLS_LANG registry value to AMERICAN_AMERICA.AL16UTF16 and restarted my SQL Developer.

Now I get a new error, while trying to import to Oracle from the same Excel file:

ORA-28545: Net8 אבחן שגיאה במהלך ההתחברות לסוכן
Unable to retrieve text of NETWORK/NCR message 65535
ORA-02063: שגיאה מקדימה 2 lines מתוך ODBC_IMPORT_ANALYST
28545. 0000 -  "error diagnosed by Net8 when connecting to an agent"
*Cause:    An attempt to call an external procedure or to issue SQL
           to a non-Oracle system on a Heterogeneous Services database link
           failed at connection initialization.  The error diagnosed
           by Net8 NCR software is reported separately.
*Action:   Refer to the Net8 NCRO error message.  If this isn't clear,
           check connection administrative setup in tnsnames.ora
           and listener.ora for the service associated with the
           Heterogeneous Services database link being used, or with
           'extproc_connection_data' for an external procedure call.
Error at Line: 59 Column: 17

I don't remember that I changed any of ODBS parameters or tnsnames.ora or listener.ora.
Do you know - what may be the reason? It worked before.

Report message to a moderator

Re: Importing Hebrew, using ODBC from Excel [message #626395 is a reply to message #626393]

Mon, 27 October 2014 10:07

Analyst
Messages: 45
Registered: June 2014

Member

thatjeffsmith wrote on Mon, 27 October 2014 16:56

I don't think you're really using SQL Developer - except to look at the data once you've already brought it in, correct?

SQL Developer is 100% Unicode compatible - most display issues in the tool come down to not using the right display FONT.

You should be able to skip all the ODBC link to Oracle stuff, and just have SQL Developer read your Excel file directly and import it in.

I use SQL to take the raw data from our ERP databases, process it and build flat panels of data for my analysis tasks in the Oracle DB, that I created by myself. I am an analyst, "looking at data" as you say, and not a DBA at all.

I am trying to solve the issues by myself, because we have no DBA staff. Don't know what you mean by "skip all the ODBC link to Oracle stuff". If I understand right, the purpose of this forum is to help in such problems.

Report message to a moderator

Re: Importing Hebrew, using ODBC from Excel [message #626403 is a reply to message #626394]

Mon, 27 October 2014 11:49

Michel Cadot
Messages: 68729
Registered: March 2007
Location: Saint-Maur, France, https...

Senior Member
Account Moderator

Quote:

I don't remember that I changed any of ODBS parameters or tnsnames.ora or listener.ora.

The reason may be in the character AL16UTF16 is not supported.
Try with UTF8.

Report message to a moderator

Re: Importing Hebrew, using ODBC from Excel [message #626466 is a reply to message #626403]

Tue, 28 October 2014 05:11

Analyst
Messages: 45
Registered: June 2014

Member

Hi, I used this AMERICAN_AMERICA.AL32UTF8 for NLS_LANG registry value. It helped partially.

When I make a direct query from Excel file with SQL Developer:

Select *
From DATA$@ODBC_IMPORT_ANALYST;

I see Hebrew:

בדיקה

But if I insert the Hebrew values in Oracle table:

Insert into TEST_TABLE
Select *
From DATA$@ODBC_IMPORT_ANALYST;

I see it like this now:

힑힓힙힧힔

Maybe I should define some new Environment Variable or something?

Report message to a moderator

Re: Importing Hebrew, using ODBC from Excel [message #626467 is a reply to message #626466]

Tue, 28 October 2014 05:17

Michel Cadot
Messages: 68729
Registered: March 2007
Location: Saint-Maur, France, https...

Senior Member
Account Moderator

Try with just UTF8 not AL32UTF8.

Report message to a moderator

Re: Importing Hebrew, using ODBC from Excel [message #626469 is a reply to message #626467]

Tue, 28 October 2014 05:25

Michel Cadot
Messages: 68729
Registered: March 2007
Location: Saint-Maur, France, https...

Senior Member
Account Moderator

By the way, what are your Windows code pages?
See registry key HKLM\SYSTEM\CurrentControlSet\Control\Nls\CodePage, values ACP and OEMCP.

Report message to a moderator

Re: Importing Hebrew, using ODBC from Excel [message #626470 is a reply to message #626469]

Tue, 28 October 2014 05:31

Analyst
Messages: 45
Registered: June 2014

Member

ACP - 1255,
OEMCP - 862.

Report message to a moderator

Re: Importing Hebrew, using ODBC from Excel [message #626471 is a reply to message #626470]

Tue, 28 October 2014 05:35

Michel Cadot
Messages: 68729
Registered: March 2007
Location: Saint-Maur, France, https...

Senior Member
Account Moderator

So also try with NLS_LANG=xxx_xxx.IW8MSWIN1255

Report message to a moderator

Re: Importing Hebrew, using ODBC from Excel [message #626475 is a reply to message #626471]

Tue, 28 October 2014 05:56

Analyst
Messages: 45
Registered: June 2014

Member

I'll try.

Do I need to restart after changing the NLS_LANG registry value?

Report message to a moderator

Re: Importing Hebrew, using ODBC from Excel [message #626476 is a reply to message #626475]

Tue, 28 October 2014 06:09

Michel Cadot
Messages: 68729
Registered: March 2007
Location: Saint-Maur, France, https...

Senior Member
Account Moderator

You only need to restart SQL Developer.

Report message to a moderator

Re: Importing Hebrew, using ODBC from Excel [message #626480 is a reply to message #626476]

Tue, 28 October 2014 06:48

Analyst
Messages: 45
Registered: June 2014

Member

After changing it to AMERICAN_AMERICA.IW8MSWIN1255 I see Hebrew in imported from Excel tables correctly.
But now I have a problem bringing Hebrew data from our ERP Oracle DB.
Now I see Hebrew from there like this ôøéè ìáéèåì òéñ÷àåú.

[Updated on: Tue, 28 October 2014 06:49]

Report message to a moderator

Re: Importing Hebrew, using ODBC from Excel [message #626481 is a reply to message #626480]

Tue, 28 October 2014 06:53

BlackSwan
Messages: 26766
Registered: January 2009
Location: SoCal

Senior Member

do you have a data storage problem or a data presentation problem?

select acsiistr(hebrew_col) from hebrew_tbl where id = 1;
post results from similar SQL transformed to meet you specific requirements

Report message to a moderator

Re: Importing Hebrew, using ODBC from Excel [message #626482 is a reply to message #626480]

Tue, 28 October 2014 07:02

Michel Cadot
Messages: 68729
Registered: March 2007
Location: Saint-Maur, France, https...

Senior Member
Account Moderator

Quote:

But now I have a problem bringing Hebrew data from our ERP Oracle DB.

This is the same problem, your query tool must have been configured to support Hebrew characters.
First see NLS_LANG when it was started. Fix it and restart the tool.

Report message to a moderator

Re: Importing Hebrew, using ODBC from Excel [message #626483 is a reply to message #626482]

Tue, 28 October 2014 07:07

Analyst
Messages: 45
Registered: June 2014

Member

do you have a data storage problem or a data presentation problem?

select acsiistr(hebrew_col) from hebrew_tbl where id = 1;
post results from similar SQL transformed to meet you specific requirements

Now I have presentation and storage data problem bringing it from External Oracle DB, to which I connect with DB link.
Doing This on that External Oracle DB

Select Asciistr(ITEMS.LOCAL_NAME) as ACSII_ITEM_NAME, 
       ITEMS.LOCAL_NAME
From ITEMS@EXTERNAL_DB_LINK;

Gives me this:

\00F4\00F8\00E9\00E8 \00EC\00E1\00E9\00E8\00E5\00EC \00F2\00E9\00F1\00F7\00E0\00E5\00FA	ôøéè ìáéèåì òéñ÷àåú

This is the same problem, your query tool must have been configured to support Hebrew characters.
First see NLS_LANG when it was started. Fix it and restart the tool.

I don't understand. Where should I see NLS_LANG?

[Updated on: Tue, 28 October 2014 07:08]

Report message to a moderator

Re: Importing Hebrew, using ODBC from Excel [message #626484 is a reply to message #626483]

Tue, 28 October 2014 07:11

Michel Cadot
Messages: 68729
Registered: March 2007
Location: Saint-Maur, France, https...

Senior Member
Account Moderator

Quote:

Where should I see NLS_LANG?

In the client that queries your ERP database.

Report message to a moderator

Re: Importing Hebrew, using ODBC from Excel [message #626486 is a reply to message #626484]

Tue, 28 October 2014 07:15

Analyst
Messages: 45
Registered: June 2014

Member

I ran the following in my client (SQL Developer):

Select *
From v$nls_parameters

Select * 
From nls_database_parameters

I get this in both cases:

NLS_CHARACTERSET AL32UTF8
NLS_NCHAR_CHARACTERSET AL16UTF16

Report message to a moderator

Re: Importing Hebrew, using ODBC from Excel [message #626487 is a reply to message #626486]

Tue, 28 October 2014 07:21

Michel Cadot
Messages: 68729
Registered: March 2007
Location: Saint-Maur, France, https...

Senior Member
Account Moderator

This gives information about DATABASE character set NOT client one.
Query V$SESSION_CONNECT_INFO.

Report message to a moderator

Re: Importing Hebrew, using ODBC from Excel [message #626489 is a reply to message #626487]

Tue, 28 October 2014 07:48

Analyst
Messages: 45
Registered: June 2014

Member

This query:

Select *
From V$SESSION_CONNECT_INFO

doesn't give any data about NLS_LANG.
I post what I get with above query:

SID	SERIAL#	AUTHENTICATION_TYPE	OSUSER	NETWORK_SERVICE_BANNER
251	41	DATABASE	Analyst	Windows NT TCP/IP NT Protocol Adapter for 64-bit Windows: Version 12.1.0.1.0 - Production
251	41	DATABASE	Analyst	Encryption service for 64-bit Windows: Version 12.1.0.1.0 - Production
251	41	DATABASE	Analyst	Crypto-checksumming service for 64-bit Windows: Version 12.1.0.1.0 - Production

CLIENT_CHARSET	CLIENT_CONNECTION	CLIENT_OCI_LIBRARY	CLIENT_VERSION	CLIENT_DRIVER	CLIENT_LOBATTR	CLIENT_REGID	CON_ID
Unknown	Heterogeneous	Unknown	12.1.0.1.0	jdbcthin	Client Temp Lob Rfc On	0	1
Unknown	Heterogeneous	Unknown	12.1.0.1.0	jdbcthin	Client Temp Lob Rfc On	0	1
Unknown	Heterogeneous	Unknown	12.1.0.1.0	jdbcthin	Client Temp Lob Rfc On	0	1

Report message to a moderator

Re: Importing Hebrew, using ODBC from Excel [message #626492 is a reply to message #626489]

Tue, 28 October 2014 07:51

Michel Cadot
Messages: 68729
Registered: March 2007
Location: Saint-Maur, France, https...

Senior Member
Account Moderator

I don't understand you said:

Quote:

After changing it to AMERICAN_AMERICA.IW8MSWIN1255 I see Hebrew in imported from Excel tables correctly.
But now I have a problem bringing Hebrew data from our ERP Oracle DB.
Now I see Hebrew from there like this ôøéè ìáéèåì òéñ÷àåú.

So what do you do when you see the data correctly and what do you do when you don't?

Report message to a moderator

Re: Importing Hebrew, using ODBC from Excel [message #626493 is a reply to message #626492]

Tue, 28 October 2014 07:56

Analyst
Messages: 45
Registered: June 2014

Member

After the registry NLS_LANG value change to AMERICAN_AMERICA.IW8MSWIN1255:

When I bring Hebrew data from Excel via ODBC and store it - I see it correctly.

When I bring Hebrew data from another Oracle DB (from ERP) via database link, I see Hebrew like this: ôøéè ìáéèåì òéñ÷àåú.

Report message to a moderator

Re: Importing Hebrew, using ODBC from Excel [message #626495 is a reply to message #626493]

Tue, 28 October 2014 08:00

Michel Cadot
Messages: 68729
Registered: March 2007
Location: Saint-Maur, France, https...

Senior Member
Account Moderator

Not clear, post both queries.

Report message to a moderator

Re: Importing Hebrew, using ODBC from Excel [message #626496 is a reply to message #626495]

Tue, 28 October 2014 08:02

BlackSwan
Messages: 26766
Registered: January 2009
Location: SoCal

Senior Member

Please read and follow the forum guidelines, to enable us to help you:

http://www.orafaq.com/forum/t/88153/0/ and read http://www.orafaq.com/forum/t/174502/

Report message to a moderator

Re: Importing Hebrew, using ODBC from Excel [message #626499 is a reply to message #626496]

Tue, 28 October 2014 08:06

Analyst
Messages: 45
Registered: June 2014

Member

When I query Hebrew data from Excel:

Select *
From DATA$@ODBC_IMPORT_ANALYST;

I see it correctly:

בדיקה

When I query Hebrew data from another Oracle DB (from ERP) via database link:

Select Asciistr(ITEMS.LOCAL_NAME) as ACSII_ITEM_NAME, 
       ITEMS.LOCAL_NAME as ITEM_NAME
From ITEMS@ERP_ANALYST;

I see it incorrectly:

ACSII_ITEM_NAME	ITEM_NAME
\00F4\00F8\00E9\00E8 \00EC\00E1\00E9\00E8\00E5\00EC \00F2\00E9\00F1\00F7\00E0\00E5\00FA	ôøéè ìáéèåì òéñ÷àåú

Report message to a moderator

Re: Importing Hebrew, using ODBC from Excel [message #626500 is a reply to message #626499]

Tue, 28 October 2014 08:25

Michel Cadot
Messages: 68729
Registered: March 2007
Location: Saint-Maur, France, https...

Senior Member
Account Moderator

Quote:

When I query Hebrew data from another Oracle DB (from ERP) via database link:

I assume this is done with the same client and the same tool but it should be better you specify all of these in your posts.

Conversion occurs during transfer of data because database, the instance or client does not support the characters.
What is the character set of this latter database?
What was NLS_LANG value when the database was started?

Report message to a moderator

Re: Importing Hebrew, using ODBC from Excel [message #626507 is a reply to message #626500]

Tue, 28 October 2014 08:44

Analyst
Messages: 45
Registered: June 2014

Member

Yes, all the queries I do with the same SQL Developer on my computer.

Now we are talking about external DB (Let's call him ERP DB), I use?
What queries should I run on it in order to give you the needed information?

When I query ERP DB:

Select * 
From nls_database_parameters

I get:

NLS_CHARACTERSET	WE8MSWIN1252
NLS_NCHAR_CHARACTERSET	AL16UTF16

Report message to a moderator

Re: Importing Hebrew, using ODBC from Excel [message #626511 is a reply to message #626507]

Tue, 28 October 2014 08:55

Michel Cadot
Messages: 68729
Registered: March 2007
Location: Saint-Maur, France, https...

Senior Member
Account Moderator

WE8MSWIN1252 does not support Hebrew characters.

Report message to a moderator

Pages (2): [1 2 › »]

Previous Topic:	SQL DATA MODEL IS NOT ENABLE!?
Next Topic:	Problem with Arabic language

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Jan 02 18:22:34 CST 2025