APEX 3.0.1 to 3.2.0 : APEX Is Shown As INVALID In DBA_REGISTRY After Removing Development Environment (Doc ID 1055160.1)

Last updated on OCTOBER 27, 2016

Applies to:

Oracle Application Express (formerly HTML DB) - Version 3.0.1 to 3.2.0
Information in this document applies to any platform.
***Checked for relevance on 01-Oct-2012***

Symptoms

This article is specific to APEX Version 3.0.1 to 3.2.0. For APEX Version 4.0.x, please see <NOTE 1205613.1>

 

 


In Oracle Application Express 3.x, if you have a full development version (the default) and you choose to remove the development environment and convert it to a runtime installation only, which is recommended for production installations, then:

  1. The APEX component will be listed as INVALID in DBA_REGISTRY
  2. Errors are not reported during execution of the APEX development removal installation script, apxdevrm.sql, leading you to believe that no errors occurred.

APEX applications will continue to run in this environment, even with the APEX component being marked as INVALID in DBA_REGISTRY. While this does not directly impact the execution of applications, it can impact future upgrade actions.

Changes

Moved from development environment to runtime only by running the script apxdevrm.sql.

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