1. Migrate an on-premises database to the cloud with zero downtime
  2. Prepare Services in the Cloud to Accept Migrated Data

Prepare Services in the Cloud to Accept Migrated Data

Prepare your Oracle Cloud Infrastructure account to accept migrated data by creating a storage bucket to store the data and provisioning a compatible database in your region. The database version must be the same as the source database version and the patch version should be the same (or higher) than the source database.

Create a Bucket in Object Storage

Buckets are used to store and organize data. The bucket that you create will be the container for the data that's backed up to Oracle Cloud Infrastructure Object Storage.

  1. In the Oracle Cloud Infrastructure Console, under Core Infrastructure, click Object Storage.
  2. Select the compartment from the Compartments list on the left side of the page.
    The compartment is where you deployed the resources.
  3. Click Create Bucket.
  4. Name the bucket.
    The system generates a default bucket name that reflects the current year, month, day, and time, for example bucket-20210210-1359. When changing the default to any other bucket name, use letters, numbers, dashes, underscores, and periods. Avoid entering confidential information. For example, name the bucket atp-upload.
  5. Use the default values for the bucket attributes.
    For example, select the Standard Storage Tier. Standard is the primary, default storage tier used for storing data that requires fast and immediate access.
  6. Click Create Bucket.

Deploy a Oracle Base Database Service Topology

The Terraform code to deploy the target cloud topology is available in Oracle Cloud Infrastructure Resource Manager or GitHub. You can use the code to provision the required networking resources, a compute instance for the bastion server, and Oracle Base Database Service.

  • Deploy the cloud resources by using Oracle Cloud Infrastructure Resource Manager:
    1. Click Deploy to Oracle Cloud
      If you aren't already signed in, enter the tenancy and user credentials.
    2. Review and accept the terms and conditions.
    3. Select the region where you want to deploy the stack.
    4. Follow the on-screen prompts and instructions to create the stack.
    5. After creating the stack, click Terraform Actions, and select Plan.
    6. Wait for the job to be completed, and review the plan.
      To make any changes, return to the Stack Details page, click Edit Stack, and make the required changes. Then, run the Plan action again.
    7. If no further changes are necessary, return to the Stack Details page, click Terraform Actions, and select Apply.
  • Deploy the cloud resources by using the Terraform CLI:
    1. Go to GitHub.
    2. Download the code to your local computer.
    3. Complete the prerequisite steps in the README.
    4. Apply the configuration using the Terraform CLI.

Provision a Database in Oracle Cloud Infrastructure

Provision a compatible database in Oracle Cloud Infrastructure. The database can be either a bare metal or virtual machine, but the version must be at least the same version as the source database.

The target database version must be the same or higher than the source database version. The target database can be a higher patch level. If it's a higher version, then an upgrade is required before migrating.

The container database (CDB) or system identifier (SID) name in the cloud must be the same as the source database CDB or SID name. Depending on the type of database system and the number of nodes provisioned, it can take over an hour to provision a database system.

Before you begin, the compartment must have a Virtual Cloud Network (VCN) setup with a private subnet to provision the Oracle Base Database Service. To access the database, you must either provision a bastion host in a public subnet in the VCN (so that it has a public IP), or you'll need direct access to the private network through VPN or Oracle Cloud Infrastructure FastConnect. Create a Security List rule on the database private subnet giving access to the database port (1521) from the public subnet CIDR block.

  1. Open the navigation menu in the OCI Console.
  2. Select Oracle Database, then select Oracle Base Database.
  3. Click Create DB system.
  4. Select the Compartment where the database system will reside.
  5. Name your DB system.
  6. Select an availability domain.
  7. Configure the shape that matches your database requirements.

    The shape determines the type of DB system created and the resources allocated to the system. By default, AMD VM.Standard.E4.Flex shape with 4 OCPUs is selected.

    To specify a shape other than the default, click Change shape, and select an available shape from the list.

  8. Select Ampere, AMD, or Intel processor in the processor group

    Note:

    If you select an Ampere A1, AMD E4, or Intel X9 flexible shape, the memory, network bandwidth, and maximum theoretical IOPS scale proportionally.

  9. Configure OCPU: Select the number of OCPUs you want to allocate to this instance.
    For Ampere A1, AMD E4, and Intel X9 flexible shapes, you can select the number of OCPUs by using the slider in the Number of OCPUs per node field.
    • For Ampere A1 shape, a minimum of 1 OCPU and a maximum of 57 OCPUs can be selected.
    • For AMD E4 shape, a minimum of 1 OCPU and a maximum of 64 OCPUs can be selected.
    • For Intel X9 shape, a minimum of 1 OCPU and a maximum of 32 OCPUs can be selected.

    The following resources scale proportionately to the number of OCPUs you selected.

    • Memory (GB): The amount of memory you want to allocate to this instance.

      For Ampere A1, AMD E4, and Intel X9 shapes, the memory will scale proportionally based on the number of OCPUs selected.

      • For Ampere A1 shape, for each OCPU, 8 GB of memory is allocated. A minimum of 8 GB and a maximum of 456 GB of memory is allocated.
      • For AMD E4 shape, for each OCPU, 16 GB of memory is allocated. A minimum of 16 GB and a maximum of 1024 GB of memory is allocated.
      • For Intel X9 shape, for each OCPU, 16 GB of memory is allocated. A minimum of 16 GB and a maximum of 512 GB of memory is allocated.
    • Network bandwidth (Gbps): The amount of network bandwidth you want to allocate to this instance.

      For Ampere A1, AMD E4, and Intel X9 shapes, the bandwidth will scale proportionally based on the number of OCPUs selected. For each OCPU, 1 Gbps of network bandwidth is allocated.

      • For Ampere A1 shape, a minimum of 1 Gbps and a maximum of 40 Gbps of network bandwidth is allocated.
      • For AMD E4 shape, a minimum of 1 Gbps and a maximum of 40 Gbps of network bandwidth is allocated.
      • For Intel X9 shape, a minimum of 1 Gbps and a maximum of 32 Gbps of network bandwidth is allocated.
    • Theoretical max IOPS: The amount of input and output per second (IOPS) you want to allocate to this instance. Theoretical max IOPS is also dependent on the storage you select.

      For Ampere A1, AMD E4, and Intel X9 shapes, the theoretical max IOPS will scale proportionally based on the number of OCPUs selected. For each OCPU, 16K theoretical max IOPS is allocated.

      • For Ampere A1 shape, a minimum of 16K and a maximum of 640K theoretical max IOPS is allocated.
      • For AMD E4 shape, a minimum of 16K and a maximum of 640K theoretical max IOPS is allocated.
      • For Intel X9 shape, a minimum of 16K to a maximum of 512K theoretical max IOPS is allocated.
  10. Click Select shape.
  11. Configure storage
    To specify storage other than the default, click Change storage and select an available storage from the list.
    • Ampere A1 shape is only supported on Logical Volume Manager. When the Ampere A1 shape is selected, the storage management software type changes to Logical Volume Manager with the Higher Performance option.
  12. Choose Storage management software by selecting one of the following:
    • Oracle Grid Infrastructure to use Oracle Automatic Storage Management (recommended for production workloads). It allows management of storage spanning multiple nodes seamlessly and is recommended for resilience. Version 11g is only available when using Oracle Grid Infrastructure.
    • Logical Volume Manager to quickly provision your DB system using Logical Volume Manager storage management software.

      Note:

      • Ampere A1 shape is only supported on Logical Volume Manager.
      • The Available storage (GB) value you specify during provisioning determines the maximum total storage available through scaling.
  13. Configure storage performance by selecting the amount of storage required for this database.
    1. Select one of the following for Storage volume performance:
      • Balanced for most workloads that require a good balance between performance and cost savings.
      • Higher performance for large databases and workloads with high I/O requirement. It is the default performance level.
    2. In Available data storage (GB), select the amount of Block Storage in GB to allocate to the DB system.
      Available storage can be scaled up or down as needed after provisioning your DB system.

    The read-only Recovery area storage (GB) field displays the amount of storage available for recovery log data (RECO storage). The recovery area storage is determined based on the storage selected. However, you can change the recovery area storage independently after provisioning.

    The read-only Expected theoretical max IOPS for data storage displays the maximum theoretical IOPS that is achievable for the storage you have selected.

  14. Click Save changes.
  15. Configure the DB system.
    1. Specify the Total node count to define the number of nodes in the DB system.
      You can specify either one or two nodes. It also depends on the shape and storage you select.
      • Multi-node RAC DB systems require a minimum of two OCPUs per node and are not available on Logical Volume Manager.
      • Ampere A1 shape and VM.Standard2.1 shape are only available on single-node DB systems.
    2. Oracle Database software edition
      The database edition supported by the DB system. The database edition cannot be changed later.
      • Oracle Database Standard Edition is not supported on Ampere A1 shape-based DB systems.
    3. Total storage (GB)
      Read-only field. It displays the total amount of storage that will be used by the DB system, including storage required by the DB system software. The size of the backup determines the minimum value for available storage.
    4. Cluster name
      Displays only for multi-node DB systems to enable you to specify the cluster to store the node.
    5. Theoretical max IOPS
      Displays the maximum IOPS that is supported for your instance. It is the minimum of the network IOPS and storage IPOS you selected in the Configure Shape and Configure storage sections.
      • Maximum theoretical IOPS is calculated based on database with 8K block size.
  16. IOPS limiting factor
    Displays either Storage or Network based on which the theoretical max IOPS is determined. It helps identify if you need to increase storage or increase the network bandwidth (by increasing the number of OCPUs proportionally) for your shape if more IOPS are required.
  17. Add SSH key to upload your SSH public key for access.
  18. Choose the License Type
    • License Included means the cost of this Oracle Cloud Infrastructure Database service resource will include both the Oracle Database software licenses and the service.
    • Bring Your Own License means you will use your organization's Oracle Database software licenses for this Oracle Cloud Infrastructure Database service resource.
  19. Specify the network information
    1. Virtual cloud network. Click Change compartment to select a VCN in a different compartment.
      The VCN in which to create the DB system.
    2. Client subnet. Click Change compartment to select a subnet in a different compartment.
      The subnet to which the DB system attaches. For both single-node and multi-node RAC DB systems, do not use a subnet that overlaps with 192.168.16.16/28, which is used by the Oracle Clusterware private interconnect on the database instance. Specifying an overlapping subnet causes the private interconnect to malfunction.
    3. (Optional) Network security groups

      Optionally, you can specify one or more network security groups (NSGs) for your DB system. NSGs function as virtual firewalls, enabling you to apply a set of ingress and egress security rules to your DB system. A maximum of five NSGs can be specified.

      Note:

      If you select a subnet with a security list, the security rules for the DB system will be a union of the rules in the security list and the NSGs.

      To use network security groups:

      1. Select Use network security groups to control traffic. You must have a virtual cloud network selected to be able to assign NSGs to your DB system.
      2. Specify the NSG to use with the DB system. You may need to use more than one NSG. If you're not sure, contact your network administrator.
      3. To use additional NSGs, click + Another network security group.
  20. Host domain name for the DB system.
    If the selected subnet uses the Oracle-provided Internet and VCN Resolver for DNS name resolution, then this field displays the domain name for the subnet and it can't be changed. Otherwise, you can provide your choice of a domain name. Hyphens (-) are not permitted.
  21. Host and domain URL.
    Combines the host and domain names to display the fully qualified domain name (FQDN) for the database. The maximum length is 64 characters.
  22. Diagnostic collection.

    The diagnostics collection and notifications feature enables Oracle Cloud Operations and you to identify, investigate, track, and resolve guest VM issues quickly and effectively. Subscribe to events to get notified about resource state changes. You can enable or disable this feature at anytime.

  23. Click Show advanced options to specify advanced options for the DB system.
    For example, the fault domain in which the DB system resides and the default time zone for the DB system.
  24. Click Next to advance to the Database information screen and provide the following information for the initial database.
    1. Database name
      Enter the Database Name, also known as the DB_NAME, that corresponds to the source CDB name, or the source Database SID. The source and target database names must match in order for the restore phase to work seamlessly.
    2. Database image
      Determines what Oracle Database version is used for the database.
    3. Password
      Set a password for the SYS user matching the password requirements. The SYS password must be the same as the SYS password of the source database.
  25. Click Create DB system.