Backward compatibility between OAS 2025 and OAS 2024 during staggered upgrades

Question

Hi all,

We’re planning a staggered upgrade from Oracle Analytics Server (OAS) 2024 to OAS 2025 across multiple environments (DEV → TEST → UAT → PROD). We’ll be upgrading one environment at a time, so there will be a period during which some environments run on 2024 and others on 2025.

Before we lock dates, I’d like to confirm compatibility and promotion paths during this mixed-version window.

If you have official docs/notes, compatibility matrices, or a MOS note that spells this out for OAS 2025 vs 2024, I’d really appreciate the references. Also, happy to hear real-world experiences from anyone who’s done a staggered 2024 → 2025 rollout.

Thank you

SteveF-Oracle · Accepted Answer

Hi Stephanie (@User_XF8Z3),

Welcome to the Oracle Analytics Community! We are glad you are here, and it is a good question.

Our documentation (or MOS notes) will provide guidance on how to upgrade (i.e. - steps), but not so much on the strategy.

I will definitely welcome community comments for that part. There is a lot of experience in this community.

What I will say, is that when developing your upgrade plan, is that you do not want to develop in a newer update environment (OAS 2025) and deploy elements in an lower update environment (OAS 2024).  This is especially true with Data Visualization Workbooks (i.e. export DVA) and snapshots.  You can get away with it on the Classic Dashboard/Analysis side with catalog archive/unarchive, but a best practice is to not move from newer to older instances.

It may be worth the extra resources to have a dual DEV2024/DEV2025 and TEST2024/TEST2025.

I will be interested to hear what the community shares with you here, in terms of their vast experiences.