Invalid Objects on Custom Schemas After Upgrading APEX To 22.1
(Doc ID 2878055.1)
Last updated on APRIL 29, 2024
Applies to:
Oracle Application Express (APEX) - Version 22.1 and laterOracle Cloud Infrastructure - Database Service - Version N/A and later
APEX Application Development - Version NA and later
Information in this document applies to any platform.
Symptoms
On : APEX 22.1 version, Administration
ACTUAL BEHAVIOR
---------------
Several invalid objects on custom schemas after update to APEX 22
sample object:
APEX$_WS_ROWS_T1 TRIGGER
EXPECTED BEHAVIOR
-----------------------
No Invalid objects
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Upgrade to APEX 22
2. Review invalid objects with view dba_objects
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 |
Cause |
Solution |
References |