General Information

Procedure

1. Open the navigation menu. Select Oracle Database, then select Oracle Base Database Service.
2. Select your Compartment. A list of DB systems is displayed.
3. Navigate to the backup or standalone backup you want to use to create the new DB system:

   Note:

   If you are creating a database from an automatic backup, you may choose any level 0 weekly backup, or a level 1 incremental backup created after the most recent level 0 backup.
   • To select a daily automatic backup or on-demand full backup as the source:
     1. Find the DB system where the database is located, and click the system name to display details about it.
     2. From the Databases list, click the source database name.
     3. Find your desired backup in the Backups list. If you don't see the backups list on the Database Details page, click Backups in the Resources menu.
     4. Click the Actions menu for the backup, and then click Create database.
   • To select the last archived redo log automatic backup as the source:
     1. Find the DB system where the database is located, and click the system name to display details about it.
     2. Find the database associated with the backup you wish to use, and click its name to display details about it.
     3. On the Database Details page, click Create database from backup.
   • To specify a timestamp for a point-in-time copy of the source:
     1. Find the DB system where the database is located, and click the system name to display details about it.
     2. Find the database associated with the backup you wish to use, and click its name to display details about it.
     3. On the Database Details page, click Create database from backup.
     4. In the Create database from backup dialog, do the following:
        1. Select Create database from specified timestamp.
        2. In the Restore timestamp field, enter a timestamp. The restore timestamp determines the most recent data that will be included in the restored version of the database.
        3. Click Create.
   • To select a standalone backup or a long-term retention backup (LTR) as the source:
     1. Under Resources, click Standalone backups.
     2. In the list of standalone backups, find the backup you want to use to create the database.
     3. Click the Actions menu for the backup you are interested in, and then click Create database.
4. In the Create database from backup dialog, enter the following DB system information.
5. Select a compartment: Select a compartment for your new DB system. By default, the DB system is created in your current compartment and you can use the network resources in that compartment.
6. Name your DB system: A nonunique, display name for the DB system. An Oracle Cloud Identifier (OCID) uniquely identifies the DB system. Avoid entering confidential information.
7. Select a region: The target region where you want to create the database.
8. Select an availability domain: The availability domain in which the DB system should reside.
9. Configure shape: 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.
10. To specify a shape other than the default, click Change shape, and select an available shape from the list. For a complete list of shapes, see Available Shapes and How It Determines the Resources Allocated.
11. Shape series: Select Ampere, AMD, or Intel processor in the processor group.
    • Ampere: Shapes that use Arm-based Ampere processors. The Ampere shapes are flexible.
    • AMD: Shapes that use current-generation AMD processors. The AMD shapes are flexible.
    • Intel: Standard and optimized shapes that use current-generation Intel processors. Both fixed and flexible Intel shapes are available.

    Note:

    If you select Ampere A1, AMD E4, AMD E5, or Intel X9 flexible shapes, the memory, network bandwidth, and maximum theoretical IOPS scale proportionally.
12. Configure OCPU: Select the number of OCPUs you want to allocate to this instance. For Ampere A1, AMD E4, AMD E5, 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 and E5 shapes, 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, AMD E5, 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 and E5 shapes, 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, AMD E5, 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 and E5 shapes, 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, AMD E5, 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 and E5 shapes, 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.
13. Click Select shape.
14. 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.
15. Choose storage management software: Select one of the following:
    • Oracle Grid Infrastructure to use Oracle Automatic Storage Management (recommended for production workloads)
    • 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. For total storage available for each choice, see Storage Scaling Considerations While Using Fast Provisioning.
16. In the Configure storage performance section, in the Storage volume performance, select one of the following:
    • 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.

    In the 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. For more information about changing the recovery area storage, see Scale the DB System article.

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

