Not Able to Access APEX After Creating Database Objects - HTTP 404
(Doc ID 2310961.1)
Last updated on OCTOBER 17, 2023
Applies to:
Oracle Application Express (APEX) - Version 3.2.1 and laterOracle Database Cloud Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
The customer is unable to access APEX after adding additional database objects to the schema. When running APEX, an HTTP 404 error is seen.
http://<HOSTNAME>:<PORT>/apex/f?p=4000:1500:<sessionid>
Prior to adding these objects, APEX ran without error.
Then HTTP response header for the requests returns the following:
Error-Reason:error="procedure"; error_description*=UTF-8''The procedure named
f could not be accessed, it may not be declared or the user executing this
request may not have been granted execute privilege on the procedure. Check
the spelling of the procedure and check that the execute privilege has been
granted to the caller
Changes
The customer created a database object in their workspace schema that conflicted with an existing APEX object.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |