My Oracle Support Banner

Reverting to APEX 4.1 From APEX 4.2.5 Does Not Work - DBA_REGISTRY Still Shows 4.2.5 (Doc ID 1994168.1)

Last updated on FEBRUARY 18, 2021

Applies to:

Oracle Application Express (APEX) - Version 4.2.5.00.08 to 4.2.6 [Release 4]
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

After a failed installation, the APEX 4.2.5 installation was reverted back to the previous 4.1.0 version using the instructions in the APEX installation guide.

Though there are no errors presented, the following can be seen:

The problem is experienced in both Runtime Only and Development instances. It is not specific to a particular type of installation.

Steps to Reproduce:

1. Ensure that a 4.1.x version of APEX is installed in the database.

2. Upgrade to 4.2.5 according to the instructions in the installation guide.

3. Verify that 4.2.5 is up and running and the install is valid (no errors in the installation log).

4. Revert the installation to 4.1 according to the instructions in the 4.2.x installation guide:

    http://docs.oracle.com/cd/E37097_01/doc/install.42/e35123/trouble.htm#BABFEIGG.

5. Verify the version in the DBA_REGISTRY:

 
   Note the version still shows APEX 4.2.5
   Querying DBA_OBJECTS shows a number of invalid objects.

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
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.