Maybe you also already got the 404 Not Found error message
The requested URL /pls/apex/wwv_flow.accept was not found on this server.
when you submit an Oracle APEX page, …
There are a lot of reasons why this error can occur. But the above error message doesn’t tell you a lot about the root cause of the problem. The real error message can be found on your Apache Web server in the Apache\Apache\logs\error_log.xxxxx file. There you will find and entry like
[Thu Apr 3 ...] mod_plsql: /pls/htmldb/wwv_flow.accept HTTP-404 wwv_flow.accept: SIGNATURE (parameter names) MISMATCH VARIABLES IN FORM NOT IN PROCEDURE: P_T02XXX NON-DEFAULT VARIABLES IN PROCEDURE NOT IN FORM:
Without the above information, you have no chance to find out what’s causing the 404 error. But the problem is, that most developers don’t have access to the application server.
You don’t have to!
Just put
<Location /pls/apex> ... PlsqlErrorStyle DebugStyle ...
into your dads.conf/marvel.conf and after restarting the Apache server you will get the error message directly in your browser.
For more details about PlsqlErrorStyle, have a look at the documentation.
Note: Only use this setting on developments systems, because on production systems a hacker might get more information as he should!
Credit for this tip goes to Dietmar Aust!
December 15th, 2009 at 12:14
Hi, Patrick! And what if I use apex with embedded pl/sql gateway. There is no Apache web server outside. In this case, where these log files with errors description could be placed? I have no idea though I need it indeed.
February 18th, 2010 at 08:13
Hi Patrick,
I have the same problem like daneska.
My problem (look at http://www.htmldb.de/htmldb/read.php?4,2078) can not be identified.
Where can I find some errormessages in this case?
Kindly regards
Samson
February 19th, 2010 at 11:59
Hi Samson and Daneska,
have a look at http://blog.oracleapex.at/fehler-404-die-losung/ which explains how you can do that for the Embedded PL/SQL gateway (EPG) as well.
You just have to execute
SQL>exec dbms_epg.set_dad_attribute(’APEX’, ‘error-style’, ‘DebugStyle’);
Hope that helps
Patrick
February 23rd, 2010 at 11:25
Localized problem.
A nice colleague of us caring Company (DBA) has found in Internernet the statement.
Guilt is a bug in OracleXE that occurs when using Database link (Declaration Metalink 6798427.8).
Accordingly, I can not use the XE database as planned, because I wanted APEX run on XE-database, and everything connected via DB link with the environment.
Too bad the XE is certainly not maked “bug-free”.
Regards
Samson