2 Prepare to Migrate Oracle Analytics Cloud - Classic Instances

Before you migrate Oracle Analytics Cloud - Classic instances to Oracle Cloud Infrastructure plan and prepare for migration.

Task	Description	More Information
Plan your new service	Plan your Oracle Analytics Cloud deployment on Oracle Cloud Infrastructure. Think about what you want before you start.	Plan Your Service on Oracle Cloud Infrastructure
Complete your order and sign in to your Oracle Cloud account	You must have a subscription for Oracle Analytics Cloud (or Oracle Analytics Cloud Subscription) to create services on Oracle Cloud Infrastructure. As Cloud Account Administrator, you can complete all setup tasks.	Signing in for the First Time
Migrate users and groups	Migrate users and groups from Oracle Identity Cloud Service Migrate users and roles from embedded WebLogic LDAP	Migrate Users and Groups from Oracle Identity Cloud Service Migrate Users and Groups from Embedded WebLogic LDAP Server
Reconfigure single-sign on	(Optional) If SAML Single Sign-on (SSO) is configured in your source environment using samlssodocker, set up SSO in your target environment.	Oracle Cloud Infrastructure Identity and Access Management Identity Domains Federating with Identity Providers Oracle Identity Cloud Service Add an Identity Provider Integrating Oracle Identity Cloud Service with Microsoft Active Directory Federation Services
Integrate with external identity providers	(Optional) Integrate with external identity providers in your target environment. For example, Microsoft Active Directory and other identity providers that support the Security Assertion Markup Language (SAML) 2.0.	Oracle Cloud Infrastructure Identity and Access Management Identity Domains Federating with Identity Providers Setting Up a Microsoft Active Directory (AD) Bridge REST API for IAM Identity Domains Oracle Identity Cloud Service Manage Bridges for Oracle Identity Cloud Service Integrate Oracle Identity Manager with Oracle Identity Cloud Service REST API for Oracle Identity Cloud Service
Create a service on Oracle Cloud Infrastructure	Create an Oracle Analytics Cloud instance with the required size and shape on Oracle Cloud Infrastructure. If you subscribe through Universal Credits, create the service with Oracle Analytics Cloud on Oracle Cloud Infrastructure (Gen 2). If you have a non-metered subscription, create the service with Oracle Analytics Cloud Subscription.	Create a Service with Oracle Analytics Cloud Create a Service with Oracle Analytics Cloud Subscription
Verify your service	Verify that your service is up and running on Oracle Cloud Infrastructure and that you can sign in.	Verify Your Service and Sign In
Reconfigure connections to your data	Update connection information on the target Oracle Analytics Cloud instance. If your data is stored in a database on Oracle Cloud Infrastructure Classic you must move the data to Oracle Cloud Infrastructure.	Connect to Your Data
Add the IP address of your service to allowlists	If you registered the IP address of your Oracle Analytics Cloud - Classic instances in any data source allowlists, you must perform this task again for the new Oracle Analytics Cloud instance on Oracle Cloud Infrastructure.	Find the IP or Host Name of Your Oracle Analytics Cloud Instance

About Downtime Requirements

The migration process doesn't affect the availability of your existing Oracle Analytics Cloud - Classic instance on Oracle Cloud Infrastructure Classic. Users can continue to sign in and use the service.

Note:

If you do allow users to access and make changes after you've taken the final snapshot for migration, you might need to take another snapshot and repeat the migration if you want to include any changes that they make.

After a service instance is migrated successfully, you can reroute users to the new instance in Oracle Cloud Infrastructure.

Plan Your Service on Oracle Cloud Infrastructure

Take some time to plan your service on Oracle Cloud Infrastructure before you create it. Consider the size, shape, and location of your current deployment and decide what you want your Oracle Cloud Infrastructure to look like, before you start. If it helps, use a checklist similar to the one shown here.

• Planning checklist - an example

• Which type of subscription do you need?

• Which feature set do you need?

• What sizing options are available to you?

  • How many OCPUs do you think you’ll need?

  • How many people will use the service?

• Where do you want to deploy your service?

• What name do you want for your service?

Planning checklist - an example

Use a checklist similar to this one to help you decide.

Description of the illustration checklist.jpg

Which type of subscription do you need?

If you subscribe through Universal Credits, you create Oracle Analytics Cloud services on Oracle Cloud Infrastructure (Gen 2) . If you have a non-metered subscription, you use Oracle Analytics Cloud Subscription to create services on Oracle Cloud Infrastructure.

• Oracle Analytics Cloud (Universal Credits): Oracle Cloud Infrastructure (Gen 2)

• Oracle Analytics Cloud Subscription: Oracle Cloud Infrastructure (Gen 1)

Which feature set do you need?

Check which edition and feature set you used to create the service on Oracle Cloud Infrastructure Classic. In most cases, you use the same feature set to create your target deployment on Oracle Cloud Infrastructure.

Feature set options available on Oracle Cloud Infrastructure Classic:

• Data Visualization: Self-service data visualization, preparation and smart discovery (Professional Edition)
• Business Intelligence: Enterprise data modeling, reporting features, and data visualization (Enterprise Edition)
• Essbase: Collaborative data collection, scenarios and what-if analysis (Professional Edition or Essbase Edition)

Feature set options available on Oracle Cloud Infrastructure:

• Self-Service Analytics: Suitable if you want to offer only data visualization and migrate only data visualization artifacts (Professional Edition).
• Enterprise Analytics: Suitable if you want to offer data visualization, plus enterprise modeling and reporting features. Required if you want to migrate analyses, dashboards, pixel-perfect reports, and data visualizations (Enterprise Edition).
• Essbase Edition: Required if you want to migrate an Essbase instance. *This guide doesn’t describe how to migrate Oracle Analytics Cloud - Classic services deployed with Essbase.

Use this table to determine which feature set you need to migrate Oracle Analytics Cloud - Classic services deployed with data visualization and business intelligence:

Oracle Analytics Cloud - Classic		Oracle Analytics Cloud	Oracle Analytics Cloud Subscription
Edition	Feature Set	Feature Set	Edition Required
Professional Edition	Data Visualization	Self-Service Analytics	Professional Edition
Enterprise Edition	Data Visualization	Self-Service Analytics	Professional Edition
	Business Intelligence	Enterprise Analytics	Enterprise Edition

What sizing options are available to you?

When you create an Oracle Analytics Cloud service, you either specify the number of Oracle Compute Units (OCPUs) you want to deploy or the number of people you expect to use the service.

Size Options	Oracle Analytics Cloud (Universal Credits)	Oracle Analytics Cloud Subscription
Number of OCPUs	Yes	Yes
Number of Users	Yes	Yes

How many OCPUs do you think you’ll need?

Verify the current compute shape of your service on Oracle Cloud Infrastructure Classic. Consider whether or not the size of your current deployment meets your current requirements. For example, if your compute shape on Oracle Cloud Infrastructure Classic is OC6 (8 OCPUs and 60 GB memory) you might want your deployment on Oracle Cloud Infrastructure to have a similar number of OCPUs, more OCPUs, or less OCPUs. The decision is yours.

Oracle Cloud Infrastructure offers a range of compute sizes (OCPUs) to suit different scenarios. The larger the compute size, the greater the processing power. For more guidance, read the topic: How many OCPUs do you think you’ll need?

How many users will use the service?

Alternatively, you can specify how many people you expect to use the service. Verify how many people are using your service on Oracle Cloud Infrastructure Classic and consider whether or not this number of users is likely to increase.

For more guidance, read the Oracle Analytics Cloud on Oracle Cloud Infrastructure topic: How many people do you expect to use the service?

Where do you want to deploy your service?

Verify the region where you deployed your current service on Oracle Cloud Infrastructure Classic.

Oracle Cloud Infrastructure is hosted in similar geographic areas, also called regions. If multiple regions are available to you, decide where you want to deploy your service. For example, Phoenix, Ashburn, Frankfurt, London. To find out which regions are available, see www.oracle.com/cloud/data-regions.html.

What name do you want for your service?

Think about a suitable name for your service. The name that you specify is displayed in Oracle Cloud Infrastructure Console and in the URL for your service. If you want, you can use the same name as your current service on Oracle Cloud Infrastructure Classic.

Name restrictions on Oracle Cloud Infrastructure:

• Must contain between 1 and 25 characters.

• Must start with an ASCII letter: a to z or A to Z.

• Must contain only ASCII letters or numbers.

• Mustn't contain any other special characters.

• Must be unique within the identity domain.

Migrate Users and Roles from Oracle Analytics Cloud - Classic

Before you migrate to Oracle Cloud Infrastructure, you must migrate your users and groups from Oracle Cloud Infrastructure Classic. The way you migrate depends on whether you're using Oracle Identity Cloud Service or an embedded WebLogic LDAP server. If you subscribe to Oracle Analytics Cloud - Classic through Universal Credits, you manage users in Oracle Identity Cloud Service. If you subscribe to Oracle Analytics Cloud - Classic through a traditional metered or unmetered subscription, you might be using an embedded WebLogic LDAP server.

Topics

• Migrate Users and Groups from Oracle Identity Cloud Service

• Migrate Users and Groups from Embedded WebLogic LDAP Server

Migrate Users and Groups from Oracle Identity Cloud Service

Use export and import features in your identity management system to migrate users and groups from an identity domain on Oracle Cloud Infrastructure Classic to another identity domain on Oracle Cloud Infrastructure.

The way you migrate users and groups depends whether your target environment offers Oracle Cloud Infrastructure Identity and Access Management (IAM) identity domains or Oracle Identity Cloud Service (IDCS).

• Oracle Cloud Infrastructure Identity and Access Management (IAM) Identity Domains

  • To migrate users, see Export Users from IDCS in Administering Oracle Identity Cloud Service and Import Users to IAM Identity Domains in Oracle Cloud Infrastructure documentation.

  • To migrate user groups, see Export Groups from IDCS in Administering Oracle Identity Cloud Service and Import Groups to IAM Identity Domains in Oracle Cloud Infrastructure documentation.

• Oracle Identity Cloud Service

  • To migrate users, see Export Users from IDCS and Import Users to IDCS in Administering Oracle Identity Cloud Service.

  • To migrate user groups, see Export Groups from IDCS and Import Groups to IDCS in Administering Oracle Identity Cloud Service.

Migrate Users and Groups from Embedded WebLogic LDAP Server

If you subscribe to Oracle Analytics Cloud - Classic through a traditional metered or unmetered subscription you might be using an embedded WebLogic LDAP server for identity management. The way you migrate users and groups to Oracle Analytics Cloud on Oracle Cloud Infrastructure (Gen 2) depends whether your target environment offers Oracle Cloud Infrastructure Identity and Access Management (IAM) identity domains or Oracle Identity Cloud Service (IDCS).

If your service uses an embedded WebLogic LDAP server, use the wls_ldap_csv_exporter script to export users and groups to CSV files so you can migrate to Oracle Cloud Infrastructure (Gen 2). Prepare both CSV files so they contain all the information required and then import them on the target environment.

1. Export users and groups from your source environment. Run the wls_ldap_csv_exporter script:

   $ /bi/app/public/bin/wls_ldap_csv_exporter -u weblogic_admin_user -c oracle_common_folder_path -D output_dir

   Typically, oracle_common_folder_path is the folder /bi/app/fmw/oracle_common

   This script creates two CSV files, one CSV file contains users and the other contains groups. There is also a log file, which describes any invalid or incompatible records that your target environment won’t understand.

   • Every user must have a default password.

   • IAM identity domains and IDCS don't support group memberships; that is, where a group is a member of another group. Such records are discarded from the group CSV file and mentioned in the log file.

   • IAM identity domains and IDCS both require several mandatory parameters for users: User ID,Last Name,First Name,Password,Work Email. User records that don't include all the required parameters aren't imported.

   Before you import CSV files on your target environment, take some time to make sure the CSV files contain all the required information.

2. Prepare both CSV files for migration.
   1. Review the log file for information about invalid or incomplete records.
   2. Review the users CSV file, and ensure the information is complete.
   3. Repeat for the groups CSV file.
3. Import users from the CSV file you exported earlier:

   • Oracle Cloud Infrastructure Identity and Access Management (IAM) Identity Domains

     See Import Users to IAM Identity Domains in Oracle Cloud Infrastructure documentation.

   • Oracle Identity Cloud Service

     See Import User Accounts to IDCS in Administering Oracle Identity Cloud Service.

4. Import groups from the CSV file you exported earlier.

   • Oracle Cloud Infrastructure Identity and Access Management (IAM) Identity Domains

     See Import User Groups to IAM Identity Domains in Oracle Cloud Infrastructure documentation.

   • Oracle Identity Cloud Service

     See Import User Groups in Administering Oracle Identity Cloud Service.

Create Your Service on Oracle Cloud Infrastructure

As Cloud Account Administrator, you can create services on Oracle Cloud Infrastructure. If you subscribe through Universal Credits, create the service with Oracle Analytics Cloud. If you have a non-metered subscription, create the service with Oracle Analytics Cloud Subscription.

Topics

• Create a Service with Oracle Analytics Cloud

  Oracle recommends that you deploy new services on Oracle Cloud Infrastructure Gen 2. If you don't have access yet, see When and how do I access the new administration console for Oracle Cloud Infrastructure (Gen 2)?

• Create a Service with Oracle Analytics Cloud Subscription

Create a Service using the Console

You can use Oracle Cloud Infrastructure Console to set up a service instance with Oracle Analytics Cloud.

You must belong to an OCI group that is granted the required policies to create an Analytics instance. See Give Users Permissions to Manage Analytics Cloud Instances.

1. Sign in to your Oracle Cloud account.

   The way you sign in depends whether your cloud account uses identity domains or federates with Oracle Identity Cloud Service. See Signing In to the Oracle Cloud Infrastructure Console.

2. In Console, click in the top left corner.
3. Click Analytics & AI. Under Analytics, click Analytics Cloud.
   
   Description of the illustration console_oac_nav.jpg
4. From the Compartment list, select the compartment in which you want to create the service.
5. Click Create Instance.
   
   Description of the illustration console_oac.jpg
6. Enter a Name and a brief description.
   The name must start with a letter and can contain only letters and numbers.
7. For Capacity, select the size of your deployment.

   Configure the capacity type that matches your subscription, that is, either OCPUs per hour or Users per month.

   • OCPU: Select the number of OCPUs you want to deploy.

     • Production environment: Select between 2 and 52 OCPUs.

     • Non-production environment: Select 1 OCPU if you want to create an instance for test purposes.

     See What's the Difference Between Production and Non-Production Environments.

     You must select the OCPU option if you plan to use your Oracle Middleware on-premise license with Oracle Analytics Cloud (BYOL).

   • Users: Enter the number of users you expect to use this service.

     You can split your capacity over multiple services. For example, if your subscribe to 100 users per month, you might deploy a test instance for 10 users and a production instance with the remaining 90 users.

8. For License, select License Included to subscribe to an Oracle Cloud license for Oracle Analytics Cloud or Bring Your Own License (BYOL) to use your Oracle Middleware on-premise license with Oracle Analytics Cloud and be charged the Bring Your Own License (BYOL) rate.

   The Bring Your Own License (BYOL) option is available when you select OCPU for Capacity.

   If you select Users, you must have an Oracle Cloud license for Oracle Analytics Cloud.

9. Select the Edition that matches your subscription.
   • Enterprise Edition: Deploys an instance with enterprise modeling, reporting, and data visualization.
   • Professional Edition: Deploys an instance with data visualization.

   For example:

   
   Description of the illustration console_oac_create.jpg
10. Optional: Click Show Advanced Options to configure network or encryption options.
    
    Description of the illustration console_oac_create2.jpg
