Skip to Main Content
Forums

APEX

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

APEX5.1 and 18.1 Compatability

Patrick JolliffeJun 4 2018 — edited Jun 5 2018

Forgive the basic question, but if I've got one apex development environment, plus multiple run-time environments, all on 5.1, what options to I have for migrating to 18.1?

Can I upgrade all run-time environments to 18.1 first, and they can still deploy files exported generated from 5.1 development environment?

Or can I upgrade the development environment to 18.1 first and still import to 5.1 runtime environments?
Or will I have to do all together, ie upgrade the development environment and then have to upgrade each runtime before I can import updated applications?

Thanks in advance

Patrick
This post has been answered by Scott Wesley on Jun 4 2018
Jump to Answer

Comments

Mahmoud_Rabie

Hi Patrick

I recommend reading success stories for upgrading to 18.1

https://easyoradba.com/2018/05/28/upgrade-oracle-apex-from-5-1-x-to-18-1/

Dimitri Gielis Blog (Oracle Application Express - APEX): Safely Upgrading to Oracle APEX 18.1

I hope that helps.


Regards

Mahmoud

Patrick Jolliffe

Mahmoud,

Thanks for taking the time to respond to my question, and I've reviewed the links you have provided, but they seem to address only steps of how to upgrade a single instance from 5.1 to 18.1, but I don't have any problem with that, the documentation for the upgrade seems more than sufficient.

To repeat my question, can either first upgrade my development environments to 18.1 and still import my applications into 5.1 run-times?

Or can I upgrade my run-time environment to 18.1 and still import from 5.1 development environment?
Regards,

Patrick

Scott Wesley
Answer

APEX applications may not be exported from a higher version, then imported into a previous (eg, 18.x -> 5.x)

So you need to do your runtime environments first, once you're happy with the regression testing of the applications.

Marked as Answer by Patrick Jolliffe · Sep 27 2020
2 people found this helpful
Billy Verreynne

It is a catch 22. Which in our case means new temporary db server with new APEX version for testing applications (heavily customised and using ExtJS for example), prior to the upgrades of production runtime, and development.

It always have been an issue with only one APEX version that works in a database. Makes testing/porting/migrating apps to new APEX versions incredibly difficult.

Supporting multiple active APEX versions, in the same database, at the same time, is doable.

For ORDS (or mod_plsql) db connection schemas - use schema 1 that contains the scope for APEX version A (via synonyms), and use schema 2 for the scope for APEX version B (via public synonyms).

This simply requires no collisions in APEX objects between APEX versions A and B. WHICH IS A SOUND SOFTWARE ENGINEERING DECISION ANYWAY!!

I need more coffee....

Patrick Jolliffe

Perfect, just tested and can confirm I can import 5.1 developed application into 18.1 runtime.

For some reason I assumed it would be the other way round!

Can also confirm that 18.1->5.1 rollback/downgrade also works OK!

1 person found this helpful
1 - 5
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Jul 3 2018
Added on Jun 4 2018
#apex-discussions
5 comments
1,401 views