How to Enable Editioning for APEX After EBS Upgrade from 12.1.3 to 12.2.6
(Doc ID 2295519.1)
Last updated on OCTOBER 25, 2023
Applies to:
Oracle Application Express (APEX) - Version 5.0.0.00.31 and laterOracle Database Cloud Exadata Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Goal
E-Business Suite (EBS) was upgraded from 12.1.3 to 12.2.6, however the following was not done prior to upgrade - Extending Oracle E-Business Suite Release 12.1 and above using Oracle Application Express Revision 2.01
Before running the Oracle E-Business Suite Online Enablement process, it is critical that the Application Express schemas (we are talking about the parsing schemas that APEX uses. APEX schemas like APEX_PUBLIC_USER, APEX_230100, etc.)do not have to be editioned to work well in an EBS environment.") conform to Online Patching Standards as defined in My Oracle Support Knowledge Document 1531121.1. Otherwise, your Application Express extensions will stop working. With Oracle E-Business Suite Release 12.2 the APPS schema will be Edition-Based Redefintion (EBR) enabled to facilitate E-Business Suite Online Patching. Attempting to access editioned objects from a non-editioned schema will cause Oracle errors.
APEX does run successfully outside of EBS, but fails when it is called from EBS.
Is there a workaround or a fix to recover from this?
Solution
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
| Goal |
| Solution |
| References |