Comments on: Oracle APEX: Got a 404 Not Found?

By: peter rurenga

peter rurenga — Mon, 25 Oct 2010 23:19:02 +0000

Hi Patrick, this really helped me out.
An unable to extend error caused the problem. Wouldn’t have thought of that so quickly!
Thanks again.
Peter

By: Michelle Skamene

Michelle Skamene — Thu, 12 Aug 2010 20:32:51 +0000

Hi Patrick,
Do you have any tips for checking the cause of the 404 error on a hosted instance?? I have been getting this error on a couple of my pages since the recent APEX 4.0, and it is causing my users a lot of grief (kids, by the way!!!). I am afraid I don’t know where to start investigating…
Many thanks!
Michelle

By: Kamran

Kamran — Wed, 31 Mar 2010 11:27:55 +0000

Good to see the error message rather than 404 error. I had been updating APEX with a hope that it will fix the problem but it appears that issue is inherited from XE Database that cannot be patched. Oracle does offer XE for free but unfortunately there is no support or patching and with License Agreement it is not clear whether the later patch that fixes this error on database will violate the XE license.

By: Bernd_Herbert

Bernd_Herbert — Thu, 25 Mar 2010 07:09:38 +0000

Many thanks for this information. This helped us to locate faster and easily problems, which have nothing to do with the APEX applications itself but with the environment.

By: samson

samson — Tue, 23 Feb 2010 10:25:10 +0000

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

By: Patrick Wolf

Patrick Wolf — Fri, 19 Feb 2010 10:59:18 +0000

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

By: samson

samson — Thu, 18 Feb 2010 07:13:45 +0000

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

By: daneska

daneska — Tue, 15 Dec 2009 11:14:26 +0000

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.

By: Fehler 404 - die Lösung | Der Oracle APEX Experten Blog

Fehler 404 - die Lösung | Der Oracle APEX Experten Blog — Fri, 30 Jan 2009 17:14:35 +0000

[...] an Patrick Wolf und Dietmar Aust für diesen wertvollen Tipps. « Bug im CSV-Export der Interactive [...]