- 3,727,090 Users
- 2,245,319 Discussions
- 7,852,585 Comments
Forum Stats
Discussions
Howdy, Stranger!
Categories
- 380.8K All Categories
- 16 Data
- 362.2K Big Data Appliance
- 7 Data Science
- 2.3K Databases
- 670 General Database Discussions
- 3.7K Java and JavaScript in the Database
- 32 Multilingual Engine
- 499 MySQL Community Space
- 8 NoSQL Database
- 7.7K Oracle Database Express Edition (XE)
- 2.8K ORDS, SODA & JSON in the Database
- 424 SQLcl
- 68 SQL Developer Data Modeler
- 185.2K SQL & PL/SQL
- 21.1K SQL Developer
- 2.7K Development
- 3 Developer Projects
- 32 Programming Languages
- 135.9K Development Tools
- 18 DevOps
- 3K QA/Testing
- 381 Java
- 15 Java Learning Subscription
- 14 Database Connectivity
- 72 Java Community Process
- 2 Java 25
- 13 Java APIs
- 141.2K Java Development Tools
- 14 Java EE (Java Enterprise Edition)
- 153K Java Essentials
- 135 Java 8 Questions
- 86.2K Java Programming
- 270 Java Lambda MOOC
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 18 Java SE
- 13.8K Java Security
- 4 Java User Groups
- 22 JavaScript - Nashorn
- 18 Programs
- 156 LiveLabs
- 36 Workshops
- 11 Software
- 5 Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 4 Deutsche Oracle Community
- 17 Español
- 1.9K Japanese
- 4 Portuguese
Migration from Apex 19.2 to 20.2
Hello
I have developed an Apex Application with version 19.2
Now we would like to install Apex 20.2 on another DB and import/migrate the developed application in 19.2 Is it ok to simply export in 19.2 and import in 20.2 or are there other things to consider?
I'm sure there is documentation for such things, just couldn't find it in Internet.
Regards
Best Answer
-
Hello John,
There is not much else to do other than a usual export / import. Bring you db objects if there are not in the 20.2 instance. Unless you have server sides files like custom css or specific image folders on the ORDS server, you should be ready to go.
Good luck!
Answers
-
Hello John,
There is not much else to do other than a usual export / import. Bring you db objects if there are not in the 20.2 instance. Unless you have server sides files like custom css or specific image folders on the ORDS server, you should be ready to go.
Good luck!
-
Thank you for your answer, glad to hear it works that way! Luckily no external (custom) objects like CSS.
Regards
-
Now we would like to install Apex 20.2 on another DB and import/migrate the developed application in 19.2 Is it ok to simply export in 19.2 and import in 20.2 or are there other things to consider?
Always check the Release Notes for the target version (and any others that are being skipped) for deprecation/desupport notices, fixed/known bugs, and other changes in behaviour or functionality.
-
fac586 is right (as always!) You should always review the documentation when moving to a newer version.
-
Thank you all...
After checking https://docs.oracle.com/en/database/oracle/application-express/20.2/htmrn/index.html#HTMRN-GUID-216EF074-6E0C-4CCC-BC39-AFECE3674305 I had a shock what all was stopped, deprecated, desupported so we now stay on Apex 19.2
-
Could you tell this forum what is preventing you from moving forward to 20.2? This will help others with their evaluation.
-
IE 11 no longer supported (which I understand) but the company I'm working for has many business locations worldwide and some of them still use IE11.
Many pages use openmodal which is deprecated.
I did not check further after finding those two. Sure, sooner or later we probably must upgrade but then everything (every page) must be tested in detail.
-
These are interesting points that you are bringing up.
Even though Microsoft announced in August 2020 that they will not support IE11 anymore, many organizations (including yours) are not or have not put in place a project to move to Edge, or any other browser. For a browser released in 2013, that seems like pre industrial times in IT time! lol
So I guess it makes sense for Oracle to stop supporting IE11 if Microsoft doesn't support it anymore, and had stopped any development of IE over 4 years ago...
As for openModal specifically, it was actually announced as deprecated in APEX 19.2 and is now desupported in APEX 20.2. You can still use it in your 20.2 application, you won't be able to get support for it if something fails. That's where testing is quite important for such situations.
Thank you for providing these reasons for the rest of the community.
-
Thanks, I totally agree with you and all over de-support IE 11 makes totally sense, it's way overaged and I'm not up to finger-pointing! It lies in the nature of changes that this once was happening. I've developed the application in Chrome with Apex 19.2 what worked well.
The "IE11 problem" here is the current major issue why we decided to stop the migration to 20.2 (for now). As usual the business wants to see the app asap in PROD and as we have found out not all areas have Chrome or Edge in use. There were projects with switching to Chrome and Edge but it's not that easy in a company with several thousand employees worldwide divided in divisions and subdivisions, different IT infrastructures/departments. I would love to switch to 20.2 but as there is no time given (yet) we have to go the "safest" way and stay on 19.2
Open/CloseModal might have been fixed now as there is a provided solution. It just jumped into my eye overviewing the list.
-
Those challenges that you are describing are real and common in many organizations. Your decision to stay on APEX 19.2 make sense in the current situation but you will need to advocate for an extra effort from the organization in order to keep up (sic!) with technology!
Thanks again for sharing your experience with everyone in the community.
