Encryption results in 8i and 9i are different

Question

I have the problem with encryption of data with DES key (DBMS_OBFUSCATION_TOOLKIT package). Encryption resuls are different in 8i and 9i database. I have data encrypted in 8i db and i am unable to decrypt them in 9i db. Have anyone same experience and some solution?
There are different result with example code from bulletin "Encrypting Data using the DBMS_OBFUSCATION_TOOLKIT package" - Doc ID: Note:102902.1:
===============================================================
set serveroutput on;
CLEAR BUFFER
PROMPT Please enter a password - Must be 8 characters !
PROMPT
ACCEPT PASSWD
DECLARE
input_string VARCHAR2(16) := 'abcdefgh';
raw_input RAW(128) := UTL_RAW.CAST_TO_RAW(input_string);
key_string VARCHAR2(16) := 'keepthesecretnum';
raw_key RAW(128) := UTL_RAW.CAST_TO_RAW(key_string);
encrypted_raw RAW(2048);
encrypted_string VARCHAR2(2048);
decrypted_raw RAW(2048);
decrypted_string VARCHAR2(2048);
error_in_input_buffer_length EXCEPTION;
PRAGMA EXCEPTION_INIT(error_in_input_buffer_length, -28232);
INPUT_BUFFER_LENGTH_ERR_MSG VARCHAR2(100) :=
'*** DES INPUT BUFFER NOT A MULTIPLE OF 8 BYTES - IGNORING EXCEPTION ***';
double_encrypt_not_permitted EXCEPTION;
PRAGMA EXCEPTION_INIT(double_encrypt_not_permitted, -28233);
DOUBLE_ENCRYPTION_ERR_MSG VARCHAR2(100) :=
'*** CANNOT DOUBLE ENCRYPT DATA - IGNORING EXCEPTION ***';
-- 1. Begin testing raw data encryption and decryption
BEGIN
dbms_output.put_line('> ========= BEGIN TEST RAW DATA =========');
dbms_output.put_line('> Raw input : ' ||
UTL_RAW.CAST_TO_VARCHAR2(raw_input));
BEGIN
dbms_obfuscation_toolkit.DESEncrypt(input => raw_input,
key => raw_key, encrypted_data => encrypted_raw );
dbms_output.put_line('> encrypted hex value : ' ||
rawtohex(encrypted_raw));
dbms_obfuscation_toolkit.DESDecrypt(input => encrypted_raw,
key => raw_key, decrypted_data => decrypted_raw);
dbms_output.put_line('> Decrypted raw output : ' ||
UTL_RAW.CAST_TO_VARCHAR2(decrypted_raw));
dbms_output.put_line('> ');
if UTL_RAW.CAST_TO_VARCHAR2(raw_input) =
UTL_RAW.CAST_TO_VARCHAR2(decrypted_raw) THEN
dbms_output.put_line('> Raw DES Encyption and Decryption successful');
END if;
EXCEPTION
WHEN error_in_input_buffer_length THEN
dbms_output.put_line('> ' || INPUT_BUFFER_LENGTH_ERR_MSG);
END;
dbms_output.put_line('> ');
END;
===============================================================
Result in 8i (8.1.7.0.0):
========= BEGIN TEST RAW DATA =========
Raw input : abcdefgh
encrypted hex value : 13E7047CADC24D5E
Decrypted raw output : abcdefgh
Raw DES Encyption and Decryption successful
Result in 9i (9.0.1.0.0):
========= BEGIN TEST RAW DATA =========
Raw input : abcdefgh
encrypted hex value : FBC0CF116D1B48E8
Decrypted raw output : abcdefgh
Raw DES Encyption and Decryption successful

Answer 1

I know Oracle intended to introduce stronger encryption in 9i, but I thought they did that by adding new procedures. I know they occasionally change the hashing algorithm, so you have to be careful with stored passwords and the like. But if they really have screwed up the DESEncrypt function, that is very poor.
I would recommend you contact Support about it. If you don't have a support contract and this is a bug then I think the only thing you can do is to restore your 8i database, decrypt the data, then do the ungrade and re-encrypt. But this sort of thing really ought to be in the Release Notes.
Good luck, APC