We have recently converted our 11g DB character set to UTF8, since then we are not able to view data in the data grid for some of the columns that has encrypted data.
How can this be resolved? We do not have any issues when we use SQLDeveloper to view data.
If it’s Oracle’s Transparent Data Encryption, there shouldn’t be anything that you have to do in Toad to see the data. If it’s some other kind of encryption, I guess I’ll need more information.
OK. Toad doesn’t have any built-in mechanism to automatically decrypt columns that are encrypted that way. You’d have to include the decrypt calls in your SQL statement. I don’t know what SQLDeveloper is doing, but if you feel it’s a bug in Toad, I’ll need some steps to reproduce the problem.
I used that toolkit some time back to create a Web based password vault under 9i. If I remember correctly, I had to use RAW or BLOB data types to hold the encrypted data. Not sure if the toolkit is improved or different/better these days as I haven't needed to use it lately.
HTH.
Cheers,
Norm [ TeamT ]
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Does the encryption result in null (0) character as part of it? Select from that column so that you see the data in hex (the Oracle function to do so slips my
mind) and look for null character. If you see this then Toad will only display the data up to the null as null character terminates strings in the language Toad is written in, Delphi. Do not select from the column and then use Toad's built-in hex viewer as
this will not work.
The best way we can help you is if you can provide us specific information on what you’re doing, what you’re attempting to do, what your operating environment is like, and what is being output.
So far, all we know is:
You’re presumably using Toad
You have Oracle 11g
You’re using DBMS_OBFUSCATION_TOOLKIT
Something works in SQL*Dev and not in Toad.
I hope you can see that from our point of view, there’s not really a lot to go on here. The details are important, so some information that would be a good start for troubleshooting might be:
Version of Toad, including 32/64-bit
Version of Windows
Specific Oracle server version/platform
Specific Oracle client installation and version
Example SQL statement and the means to recreate it (e.g. table layout).
It might also help knowing if your SQL*Dev and Toad are both using the same Oracle Client.
You’re getting into the fun world of encryption and (potentially) character set translations in Oracle, and it can be a bit of a challenge. Let us know more details about your setup and hopefully we can help you troubleshoot!