11. In Network Access, configure how you want users to access Oracle Analytics Cloud: over the public internet or through a private network.

    • Public: Enable access over the public internet.

      The Public option deploys Oracle Analytics Cloud with a public internet accessible endpoint. If required, you can configure access control rules to restrict access by public IP address, public CIDR block range, VCN, and Oracle services. See Restrict Access to Oracle Analytics Cloud Deployed with a Public Endpoint.

    • Private: Enable private access from an on-premise network or hosts on a virtual cloud network (VCN). Private access means that traffic doesn't go over the internet.

      The Private option deploys Oracle Analytics Cloud with a private endpoint. Before you configure this option, you must set up the Oracle Cloud Infrastructure VCN that you plan to use with a subnet for Oracle Analytics Cloud. If required, you can restrict access to private endpoints through network security groups. If your network security groups aren't set up yet, you can save this task for later. See Deploy Oracle Analytics Cloud with a Private Endpoint.

    You can configure access control rules for a public endpoint or change the VCN, subnet, and network security group access for a private endpoint, later on as required. However, you can't change your network access selection from public to private (or private to public).

12. Optional: In Data Encryption, customize how Oracle Analytics Cloud encrypts customer data.

    • Encrypt using Oracle-managed Keys: Leave all data encryption to Oracle.

    • Encrypt using Customer-managed Keys: Specify the custom encryption key you want to use.

    You can configure data encryption now or later. If you haven’t created a master encryption key yet, leave this task for later. See Encrypt Sensitive Information.

    Your Oracle Analytics Cloud instance must be deployed with Enterprise Edition. Custom encryption isn't available on Oracle Analytics Cloud instances deployed with Professional Edition.

13. Verify that the details are correct, and click Create.

It takes about 20 minutes to create the service. Display the Instance page to check the current status.

Description of the illustration console_oac_create3.jpg

Create a Service with Oracle Analytics Cloud Subscription

You use Oracle Cloud Infrastructure Console to set up a service with Oracle Analytics Cloud Subscription. Follow these steps if you have a non-metered subscription.

1. Sign in to Oracle Cloud as the Cloud Account Administrator.
   If you're signing in for the first time, you can find your account name and login information in your welcome email.
2. In Oracle Cloud Infrastructure Console, click in the top right corner.
3. Click Service User Console, and then click Oracle Analytics Cloud Subscription.
   If you don't immediately see Oracle Analytics Cloud Subscription, enter Analytics Cloud Subscription in the search box.
4. Click Create Instance.
   
   Description of the illustration oaac_create_sub.jpg
5. For Instance Name, enter a name for your service instance.
   The name must start with a letter and can contain only letters and numbers.
6. For Notification Email, enter the email address of the person you want to notify when this service is ready to use and receive other status updates about this service in the future.
   This person is usually you, the Cloud Account Administrator who’s setting up the service.
7. If multiple identity domains are available to you, select the Identity Domain that you want this service to use and then enter the name of an existing user in this identity domain that you want to assign as the Service Administrator.
   You don't see these options if only one identity domain is available.
8. If several geographical regions are available to you, select the Region where you want to deploy Oracle Analytics Cloud. For example, uk-london–1.
9. If several edition options are available to you, select the Edition that matches the type of service you want to create.

   • Professional

   • Essbase *

   • Enterprise

   * Oracle Analytics Cloud -Essbase Edition isn't available in Oracle Cloud accounts created after 12th December 2019.

10. Determine the size of your service.
    • To size your service based on how many users you're entitled to as part of your subscription, set Subscription Type to Number of Users, and then enter the number of users (between 10 and 3000).
    • To size your service based on how many Oracle Compute Units (OCPUs) you're entitled to as part of your subscription, set Subscription Type to Number of OCPUs, and then select the number of OCPUs you want.
11. Click Next.
12. Verify that the details are correct, and click Create.

It takes about 20 minutes to create the service. Oracle sends an email to the designated email address when your service is ready. Display the Activity page to check the current status.

Description of the illustration activity-page_sub.jpg

Verify Your Service and Sign In

Oracle sends an email to the designated email address when your Oracle Analytics Cloud service is ready. Navigate to your service in Oracle Cloud Infrastructure Console, obtain the service URL, and then sign in to verify your Oracle Analytics Cloud service is up and running.

