Skip to Main Content

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.

Multi environment APEX upgrade Path / Process

Lukasz WasylowDec 20 2024

Good morning.

I was wondering how other deal with upgrading to a new versions before it get released to PROD.

We got currently DEV/TEST/UAT and finally PROD. The obvious issue is that once DEV is upgraded to newer version it will prevent any work done in that environment to deploy to older ones as you cannot export from newer to older version.

Without making an upgrade a separate project and creating a separate environment and use a specific resources just to test upgrade how you deal with this ?

One of the option considered is to first upgrade a TEST so that we verify the functionality is not broken there and in UAT business can verify as in PROD and then once we all happy do big DEV/TEST/PROD upgrade.

I really feel like there is a missing piece here for example export in compatibility or at least ability to use a older packages ( I still have not dropped old schema ) to export application using apex_export from previous schema ( wwv_flow package as this is just synonym).

Any input would be appreciated.

This post has been answered by danmcghan-Oracle on Dec 20 2024
Jump to Answer

Comments

Post Details

Added on Dec 20 2024
7 comments
266 views