Recently we were performing a database upgrade from release 220.127.116.11 to 10.2.0.4. After the successful upgrade we were issuing a problem to reach APEX. We’ve tried to browse to the APEX URL ( :/pls/apex”>http://:/pls/apex ) and the only thing we were receiving was a blank page. The strange thing is that the APEX URL has been rewriten to :/pls/apex/apex”>http://:/pls/apex/apex
There were no errors in the error.log of the Apache and only HTTP 200 entries were written to the access.log of the Apache.
When trying to reach an existing APEX application ::/pls/apex/f?p=120″>http://::/pls/apex/f?p=120 it wasn’t possible to reach the application but the error.log did write some error entries in the error.log of the Apache.
[Wed Sep 17 06:40:19 2008] [error] [client 18.104.22.168] [ecid: 1221626419:22.214.171.124:5604:7448:145,0] mod_plsql: /pls/apex/f HTTP-404 ORA-06550: line 1, column 35:\nPLS-00201: identifier ‘SYS.DBMS_CRYPTO’ must be declared\nORA-06550: line 1, column 7:\nPL/SQL: Statement ignored\nORA-06512: at “FLOWS_030100.F”, line 279\nORA-06512: at line 31\n
The problem we were facing after the upgrade was a missing grant on the SYS.DBMS_CRYPTO to FLOWS_030100. DBMS_CRYPTO came into the picture from 10G. In previous releases such as 9i the DBMS_OBFUSCATION package is used. The grants to those packages were giving at the APEX install. Upgrading the database after APEX install needs a manually grant of this DBMS_CRYPTO package.