RE: Hex viewer

No, the hex viewer only shows the hex value of the characters as they are encoded in the Editor. Depending on your version of Toad, the Editor encoding can be ANSI, UTF16, etc. The only sure way to see the hex value of the server data is to ask the server for that value using the dump command.

The NLS_LANG must match your client machine's settings so that Oracle can perform the necessary conversions properly when transferring data between your client and the DB. Mark did a nice write-up for this some time back, but I don't see it from a quick glance at the files section of Yahoo groups. It might have just been in the message body.

Michael

From: [email protected] [mailto:[email protected]] On Behalf Of Wendy Penfold
Sent: Monday, May 14, 2012 4:03 PM
To: [email protected]
Subject: Re: [toad] Hex viewer



So, if I set the NLS_LANG setting in my oracle client correctly, then Toad's hex viewer will display the actual hex value of the characters in my database?

On 5/14/2012 2:42 PM, Norman Dunbar wrote:


On 14/05/12 18:47, Rich Jesse wrote:

> And since those two charactersets don't have to be the same, their
> interpretations of characters don't have to be the same either. That's the
> job of the Oracle Server/Client communications.

Which is why it's always important to get your NLS_LANG setting correct,
otherwise, you can get characterset "conversion" problems.

Discalimer: Phyllis will like the new foxy lady in my life.
http://qdosmsq.dunbar-it.co.uk/blog/2012/05/im-quite-pleased-with-this-photo/

--
Cheers,
Norm. [TeamT]