Once you have verified that your upgrade installation was successful and all upgraded applications function properly, you should remove schemas from prior Oracle Application Express installations.
catcon.pl
to remove schemas of prior installations in a CDB.Learn about removing schemas from a prior installation by verifying if a prior installation exists.
The database users associated with schemas from prior installations are privileged users and should be removed when they are no longer necessary. Removing schemas from a prior installation is a two step process. First you verify if a prior installation exists and then you remove the schemas.
Run the SQL query to verify if a prior Oracle Application Express installation exists.
To verify if a prior installation exists:
If the results contain entries in the form FLOWS_
XXXXXX
or APEX_
XXXXXX
where XXXXXX
represents six numbers, those entries are candidates for removal.
Start SQL*Plus and connect to database and execute a statement to remove schemas from prior installations.
To remove schemas from prior installations:
Use catcon.pl
to remove schemas of prior installations in a CDB.
To remove schemas from prior installations, run a command using the following example:
$ORACLE_HOME/perl/bin/perl -I $ORACLE_HOME/rdbms/admin $ORACLE_HOME/rdbms/admin/catcon.pl -b drop_apex050100 -- --x'drop user APEX_050100 cascade'
Learn how to fix an invalid ACL if you are running Oracle Database 11g or later.
After following the instructions in"About Removing Prior Oracle Application Express Installations," you may need to fix an invalid ACL if you are running Oracle Database 11g or later and you enabled network services for the prior Oracle Application Express schema.
To fix an invalid ACL: