APEX 4.0 : APEX is Shown as INVALID in DBA_REGISTRY After Removing Development Environment. (Doc ID 1205613.1)

Last updated on OCTOBER 27, 2016

Applies to:

Oracle Application Express (formerly HTML DB) - Version 4.0 to 4.0.1 [Release 4]
Information in this document applies to any platform.
***Checked for relevance on 29-Apr-2015***

Symptoms

A full (Development and Runtime) APEX instance is converted to a runtime only instance by running the script apxdevrm.sql. Once this script has been run, APEX is shown as INVALID in DBA_REGISTRY. Furthermore, the log file created when running apxdevrm.sql contains the following error's:

...Database user "SYS", database schema "APEX_040000", user# "6612" 14:01:40
...FAILED CHECK FOR "PACKAGE BODY" "WWV_FLOW_PLUGIN_F4000" ORA-24344: success
with compilation error 14:01:41
...command: "alter package APEX_040000.WWV_FLOW_PLUGIN_F4000 compile body"
14:01:41
...DBMS registry set to invalid for APEX 14:01:41
...FAILED CHECK FOR "TRIGGER" "WWV_FLOW_FEEDBACK_T1" ORA-24344: success with
compilation error 14:01:42
...command: "alter trigger APEX_040000.WWV_FLOW_FEEDBACK_T1 compile" 14:01:42
...FAILED CHECK FOR "TRIGGER" "WWV_FLOW_FEEDBACK_T2" ORA-24344: success with
compilation error 14:01:42
...command: "alter trigger APEX_040000.WWV_FLOW_FEEDBACK_T2 compile" 14:01:42
...FAILED CHECK FOR "VIEW" "APEX_TEAM_FEATURES" ORA-24344: success with
compilation error 14:01:42
...command: "alter view APEX_040000.APEX_TEAM_FEATURES compile" 14:01:42
...Compiled 0 out of 1713 objects considered, 4 failed compilation 14:01:42


Changes

The script apxdevrm.sql was run to convert a full APEX instance to a runtime instance only.

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