Oracle Cloud Infrastructure Documentation

Exadata Database

To create an Exadata Database and its associated components (Database Home, Container Database (CDB), and Pluggable Database (PDB)) using the OCI console, follow these steps.

    1. From Google Cloud dashboard, select the Exadata Database Service > Dedicated Infrastructure menu item.
    2. By default, the Exadata Infrastructure tab is selected. Select theExadata VM Cluster tab.
    3. Select the Manage in OCI icon which allows you to manage your Exadata VM Cluster in OCI.
      This screenshot shows the step to access the Manage in OCI icon.

    4. From the OCI console, select the Databases tab and then select the Create database button.
    5. From the Create database page, complete the following steps.
    6. From the Basic Information section, enter the following.
      1. Enter a Database name.
      2. Enter a Unique Database.
      3. From the dropdown list, select your Database version.
    7. From the Database Home section, enter the following.
      1. For your Database Home source, there are two available options. These options are Create a new Database Home and Select an existing Database Home. Based on your requirements, make a selection.
      2. Select the Enable Unified Auditing checkbox. This combines all database component audit trails into single unified audit file.
      3. From the Database image drop-down, select the image that will be used for database creation.
      4. Enter a PDB name.
    8. From the Create administrator credentials section, enter the following.
      1. The administrator username is sys.
      2. Enter your Password, and ensure that it conforms to the password complexity checks.
      3. Enter your Confirm password to ensure that it matches Password.
    9. From the Database backups section, enter the following.
      1. Select the Enable automatic backups button to enable automatic incremental backups for your database.
      2. In the Backup destination drop-down, you can select either Object Storage or Autonomous Recovery Service.
      3. In the Retention period of the backup, enter a value from 7 to 60 days.
      4. The Deletion options after database termination section provide options to retain protected database backups after the database is terminated. Based on your system requirements, make a selection.
      5. In the Scheduled day for full backup (UTC) section, choose a day of the week for the initial and future LO backups to start.
      6. In the Scheduled time for full backup (UTC) drop-down, select the time window when the full backups start.
      7. In the Scheduled time for incremental backup (UTC) drop-down, select the time window when the incremental backups start.
      8. Select the Take the first backup immediately button if you want to take your first backup immediately after successful database creation.
    10. From the Encryption section, allows you to choose either Use Oracle-managed keys or Use customer-managed keys.
    11. The Advanced options section, which is optional and collapsed by default, you can enter the following
      1. Enter your Oracle SID prefix.
        Note

        The Oracle Database instance number is automatically added to the SID prefix to create the INSTANCE_NAME database parameter.
      2. The Character set field is selected as AL32UTF8.
      3. The National character set field is selected as AL16UTF16.
    12. From the Tags section, enter the following.
      1. If you want to add a tag, select Add tag button.
      2. Select your Namespace from the drop-down. The default value is entered.
      3. Enter values for your Key and Value.
    13. Select the Create button to complete the process.
    14. Once your database is created, the Status changes from Provisioning to Available. From the database details page, select the specific Exadata Database. Navigate to Encryption section and select the Change button. This displays the current encryption settings for the selected Exadata Database.
      This screenshot shows the selected Exadata VM Cluster and the Exadata Database(s) created on that cluster.

  • There is currently no content for this page. Oracle Database@Google Cloud team intends to add content here, and this placeholder text is provided until that text is added. The Oracle Database@Google Cloud team is excited about future new features, enhancements, and fixes to this product and this accompanying documentation. We strongly recommend you watch this page for those updates.

  • There is currently no content for this page. Oracle Database@Google Cloud team intends to add content here, and this placeholder text is provided until that text is added. The Oracle Database@Google Cloud team is excited about future new features, enhancements, and fixes to this product and this accompanying documentation. We strongly recommend you watch this page for those updates.

  • There is currently no content for this page. Oracle Database@Google Cloud team intends to add content here, and this placeholder text is provided until that text is added. The Oracle Database@Google Cloud team is excited about future new features, enhancements, and fixes to this product and this accompanying documentation. We strongly recommend you watch this page for those updates.

  • There is currently no content for this page. Oracle Database@Google Cloud team intends to add content here, and this placeholder text is provided until that text is added. The Oracle Database@Google Cloud team is excited about future new features, enhancements, and fixes to this product and this accompanying documentation. We strongly recommend you watch this page for those updates.