Posted by As always, you should read the Installation/Upgrade manual from top to bottom before upgrading any piece of software, and be aware of all of the pre-requisites and processes. But for me, my Application Express 20.2 upgrade was as simple as:
- Download Application Express
- Unzip to my target location
- sqlplus / as sysdba
- SQL> @apexins.sql SYSAUX SYSAUX TEMP /i/
- Validate my ORDS installation
- java -jar ords.war validate
- sqlplus / as sysdba
- SQL> @apex_rest_config.sql
And voila! A freshly upgraded Application Express in a matter of minutes…
Sweet!
For this upgrade, I kept my 20.1 installation in place, so when I started my standalone ORDS server, I needed to update the location of the new 20.2 images by editing the standalone.properties file.
jetty.port=9111
standalone.context.path=/ords
standalone.doc.root=C\:\\oracle\\ordsconf\\ords\\standalone\\doc_root
standalone.scheme.do.not.prompt=true
standalone.static.context.path=/i
standalone.static.path=C\:\\oracle\\product\\apex.202\\apex\\images
I also made sure to check out the Known Issues information and downloaded patch 32006852 and applied it as per below.
SQL> conn /@db19_pdb1 as sysdba
Connected.
SQL> @catpatch.sql
. ORACLE
.
. Application Express (APEX) 20.2.0.00.20
. Patch Set Exception 32006852
........................................
APEX_VERSION
------------------------------
APEX_SCHEMA
-------------------------------------------------------------------------------------------------------------
-------------------
20.2.0.00.20
APEX_200200
PL/SQL procedure successfully completed.
Session altered.
APEX_SCHEMA
-------------------------------------------------------------------------------------------------------------
-------------------
APEX_200200
... Disabling Jobs
... disabling ORACLE_APEX_AUTOMATIONS
... disabling ORACLE_APEX_BACKUP
... disabling ORACLE_APEX_DAILY_MAINTENANCE
... disabling ORACLE_APEX_DICTIONARY_CACHE
... disabling ORACLE_APEX_ISSUE_EMAILS
... disabling ORACLE_APEX_MAIL_QUEUE
... disabling ORACLE_APEX_PURGE_SESSIONS
... disabling ORACLE_APEX_REST_SOURCE_SYNC
... disabling ORACLE_APEX_WS_NOTIFICATIONS
PL/SQL procedure successfully completed.
Session altered.
Grant succeeded.
...wwv_flow_db_env_detection.plb
Package body created.
No errors.
PL/SQL procedure successfully completed.
...wwv_flow_asn1.sql
Package created.
No errors.
...wwv_flow_public_key_util.sql
Package created.
No errors.
...wwv_flow_asn1.plb
Package body created.
No errors.
...wwv_flow_public_key_util.plb
Package body created.
No errors.
...devpatch.sql
Session altered.
Grant succeeded.
Session altered.
PL/SQL procedure successfully completed.
...patch_32001315.sql
1 row updated.
Commit complete.
PL/SQL procedure successfully completed.
Commit complete.
PL/SQL procedure successfully completed.
... Enabling Jobs
PL/SQL procedure successfully completed.
...Validating APEX
...(13:35:14) Starting validate_apex for APEX_200200
...(13:35:15) Checking missing sys privileges
...(13:35:15) Re-generating APEX_200200.wwv_flow_db_version
... wwv_flow_db_version is up to date
...(13:35:15) Recompiling APEX_200200 ... with dbms_utility.compile_schema
...(13:35:52) Checking for objects that are still invalid
...(13:35:52) Checking invalid public synonyms
...(13:35:52) alter public synonym "APEX_IR" compile
...(13:35:52) alter public synonym "APEX_PLUGIN_UTIL" compile
...(13:35:52) alter public synonym "WWV_FLOW_PLUGIN_UTIL" compile
...(13:35:52) Key object existence check
...(13:35:52) Setting DBMS Registry for APEX to valid
...(13:35:52) Exiting validate_apex
PL/SQL procedure successfully completed.
...Recompiling invalid public synonyms
PL/SQL procedure successfully completed.
PL/SQL procedure successfully completed.
timing for: Complete Patch 32006852
Elapsed: 00:00:40.86
Disconnected from Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.8.0.0.0
C:\oracle\product\apex.202\32006852>sql19
SQL*Plus: Release 19.0.0.0.0 - Production on Tue Oct 27 13:36:10 2020
Version 19.8.0.0.0
Copyright (c) 1982, 2020, Oracle. All rights reserved.
Last Successful login time: Tue Oct 27 2020 13:34:46 +08:00
Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.8.0.0.0
SQL> select patch_version, installed_on
2 from apex_patches
3 where patch_number = 32006852;
PATCH_VERSION INSTALLED_ON
------------------------------ -------------------
2020.10.23 2020-10-27 13:35:53
SQL>
And of course, don’t forget to update your images folder with the contents that patch as well.
Happy APEX-ing!
Learning is not a spectator sport 
Hi My configuration is
APEX 20.1
ORDS
TOMCAT
Do i need to perform any extra steps ?
Hi
We don’t use ORDS. I assume it will be ok to upgrade from Oracle apex 18.2 to 20.2
Nope…. see here https://blogs.oracle.com/apex/oracle-rest-data-services-the-only-supported-web-listener-for-oracle-apex