My Oracle Support Banner

Corrupted APEX Remains in PDB$SEED after APEX Removed from CDB in 12.1.0.2 DB (Doc ID 2573279.1)

Last updated on MAY 08, 2020

Applies to:

Oracle Application Express (APEX) - Version 4.2.5 and later
Information in this document applies to any platform.

Symptoms

1. APEX was removed from 12.1.0.2 DB using apxremov.sql script.

2. APEX 5.0.3 is installed in the PDB. The PDB has a good, valid installation of APEX 5.0.3 and is working perfectly.

3. APEX Verify Scripts shows that PDB$SEED has a corrupted version of APEX 4.2.5 in it:

a. APEX Version Registered in DBA Registry
api_compatibility || '' from APEX_040200.APEX_RELEASE * ERROR at line 3: ORA-65047: object APEX_040200.APEX_RELEASE is invalid or compiled with errors in CDB$ROOT

b. However, actual query of the DBA Registry shows APEX 4.2.5 and it's showing as valid.

4. CDB has no APEX objects.
5. Installed DB Jan 2019 Bundle Patch which prompts to run this query:

SQL> select time, name,cause,message from pdb_plug_in_violations where status != 'RESOLVED';

and the results are:

<DATE TIME>
PDB$SEED
APEX
APEX mismatch: PDB has installed common APEX. CDB has not installed APEX.

Changes

 Installed DB Jan 2019 Bundle Patch.

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.