This content has been marked as final. Show 5 replies
we had issues with the wallet key when converting from 4.0 to 4.1, but that caused an
ORA-06502: PL/SQL: numeric or value error: hex to raw conversion error
I never encountered ORA-28817 on that page before. Please help us debug this issue.
(1) Are there any other issues with the migrated Apex instance?
(2) Did you migrate from 4.0 or older to 4.1 before migrating to 4.2?
(3) Are you sure you could access the Instance Settings page in 4.1?
(4) Is a wallet configured? The changed encryption for the wallet password was the reason for that 4.1 bug.
(5) Is a SMTP password configured?
As with some others reporting, I got the dreaded ORA-28817 when attempting to manage the instance settings.
I upgraded from 4.1 to 4.2 a few months back. After reading some of the comments here, I tried applying the Patch Release 4.2.1.00.08 which claims to fix it - but alas - no joy - still can't manage the instance settings.
I can also get the error via the command line:
I am not sure what else to try....
exec apex_instance_admin.set_parameter('WALLET_PWD',Null); BEGIN apex_instance_admin.set_parameter('WALLET_PWD',Null); END; * ERROR at line 1: ORA-28817: PL/SQL function returned an error. ORA-06512: at "SYS.DBMS_CRYPTO_FFI", line 67 ORA-06512: at "SYS.DBMS_CRYPTO", line 44 ORA-06512: at "APEX_040200.WWV_FLOW_CRYPTO", line 89 ORA-06512: at "APEX_040200.WWV_FLOW_SECURITY", line 1931 ORA-06512: at "APEX_040200.WWV_FLOW_INSTANCE_ADMIN", line 197 ORA-06512: at line 1
Version Info: Application Express 4.2.1.00.08
Oracle Database 11g Enterprise Edition Release 184.108.40.206.0 - 64bit Production
PL/SQL Release 220.127.116.11.0 - Production
CORE 18.104.22.168.0 Production
TNS for Linux: Version 22.214.171.124.0 - Production
NLSRTL Version 126.96.36.199.0 - Production
Note - I started a fresh thread for this item.
Edited by: Jon Finke on Mar 27, 2013 3:03 PM
this worked for me:
exec apex_instance_admin.set_parameter('SMTP_PASSWORD','...'); (replace ... with your password)
After this I was able to access instance settings without ORA-28817.
Hope, that will do for you as well!