Version 2025 I have recently completed a fresh installation of OAS 2025 in a test environment. Now, I'm considering the best approach to migrate this setup to higher environments (e.g., staging, production). I have a few questions regarding this process: * What is the recommended approach for migrating OAS 2025 to higher environments? * I initially planned to perform a fresh installation and configuration in each environment. Is this the best practice? * Are there alternative methods available, such as: a) A cloning process? b) Using VM snapshots? * Could you provide any official documentation or guidelines on this migration process? Thank you.

Oracle Communities

Oracle Analytics and AI

Child Item

Migration Process for OAS 2025

Version 2025

I have recently completed a fresh installation of OAS 2025 in a test environment. Now, I'm considering the best approach to migrate this setup to higher environments (e.g., staging, production). I have a few questions regarding this process:

What is the recommended approach for migrating OAS 2025 to higher environments?
I initially planned to perform a fresh installation and configuration in each environment. Is this the best practice?
Are there alternative methods available, such as: a) A cloning process? b) Using VM snapshots?
Could you provide any official documentation or guidelines on this migration process?

Thank you.

Find more posts tagged with

Accepted answers

Sumanth V -Oracle

@sgeorge_otn - Welcome to the Oracle Analytics Community!
Thanks for reaching out. Please find the answers to your queries below:

1. What is the recommended approach for migrating OAS 2025 to higher environments?
OAS 2025 is the latest available version as of now. The recommended approach for migrating between environments is by using snapshots. This method ensures consistency in moving content, configuration, and metadata across environments.
Refer to: Administering Oracle Analytics Server documentation for detailed steps.

2. I initially planned to perform a fresh installation and configuration in each environment. Is this the best practice?
Yes, if you are planning deployments across multiple environments (e.g., Dev, Test, Prod), it is recommended to install OAS afresh on each server. Once installed, you can use snapshots to migrate content and settings.

3. Are there alternative methods available, such as:
a) A cloning process?
b) Using VM snapshots?
Oracle does not document migrating entire OAS environments as these are customer specific.

4. Could you provide any official documentation or guidelines on this migration process?
Yes, please refer to the following official guide:
Migrating and Upgrading to Oracle Analytics Server

We hope this helps!
Please continue to use the Oracle Analytics Community for any further questions—we’re here to assist and support you.

All comments

Sumanth V -Oracle

@sgeorge_otn - Welcome to the Oracle Analytics Community!
Thanks for reaching out. Please find the answers to your queries below:

3. Are there alternative methods available, such as:
a) A cloning process?
b) Using VM snapshots?
Oracle does not document migrating entire OAS environments as these are customer specific.

4. Could you provide any official documentation or guidelines on this migration process?
Yes, please refer to the following official guide:
Migrating and Upgrading to Oracle Analytics Server

We hope this helps!
Please continue to use the Oracle Analytics Community for any further questions—we’re here to assist and support you.

Gianni Ceresa

Installations are independent and all require their unique components (like the RCU schemas being unique for each environment).

The good practise for setting up multiple environments (DEV, TEST, QA, PROD etc.) is by using response files and having a scripted installation. That way you are 100% sure that each environment is exactly configured like the others, and all have their own unique pieces.

Any cloning requires to change a number of pieces, starting from the RCU schemas in the database, the hostnames etc.

With response files and scripts for the install (could also be Ansible or other automation tools), you can install as many environments as needed, being sure they are all the same.

Steve F-2

Hi Sherry,

Some high-level information to get started.

The official documentation would have you migration your content (via snapshots) between environments initially, then there are other methods such as catalog archive/unarchive for "finer-grain" movements to update catalogs

About Snapshots

Now, how you decide to perform the installation/configuration in a higher environment would be up to your organization. Some perform complete manual (or automated - silent ) installations based off of "gold images". Others, use containerization/virtual machines (manually or automated).

Sherry J George

Thank you everyone for the answers. I will plan accordingly.