3 Migrate Your Oracle Analytics Cloud - Classic Instances
When your target environment is ready, capture the information you want to migrate in a snapshot and copy it to Oracle Cloud Infrastructure.
Task | Description | More Information |
---|---|---|
Understand snapshot options | Understand what you can include or exclude when you take a snapshot. | |
Check your target is ready for migration and take a backup | Verify that the required users and roles are available in your target service and take a snapshot in case you need to roll back. | Back Up Your Target Service Before Migration |
Take a snapshot of the source |
Capture the content you want to migrate on the source system. |
|
Export the snapshot locally |
Download the snapshot that you want to migrate to your local file system. |
|
Edit database connections |
(Only if you migrated your data from Oracle Cloud Infrastructure Classic to Oracle Cloud Infrastructure) Extract the semantic model .rpd file from the snapshot (BAR), add the new connection string, and then upload the updated semantic model to the target system. |
Edit Connections and Upload Semantic Model |
Import the snapshot to the target |
Sign in to the target system and import the snapshot. |
|
Restore the snapshot content |
Select the newly imported snapshot in the list of saved snapshots and restore the content in the snapshot. |
|
Migrate data files |
(Only if the restore process fails due to connection issues) Use the Data Migration utility to migrate and restore data files from another environment. |
|
Reconfigure data replication connections |
(Only if you migrated replicated data from Oracle Cloud Infrastructure Classic to Oracle Cloud Infrastructure) Verify that the replicated tables and the required system tables exist on the new target database, and then edit the data replication connections to point to the new database. |
|
Reconfigure service settings | Verify various administrative settings on the target service. | |
Activate deliveries |
Disable deliveries on the source service and start delivering content from the target service. |
|
(Optional) Migrate other snapshots | Export individual snapshots that you want to migrate and then import them to your target environment, as required. |
Understand Snapshot Options
You can set various options when you take a snapshot of the Oracle Analytics Cloud environment you want to migrate.
Options When You Take a Snapshot
When you take a snapshot you choose the content you want to include in it. You can take a snapshot of your entire environment (everything) or specify only specific content that you want to back up or migrate (custom).
- Everything - Saves your entire
environment in the snapshot. This option is useful if you want to:
- Back up everything in case something goes wrong.
- Migrate everything to a new environment.
- Clone an existing environment.
- Custom - You select which content to save in the snapshot.
Some content types are always included while others are optional.
Snapshot Option Description Optional? Data Data visualization content that users create (Data tab). - Datasets
Datasets that users create for data visualizations and data flows. Always included - File-based Data
File-based data that users upload to create datasets. For example, data uploaded from a spreadsheet.
Optional - Connections
Data connections that users create so they can visualize their data. Always included - Data Flows
Data flows that users create for data visualization. Always included - Sequences
Sequences that users create for data visualization. Always included - Data Replications
Data replications that users create for data visualization. Optional Machine Learning Machine learning models that users create from data flows. Always included Jobs Jobs that users schedule for data flows, sequences, data replications, and pixel-perfect reports.
Optional Plug-ins and Extensions Extensions that users upload to implement custom visualizations and custom maps.
Optional Configuration and Settings Service configuration and settings configured through Console. For example, mail settings, database connections, safe domains, data connectivity configurations, and so on.
Note: System settings aren't included in the snapshot.
Optional Day by Day Day by Day content such as the "For You" feed, bring backs, comments, and shared cards.
Optional Application Roles - User-defined application roles that administrators create through Console.
- Membership details for each application role, that is, the users, groups, and other application roles assigned to each application role.
Always included Credentials - Data connections: Credentials and other connection parameters, such as host, port, user name, and password. If you exclude credentials, you must reconfigure the connection details after you restore the snapshot.
- Cloud storage: Credentials required to access cloud storage where file-based data that users upload is stored. If you include file-based data in your snapshot, include the storage credentials if you plan to migrate the content to another environment. If you exclude credentials, you can use the Data Migration utility to download and then upload your data files separately.
Optional Classic Content Content that users create using Classic tools in Oracle Analytics Cloud, such as analyses, dashboards, and pixel-perfect reports.
Always included - Semantic Model and Subject Areas
Semantic models and subject areas that users create. Always included - Catalog Content
Catalog containing content that users create and save for future use, such as analyses, dashboards, reports, deliveries, agents, and so on. Always included - Shared Folders (including Workbooks)
Content that is being shared, that is, content that everyone with access to Classic tools can see.
This includes any data visualization workbooks saved in the shared folders.
Always included - User Folders and Personalizations (including Workbooks)
Content stored in user folders. Content that users create and store for their private use.
This includes any data visualization workbooks that users save in their private folders and any personalizations that they make to these workbooks.
Optional
Options When You Restore a Snapshot
When you restore content from a snapshot you have several options. You can restore only the content that's inside the snapshot, restore everything in your environment, or restore a specific set of items in the snapshot (custom).
- Replace Snapshot Content Only - Everything in the snapshot that's supported in your environment is restored. Any content type excluded from the snapshot remains unchanged in your environment.
- Replace Everything - Replaces your entire environment using
information in the snapshot.
Any content type excluded from the snapshot is restored to its default state, that is, "no content". For example, if you chose not to include jobs in the snapshot, any jobs that exist on your system are deleted when you restore the snapshot and the jobs feature is restored with default settings. There are some exceptions; if the snapshot doesn’t contain any file-based datasets, plug-ins, or extensions these items are left unchanged.
This option is useful if you want to:
- Replace everything after something went wrong.
- Migrate from another service.
- Clone an existing service.
- Custom - You select the content you want to restore. If you
don’t want to restore certain content types, exclude them before you restore.
In most cases, the options on restore are the same as the options when you take a snapshot. Some content types are always restored, while others are optional.
Note:
When you restore catalog content from a snapshot, delivery schedules aren’t automatically restored or activated. This is so you can restore and activate deliveries at a time that suits you. See Restore and Enable Delivery Schedules.If your snapshot contains items that your environment doesn’t support, you see the message "Not supported in this environment".
Restoring a Snapshot Taken from a Different Product
You can take snapshots in several Oracle products; Oracle BI Enterprise Edition 12c, Oracle Analytics Cloud, and Oracle Analytics Server.
-
Unsupported Content
If you take a snapshot in one product and try to restore it in a different Oracle product, you might find the snapshot contains some items that the target environment doesn’t support. When Oracle Analytics detects unsupported content, warning icons display on the Custom page to highlight unsupported items in the snapshot that won't be restored.
For example, you take a snapshot in Oracle Analytics Cloud and include data replications, file-based datasets, plug-ins and extensions in the snapshot. When you restore the snapshot in Oracle Analytics Server, you notice that these items are marked not supported. Oracle Analytics Server doesn’t allow you to include data replications, file-based datasets, plug-ins and extensions in an Oracle Analytics Server snapshot or import them from snapshots you created in other products.
Back Up Your Target Service Before Migration
Verify that your target Oracle Analytics Cloud is ready for migration and then take a snapshot in case you need to roll back the service to its pre-migration state.
- Sign-in to the target Oracle Analytics Cloud.
- Verify that the users and roles you imported are available.
- Navigate to Console, and click Users and Roles.
- Click the Users tab and then the Roles tab to verify the users and roles.
- Take a backup of the target Oracle
Analytics Cloud.
- Navigate to Console, and click Snapshots.
- Click Create Snapshot.
- For description, enter "
Snapshot before content migration
" or something similar. - Select Everything, and then click Create.
Migrate Your Content
Capture the content you want to migrate in a snapshot and restore that snapshot on your target Oracle Analytics Cloud.
Edit Connections and Upload Semantic Model
Sometimes you must reconfigure the database connection information that's saved inside your source semantic model .rpd file before you migrate to the new Oracle Analytics Cloud on Oracle Cloud Infrastructure. For example, if you moved your data from Oracle Cloud Infrastructure Classic to Oracle Cloud Infrastructure, this is required because the connect string for the new database is different. If you do need to edit the source semantic model, you must upload the updated semantic model on the target before you migrate the rest of your content.
Note:
These instructions only apply if you currently use Model Administration Tool for Oracle Analytics Cloud to manage semantic models. If you use Data Modeler, you edit database connections through Console in your target environment.Migrate File-based Data
Users upload data files, such as spreadsheets, to Oracle Analytics Cloud to create datasets. When you migrate to a new Oracle Analytics Cloud environment, you can take this file-based data with you. Sometimes, network connectivity or storage access issues might prevent you from migrating the data files in the snapshot. For such cases, Oracle Analytics Cloud offers a CLI utility (command-line interface) that enables you to move your data files to the new location. The snapshot CLI utility also moves any map-related plug-ins and extension files that users might upload for their data visualizations.
Restore
succeeded with errors - data restore failed
(or similar) when you try to restore
a snapshot that contains data files. This message occurs when:
- You migrate content from a different region.
- You migrate content from Oracle Analytics Cloud on Gen 1 or Oracle Cloud Infrastructure Classic to Oracle Analytics Cloud on Gen 2.
- The restore process fails due to some other network connectivity or storage access issue.
The CLI utility allows you to move data files directly from one environment to another in a single step. Or if you prefer, you can download your file-based data to a ZIP file and then upload the data files to your chosen environment in two separate steps.
Move Replicated Data to a Different Target Database
For example, you might need to do this if your organization migrates from Oracle Cloud Infrastructure - Classic to Oracle Cloud Infrastructure.
You can now resume data replication in incremental mode into the new database.
Configure Service Settings
Many settings are migrated for you. Take some time to review various settings on the target Oracle Analytics Cloud and reconfigure if required.
Restore and Enable Delivery Schedules
When you restore content from a snapshot or migrate content from a different environment, delivery schedules defined for agents, analyses, and dashboards in the snapshot aren’t restored or activated right away. When you’re ready to restore deliveries on your system, you can decide whether to enable or disable delivery schedules on your system. This is useful as you might not want to immediately start delivering content.
For example, if you're restoring a production environment, you probably want to restart deliveries as soon as possible. Whereas in a test environment, you might prefer to disable deliveries after restoration and activate them at a later date.