After Upgrade to a New Version of APEX, the Old Version of APEX and It's Tablespace Can Be Dropped

(Doc ID 2341250.1)

Last updated on DECEMBER 26, 2017

Applies to:

Oracle Application Express (formerly HTML DB) - Version 5.1 and later
Information in this document applies to any platform.

Symptoms

APEX has been installed / and upgraded using the following syntax for each of the upgrades:

For APEX 4.2 Upgrade, @apexins.sql SYSAPEX SYSAPEX TEMP /i/
For APEX 5.0 Upgrade, @apexins.sql SYSAPEX5 SYSAPEX5 TEMP /i/
For APEX 5.1 Upgrade, @apexins.sql SYSAPEX51 SYSAPEX51 TEMP /i/


To clean up the installation we dropped the 4.2 / 4.2 tablespace.
drop tablespace sysapex including contents and datafile cascade;

 

However, after doing this numerous 5.1 database objects become invalid:

WWV_FLOW_SW_PARSER PACKAGE
WWV_FLOW_XLIFF PACKAGE BODY
WWV_FLOW_GENERATE_DDL PACKAGE BODY
WWV_FLOW_LOAD_DATA PACKAGE BODY
WWV_MIG_ACC_LOAD PACKAGE BODY
WWV_FLOW_CLOUD_ARCHIVE PACKAGE BODY
WWV_FLOW_WS_EXPORT PACKAGE BODY
WWV_FLOW_WS_ATTACHMENT PACKAGE BODY
WWV_FLOW_WORKSPACE_REPORTS PACKAGE BODY
WWV_FLOW_DATA_QUICK_FLOW PACKAGE BODY
WWV_FLOW_API PACKAGE BODY
WWV_FLOW_GEN_API2 PACKAGE BODY
WWV_FLOW_DML PACKAGE BODY
WWV_FLOW_UTILITIES PACKAGE BODY
WWV_FLOW_DATA_UPLOAD PACKAGE BODY
WWV_FLOW_PROCESS_NATIVE PACKAGE BODY
WWV_FLOW_MAINT PACKAGE BODY
WWV_FLOW_CACHE PACKAGE BODY
WWV_FLOW_TEAM_FILE PACKAGE BODY
WWV_FLOW_INSTALL_WIZARD PACKAGE BODY
WWV_FLOW_SW_UPGRADE PACKAGE BODY
WWV_FLOW_SW_PARSER PACKAGE BODY
WWV_FLOW_SW_SCRIPT PACKAGE BODY
WWV_FLOW_THEME_MANAGER PACKAGE BODY
WWV_FLOW_WEB_SERVICES PACKAGE BODY
WWV_FLOW_IMP_PARSER PACKAGE BODY
WWV_FLOW_FND_USER_INT PACKAGE BODY
WWV_FLOW_FILE_API PACKAGE BODY
WWV_FLOW_FILE_MGR PACKAGE BODY
WWV_FLOW_PKG_APP_PARSER PACKAGE BODY
WWV_FLOW_FILES_IOT TRIGGER
WWV_FLOW_TEMP_FILES_IOT TRIGGER
WWV_FLOW_SESSIONS_T2 TRIGGER
WWV_FLOW_TEMP_FILES VIEW
APEX_WORKSPACE_SQL_SCRIPTS VIEW
WWV_FLOW_FILES VIEW
APEX_WORKSPACES VIEW
APEX_WORKSPACE_FILES VIEW
WWV_FLOW_COMPANY_FILESTATS VIEW

What is causing these objects to become invalid?
How can the old 4.2 APEX objects be removed now that they are no longer needed?


Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms