ORDS-22001 After Upgrading Apex And Ords To 22.1
(Doc ID 2881783.1)
Last updated on AUGUST 13, 2024
Applies to:
Oracle REST Data Services - Version 22.2 and laterInformation in this document applies to any platform.
Symptoms
When trying to access any apex page, getting:
ORDS-22001: The procedure named apex 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, or a function specified by security.requestValidationFunction configuration property has prevented access. Check the spelling of the procedure, check that the execute privilege has been granted to the caller and check the configured security.requestValidationFunction function.
When modifying the pool.xml to exclude
wwv_flow_epg_include_modules.authorize
it does work. However, this is not a solution to be followed, from security reasons.
In the following :
When modifying the pool.xml to exclude
wwv_flow_epg_include_modules.authorize
and
ords_util.authorize_plsql_gateway
If using the PL/SQL Gateway Procedure Allow List, check that the procedure has been allowed via ords_admin.add_plsql_gateway_procedure.
Changes
Upgraded Apex to 22.1 and ORDS to 22.2
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 |