1. Sign in to your Oracle Cloud account.
2. In Oracle Cloud Infrastructure Console, click in the top left corner.
3. Do one of the following:

   • Oracle Analytics Cloud (Universal Credits) - Click Analytics & AI. Under Analytics, click Analytics Cloud.

     Select the compartment in which you created the service, the name of the new service, and then click Analytics Home Page. See Verify Your Service.

   • Oracle Analytics Cloud Subscription - Click in the top right corner, click Service User Console, and then click Oracle Analytics Cloud Subscription

     Click Manage this instance for your service, and then click Oracle Analytics Cloud URL. See Verify Your Service.

4. Sign in with your administrator credentials.

Connect to Your Data

The way you connect your Oracle Analytics Cloud deployment on Oracle Cloud Infrastructure to your data is similar to your existing service on Oracle Cloud Infrastructure Classic. The steps you need to follow depend where your data is stored.

If you're currently using Oracle Analytics Cloud - Classic to analyze data in an Oracle Database on Oracle Cloud Infrastructure Classic, you must first move your data to Oracle Cloud Infrastructure before you migrate your Oracle Analytics Cloud - Classic instance.

Where is Your Data Stored?	Description	More Information
On-premises database	You can keep your data in on-premises databases such as Oracle Database, Oracle Essbase, MS SQL Server, Teradata, and IBM DB2. Use Data Gateway to access your on-premises data from the new Oracle Analytics Cloud instance on Oracle Cloud Infrastructure. If your remote on-premises data source is Oracle Essbase, you must continue to use the legacy Remote Data Connector.	Connect to Data on On-premises Databases
Oracle Database on Oracle Cloud Infrastructure Classic	First, migrate your data to a database on Oracle Cloud Infrastructure. Reconfigure the database connection to point to the new database before you migrate your Oracle Analytics Cloud Classic instance. There are two ways to do this: Use the Database Connection dialog in the source Oracle Analytics Cloud Classic instance before you take the final snapshot. Use this method if you use Data Modeler. Use the Model Administration Tool for Oracle Analytics Cloud to edit the connection information before you migrate the final snapshot. Use this method if you use Oracle Analytics Client Tools to manage your semantic models.	Move Data from Oracle Cloud Infrastructure - Classic
Oracle Database on Oracle Cloud Infrastructure	You can keep your data in the same database. You must reconfigure the database connection on the new Oracle Analytics Cloud instance on Oracle Cloud Infrastructure.	Connect to Data on Oracle Cloud Infrastructure
Other cloud databases	You can keep your data in the same database. You must reconfigure the database connection on the new Oracle Analytics Cloud instance on Oracle Cloud Infrastructure.	Connect to Data on Other Cloud Databases

Connect to Data on On-premises Databases

You can keep data in your on-premises database. If you haven’t done so already you need to install Data Gateway on the network where you host the data and set up a connection to the target Oracle Analytics Cloud instance on Oracle Cloud Infrastructure.

Note:

If your remote on-premises data source is Oracle Essbase, you must continue to use Remote Data Connector.

1. Set up Data Gateway.
   1. Install and set up Data Gateway.
      See Set up Data Gateway.
   2. Configure and register Data Gateway.
      See Configure and Register Data Gateway.

   You don't need to reconfigure your semantic model (.rpd).

2. (On-premises Oracle Essbase only) Set up Remote Data Connector.
   See Install the Legacy Remote Data Connector.
3. Connect to the on-premises database from Oracle Analytics Cloud.
   See Connect to an On-premises Database from Oracle Analytics Cloud.
4. If required, add the IP address range or Gateway IPs associated with your target Oracle Analytics Cloud to the allowlist for your on-premises database (on your firewall).

   • Oracle Analytics Cloud (Universal Credits): See Find the IP or Host Name of Your Oracle Analytics Cloud Instance on Oracle Cloud Infrastructure (Gen 2)

   • Oracle Analytics Cloud Subscription: See IP Ranges and Gateway IPs for Oracle Analytics Cloud

Connect to Data on Oracle Cloud Infrastructure

If your new Oracle Analytics Cloud instance on Oracle Cloud Infrastructure connects to a database on Oracle Cloud Infrastructure, you must add the IP address of the new Oracle Analytics Cloud instance to the database's allowlist.

1. Determine the IP address of the target Oracle Analytics Cloud instance.

   • Oracle Analytics Cloud (Universal Credits): See Find the IP or Host Name of Your Oracle Analytics Cloud Instance on Oracle Cloud Infrastructure (Gen 2)

   • Oracle Analytics Cloud Subscription: See IP Ranges and Gateway IPs for Oracle Analytics Cloud
2. Add the IP address range or Gateway IPs associated with your target Oracle Analytics Cloud to the allowlist for your database on Oracle Cloud Infrastructure.
   If the database instance is on private IP network, you must install and configure Data Gateway on the compute instance to enable the connection. See Set up Data Gateway.

Connect to Data on Other Cloud Databases

If your new Oracle Analytics Cloud instance on Oracle Cloud Infrastructure must connect to other cloud data sources (non-Oracle), you might need to add the IP address of the new Oracle Analytics Cloud instance to the allowlists for these data sources.

1. Determine the IP address of the target Oracle Analytics Cloud instance.

   • Oracle Analytics Cloud (Universal Credits): See Find the IP or Host Name of Your Oracle Analytics Cloud Instance on Oracle Cloud Infrastructure (Gen 2)

   • Oracle Analytics Cloud Subscription: See IP Ranges and Gateway IPs for Oracle Analytics Cloud
2. If required, add the IP range or Gateway IPs associated with your target Oracle Analytics Cloud to the allowlist for your cloud data sources.

Move Data from Oracle Cloud Infrastructure - Classic

First, move any data stored on Oracle Cloud Infrastructure Classic to a database on Oracle Cloud Infrastructure. Reconfigure the database connection to point to the new database before you migrate your Oracle Analytics Cloud Classic instance.

1. Create a new database instance on Oracle Cloud Infrastructure and migrate your data.
   See Migrate Databases Using the Migration Tools.
2. Determine the connection string for the new database, and then do one of the following:

   • In the source Oracle Analytics Cloud Classic instance, edit the connection using the Database Connection dialog before you take a final snapshot of your system.

     Always use this method if you use Data Modeler in Oracle Analytics Cloud Classic and want to continue to use Data Modeler after you migrate to Oracle Cloud Infrastructure. See Connect to Data in an Oracle Cloud Database.

   • Use the latest Model Administration Tool for Oracle Analytics Cloud to reconfigure the database connection in the source semantic model. You can extract the semantic model from the final snapshot you plan to migrate. See Edit Connections and Upload Semantic Model.

     Use this method if you use Oracle Analytics Client Tools to manage semantic models in Oracle Analytics Cloud Classic.

3. If required, add the IP range or Gateway IPs associated with your target Oracle Analytics Cloud to the allowlist for the new database on Oracle Cloud Infrastructure.

   • Oracle Analytics Cloud (Universal Credits): See Find the IP or Host Name of Your Oracle Analytics Cloud Instance on Oracle Cloud Infrastructure (Gen 2)

   • Oracle Analytics Cloud Subscription: See IP Ranges and Gateway IPs for Oracle Analytics Cloud

Add IP Address Details for Oracle Analytics Cloud to Allowlists

If you added the IP or endpoint of your Oracle Analytics Cloud - Classic instance on Oracle Cloud Infrastructure Classic to one or more allowlists, you must perform this task again for the Oracle Analytics Cloud instance on Oracle Cloud Infrastructure.

1. Determine IP address information for Oracle Analytics Cloud.

   • Oracle Analytics Cloud (Universal Credits): See Find the IP or Host Name of Your Oracle Analytics Cloud Instance on Oracle Cloud Infrastructure (Gen 2)

   • Oracle Analytics Cloud Subscription: See IP Ranges and Gateway IPs for Oracle Analytics Cloud
2. Add the IP range or Gateway IPs associated with Oracle Analytics Cloud to the allowlist for your data sources, as required.