17. Click Save changes.
18. Provide the following details in the Configure the DB system section.
19. Total node count: 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.
20. 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.
21. 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.
22. Cluster name: Displays only for multi-node DB systems to enable you to specify the cluster to store the node.
23. 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.
24. 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.
25. Add SSH key: Add the public key portion of each key pair you want to use for SSH access. Select on of the following options:
    • Generate SSH key pair: Use this option to create a new SSH key pair. Click both Save private key and Save public key when using this option. The private key is downloaded to your local system, and must be stored in a safe location. You cannot download another copy of the private key generated during this operation after completing the operation.
    • Upload SSH key files: Select this option to browse or drag and drop your existing public key (.pub) files.
    • Paste SSH keys: Select this option to paste in individual public keys. To paste multiple keys, click + Another SSH key, and supply a single key for each entry.
26. Choose a license type: The type of license you want to use for the DB system. Your choice affects metering for billing.
    • 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 (BYOL) means you will use your organization's Oracle Database software licenses for this Oracle Cloud Infrastructure Database service resource. For more information, see Bring Your Own License.
27. Provide the following details in the Specify the network information section.
28. Virtual cloud network: The VCN in which to create the DB system. Click Change compartment to select a VCN in a different compartment.

29. Client subnet 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.

    Click Change compartment to select a subnet in a different compartment.

    Choose a dual stack subnet if you want to configure the DB system with both IPv4 and IPv6 addresses.

30. 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.

    For more information, see Access and Security and Security Rules for the DB System.

    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. Check the Use network security groups to control traffic check box. Note that 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.
31. Host name prefix: Your choice of host name prefix for the DB system. The host name must begin with an alphabetic character, and can contain only alphanumeric characters and hyphens (-). The maximum number of characters allowed is 16.

    Note:

    The host name must be unique within the subnet. If it is not unique, the DB system will fail to provision.
32. Host domain name: The 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.
33. 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.

34. IP addresses: Optionally, for non-RAC DB systems, you can define the IP address of the new DB system. This is useful in development contexts where you create and delete a DB system over and over, and you need each new iteration of the DB system to use the same IP address. If you specify an IP address that is currently in use within the subnet, the provisioning operation will fail with an error message regarding the invalid IP address.

    If a dual stack subnet is selected, then both IPv4 and IPv6 address options are displayed.

    • IPv4 address: You can either automatically assign an IPv4 address or enter it manually.
      • Select the Automatically assign IPv4 addresses from subnet option to assign an address automatically.
      • Select the Manually assign IPv4 addresses option to manually enter a private IP address. The IP address should be within the subnet CIDR range.
    • IPv6 address: You can either automatically assign an IPv6 address or enter it manually.
      • Select the Automatically assign IPv6 addresses from subnet option to assign an address automatically.
      • Select the Manually assign IPv6 addresses option to manually enter an IP address. The IP address should be within the subnet CIDR range.

35. 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.

    By default the options are selected for enabling. However, you can select to uncheck the diagnostic collection check boxes if you do not require the diagnostic feature.

    • Enable diagnostic events: Enables and allows Oracle to collect and send fault notifications about critical, warning, and information events for you.
    • Enable incident logs and trace collection: Enables and allows Oracle to receive event notifications and collect incident logs and traces for fault diagnosis and issue resolution.

    Note:

    • The Enable health monitoring diagnostics collection for Oracle Cloud operations viewing is not available for the Base Database Service.
    • You are opting-in with the understanding that the list of events and log files can change in the future. You can opt-out of this feature at any time.
36. Click Show advanced options to specify advanced options for the DB system and provide the following details.
37. Fault domain: The fault domain(s) in which the DB system resides. You can select which fault domain to use for your DB system. For multi-node RAC DB systems, you can specify which two fault domains to use. Oracle recommends that you place each node of a multi-node RAC DB system in a different fault domain. For more information about fault domains, see About Regions and Availability Domains.
38. Time zone: The default time zone for the DB system is UTC, but you can specify a different time zone. The time zone options are those supported in both the Java.util.TimeZone class and the Oracle Linux operating system. For more information, see DB System Time Zone. The following options are available:
    • UTC: configures your DB system to use coordinated universal time.
    • Browser-detected: The console displays the time zone detected by your browser for this option.
    • Select another time zone: To manually specify a time zone, first make a choice using the Region or country selector to select a geographic region, then use the Time zone selector to select your required time zone.

    Tip:

    If you want to set a time zone other than UTC or the browser-detected time zone, and if you do not see the time zone you want, try selecting "Miscellaneous" in the Region or country list.

39. Security attributes: Optionally, you can specify one or more security attributes to configure Zero Trust Packet Routing (ZPR) for the DB system.

    1. Select the Namespace in which the required security attribute is available.
    2. Select the Key and Value of the required security attribute.
    3. Click Add security attribute.

    Note:

    • Administrators must set up security attribute namespaces and security attributes in a tenancy before users can apply security attributes to the DB systems.
    • A security attribute is effective only with appropriate policies. If a security attribute without any policies is added, all access will be denied by default, even if allowed in the Security List or NSGs.
    • If you use the security attribute, the security rules for the DB system will be a union of the rules in the security attributes along with any rules in the security list and the NSGs.
    • You may need to use more than one security attribute. If you're not sure, contact your network administrator.
    • A maximum of 3 security attributes can be specified for a DB system.

    For more information about:

    • add, edit, or remove a security attribute after a DB system is created, see Manage Security Attributes for the DB System.
    • defining appropriate ZPR policies, see Zero Trust Packet Routing.
    • creating a security attribute, see Creating a Security Attribute.
40. Tags: If you have permissions to create a resource, then you also have permissions to apply free-form tags to that resource. To apply a defined tag, you must have permissions to use the tag namespace. If you are not sure whether to apply tags, skip this option (you can apply tags later) or ask your administrator. For more information about tagging, see Resource Tags.
41. Click Next to advance to the Database information screen and provide the following information for the initial database.
42. Database name: The name for the database, also known as the DB_NAME. The database name must begin with an alphabetic character and can contain a maximum of eight alphanumeric characters. Special characters are not permitted.
43. Database unique name suffix: Optional. The second portion of the database unique name. The complete database unique name is created by appending the database unique name suffix to the database name you specify.
44. Database unique name: This read-only field displays the complete database unique name (DB_UNIQUE_NAME). The database unique name is a globally unique name for the database. Primary and standby databases in a Data Guard association can share the same database name, but must have different database unique names.
45. Unified Auditing: Select this check box to enable Unified auditing framework. Unified auditing provides selective and effective auditing inside the Oracle database using policies and conditions.Unified auditing option needs to be specified during provisioning. Unified auditing is enabled by default for Oracle Database 23ai. For more information, see Introduction to Auditing.

46. Database image: Optional. You can specify what Oracle Database version is used for the database. You can mix database versions on the DB system, but not editions. By default, the latest database software image as the source database is used.

    Click Change database image to choose a custom database software image that you or someone in your organization have created in your tenancy.

    Select a compartment and a database version. Then select a database image from the table of available images for the Oracle Database version you selected.

    After choosing a software image, click Select to return to the Database information Screen.

47. In the Create administrator credentials section, a database administrator named sys will be created with the password you supply.
48. Username: sys (This is a read-only field).
49. Password: Supply the password for this user. The password must meet the following criteria:
    • A strong password for SYS, SYSTEM, TDE wallet, and PDB administrator.
    • The password must be 9 to 30 characters and contain at least two uppercase, two lowercase, two numeric, and two special characters.
    • The special characters must be _, #, or -.
    • The password must not contain the user name (SYS, SYSTEM, and so on) or the word "oracle" either in forward or reversed order and regardless of casing.
50. Confirm password: Reenter the SYS password you specified.
51. Enter the source database's TDE wallet or RMAN password:(Applies only to databases using Oracle-managed encryption keys). Enter either the TDE wallet password or the RMAN encryption password for the backup, whichever is applicable. The TDE wallet password is the SYS password provided when the database was created by using the Console, API, or CLI. The RMAN encryption password is typically required instead if the password was subsequently changed manually.
52. Click Create DB system. The DB system appears in the list with a status of Provisioning. The DB system's icon changes from yellow to green (or red to indicate errors).

    After the DB system's icon turns green, with a status of Available, you can click the highlighted DB system name to display details about the DB system. Note the IP addresses. You'll need the private or public IP address, depending on network configuration, to connect to the DB system.