Dbms_crypto.encrypt_rc4 doesn´t work with special characters

Question

Hi.
I´m using this funtion to cryptografy but when I put this characters, doesn´t work.
Does anyone have any ideia the whats happening, thank you
FUNCTION fnc_get_enc_val_rc4 (
p_in_val IN VARCHAR2,
p_key IN VARCHAR2,
p_iv IN VARCHAR2 := NULL
RETURN VARCHAR2
IS
l_enc_val RAW (4000);
l_enc_algo PLS_INTEGER;
l_in RAW (4000);
l_iv RAW (4000);
l_key RAW (4000);
l_ret VARCHAR2 (4000);
BEGIN
l_enc_algo := dbms_crypto.encrypt_rc4;
l_in := utl_i18n.string_to_raw (p_in_val, 'AL32UTF8');
l_iv := utl_i18n.string_to_raw (p_iv, 'AL32UTF8');
l_key := utl_i18n.string_to_raw (p_key, 'AL32UTF8');
--l_key := utl_i18n.string_to_raw (UTL_I18N.UNESCAPE_REFERENCE(p_key), 'AL32UTF8');
--utl_i18n. AL32UTF8
--sys.utl_i
l_enc_val :=
dbms_crypto.encrypt (src => l_in,
KEY => l_key,
iv => l_iv,
typ => l_enc_algo
+ dbms_crypto.chain_cbc
+ dbms_crypto.pad_pkcs5
dbms_output.put_line (l_enc_val);
l_ret := RAWTOHEX (l_enc_val);
RETURN l_ret;
END;
fnc_get_enc_val_rc4 ('eT1yD','!@#$%&/()=?¿')
must return 16 9E 76 AD 38
but returns 43 45 25 92 4A
to skip some replies
I already did
utl_i18n.escape_reference
utl_i18n.unescape_reference
change the AL32UTF8 fopr others
if I use with others values end keys, its ok, but with this key don´t....its a bug...?
tks
I m using oracle 10g

Answer 1

890408 wrote:
Database A: WE8ISO8859P15
Database B: WE8MSWIN1252
When i do a dump(desc) on both columns I get for the reversed question mark on DB A ASCII Code 133, and for DB B I get 191.This has nothing to do with group by, from what you describe.
It seems you have a illegal character and replacement character in the db's.
How did you insert these two characters/rows and please also post actual dump output (including the query, select col, dump(col,1016), ...).
How I can I convert between the different character sets, so that my GROUP BY works as well?Firstly, you need to make sure the database character sets are capable of storing every character from your clients/apps and that you have a properly setup locale on the client side (including matching char set part of NLS_LANG).
E.g. a win-1252 client is not supported by a iso 8859-15 server, at least not if you are using or plan to use 'windows specific' characters (like the ... ellipsis).