Not Able to Access APEX After Creating Database Objects - HTTP 404

(Doc ID 2310961.1)

Last updated on SEPTEMBER 25, 2017

Applies to:

Oracle Application Express (formerly HTML DB) - Version 3.2.1 and later
Oracle Database as a Service - Version N/A and later
Oracle Database Exadata Express Cloud 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

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms