1. Administering Oracle Database Classic Cloud Service
  2. Oracle Cloud Pages for Administering Database Classic Cloud Service
  3. Create Instance: Instance Details Page

Create Instance: Instance Details Page

Create Instance: Instance Details is a page in the Create Instance wizard you use to create a new database deployment. For more information, see Creating a Customized Database Deployment.

The following tables describe the key information shown on the Create Instance: Instance Details page:

What You See in the Navigation Area

Element Description

<Previous

Click to return to the Create Instance: Instance page.

Cancel

Click to cancel the Create Instance wizard without creating a new database deployment.

Next>

Click to advance to the Create Instance: Confirmation page.

What You See in the Database Configuration Section

Element Description

DB Name (SID)

The name for the database instance. The name:

  • Must not exceed 8 characters.

  • Must start with a letter.

  • Must contain only letters and numbers.

Note:

Do not modify this value after provisioning the database successfully.

PDB Name

(Available only for Oracle Database 12c.)

The name for the default pluggable database (PDB). The name:

  • Must not exceed 8 characters.

  • Must start with a letter.

  • Must contain only letters, numbers, or _ (underscore).

This option is not available if Create Instance from Existing Backup is set to Yes.

Note:

Do not modify this value after provisioning the database successfully.

Administration Password

Confirm Password

The password for the following administrative users:

  • Oracle Database administrative users

  • Oracle Application Express admin user

The password:

  • Must be 8 to 30 characters in length.

  • Must contain at least one lowercase letter

  • Must contain at least one uppercase letter

  • Must contain at least one number

  • Must contain at least one of these symbols: _ (underscore), # (hash sign), or $ (dollar sign).

  • Must not contain the word “oracle”.

Usable Database Storage (GB)

The amount of storage in GB for actual database data.

Note that up to 8% of this storage will be used for file system constructs and other overhead.

Total Data File Storage (GB)

The computed amount of storage in GB that will be allocated to the deployment, including space for operating system and product binaries, supporting files, database data and configuration files, and so on.

Compute Shape

The number of Oracle Compute Units (OCPUs) and amount of memory (RAM) for each compute node of the new database deployment. Database Classic Cloud Service offers several OCPU/RAM combinations, as described in Computing Power.

SSH Public Key

Edit

The SSH public key to be used for authentication when using an SSH client to connect to a compute node that is associated with your database deployment.

Click Edit to specify the public key. You can upload a file containing the public key value, paste in the value of a public key, or create a system-generated key pair.

If you paste in the value, make sure the value does not contain line breaks or end with a line break.

Use High Performance Storage

(Available only if you have a metered subscription and you chose an Oracle Cloud Infrastructure Classic region on the wizard’s Instance page.)

Controls the device type to be used for database block storage. By default, block storage is allocated on spinning devices. If you select this option, then block storage will be allocated on solid state devices, at an increased cost. For pricing details, refer to the Block Storage information at https://cloud.oracle.com/compute/compute/pricing.

Advanced Settings: Listener Port

The port number for the Oracle Net Listener.

The port number must be between 1521 and 5499 (inclusive).

Advanced Settings: Timezone

The time zone for the new database deployment. The default is Coordinated Universal Time (UTC).

Advanced Settings: Character Set

The database character set for the database. The database character set is used for:

  • Data stored in SQL CHAR data types (CHAR, VARCHAR2, CLOB, and LONG)

  • Identifiers such as table names, column names, and PL/SQL variables

  • Entering and storing SQL and PL/SQL source code

This option is not available if Create Instance from Existing Backup is set to Yes.

Advanced Settings: National Character Set

The national character set for the database. The national character set is used for data stored in SQL NCHAR data types (NCHAR, NCLOB, and NVARCHAR2).

This option is not available if Create Instance from Existing Backup is set to Yes.

Advanced Settings: Enable Oracle GoldenGate

(Not available on Oracle Cloud at Customer)

Configures the database for use as the replication database of an Oracle GoldenGate Cloud Service instance. See Using Oracle GoldenGate Cloud Service with Database Classic Cloud Service.

Advanced Settings: Include "Demos" PDB

(Available only for Oracle Database 12c Release 1.)

Controls whether the "Demos" PDB is to be included in the database. This PDB contains demos for many new features of Oracle Database 12c such as in-memory and multitenant. Usable Data File Storage must to be at least 25 GB to include this PDB.

Advanced Settings: IP Reservations

(Not available on Oracle Cloud Infrastructure)

(Available only if you chose an Oracle Cloud Infrastructure Classic region on the wizard’s Instance page.)

Specifies whether to use an IP reservation for this deployment. If you choose Assign Automatically, an IP reservation is not used and Database Classic Cloud Service acquires a new IP address for use by the deployment. Otherwise, Database Classic Cloud Service uses the IP reservation you choose.

What You See in the Backup and Recovery Configuration Section

Element Description

Backup Destination

Controls how backups for the deployment are to be configured:

  • Both Cloud Storage and Local Storage—backups are configured to be created automatically and stored both on local storage and on cloud storage.

    If this choice is selected, the Cloud Storage Container, User Name and Password fields are displayed.

  • Cloud Storage Only — backups are configured to be created automatically and stored on cloud storage.

    If this choice is selected, the Cloud Storage Container, User Name and Password fields are displayed.

    Note: This choice is not currently available for database deployments that use Oracle Real Application Clusters (Oracle RAC).

  • None—Backups are not configured for the deployment.

For more information about backups and backup configurations, see About Backing Up Database Deployments on Database Classic Cloud Service.

Cloud Storage Container

The location where backups to cloud storage are to be stored:

  • For database deployments in Oracle Cloud Infrastructure, enter the URL of an existing Oracle Cloud Infrastructure Object Storage bucket. The URL is of the form: 

    https://swiftobjectstorage.region.oraclecloud.com/v1/account/bucket

    For example:

    https://swiftobjectstorage.us-phoenix-1.oraclecloud.com/v1/mycompany/mybucket

    You must create this storage bucket before you begin creating the database deployment. See Object Storage API in Oracle Cloud Infrastructure documentation.

  • For database deployments in Oracle Cloud Infrastructure Classic, enter the location of an Oracle Cloud Infrastructure Object Storage Classic container using this form: 

    Storage-identity_domain/container

    where identity_domain is the id of the identity domain, and container is the name of the container. If this container doesn’t exist, use the Create Cloud Storage Container checkbox to create it.

    Note: In some Oracle Cloud Infrastructure Classic accounts, you cannot use the above form. If you get an error when you try to use this form, you must instead provide a full URL for the container using this form: 

    rest-endpoint-url/container

    To determine the rest-endpoint-url value for your account, see Finding the REST Endpoint URL for Your Service Instance in Using Oracle Cloud Infrastructure Object Storage Classic.

Cloud Storage User Name

A user with read/write (and creation, if necessary) access to the location specified in Cloud Storage Container:

  • For database deployments in Oracle Cloud Infrastructure, enter the user name you use to sign in to the Oracle Cloud Infrastructure console.

  • For database deployments in Oracle Cloud Infrastructure Classic, enter the Oracle Cloud user name of the administrator of the Oracle Cloud Infrastructure Object Storage Classic container specified in Cloud Storage Container. Usually, this is your Oracle Cloud user name.

Cloud Storage Password

The password necessary to access the location specified in Cloud Storage Container:

  • For database deployments in Oracle Cloud Infrastructure, enter your Swift password.

  • For database deployments in Oracle Cloud Infrastructure Classic, enter the password of the Oracle Cloud user specified in Cloud Storage User Name.

Create Cloud Storage Container

(Not available on Oracle Cloud Infrastructure)

Create a new Oracle Cloud Infrastructure Object Storage Classic container as part of the database deployment creation. Specify the container name and the Cloud Storage user name and password in the preceding fields.

Total Estimated Monthly Storage

Storage for data files and backups.

What You See in the Initialize Data From Backup Section

Element Description

Create Instance from Existing Backup

Create a database deployment whose database is derived from a cloud backup created using Oracle Database Backup Cloud Service.

The other fields and options in the Initialize Data From Backup section only display if Create Instance from Existing Backup is set to Yes.

On-Premises Backup

Indicates the origin of the source database backup.

Select this option if the source database backup is not from another Database Classic Cloud Service database deployment in the same identify domain. In this case, the following fields and options are displayed except for Source Service Name.

Deselect this option if the source database backup is from another Database Classic Cloud Service database deployment in the same identify domain. In this case, only the Source Service Name field is displayed.

Database ID

The database identifier of the database from which the existing backup was created. You can get this value by using the following SQL query:

SQL> SELECT dbid FROM v$database;

Decryption Method

Edit

Specifies the information necessary to decrypt the source database backup. Click Edit to specify the necessary information.

In the resulting dialog:

  • For a backup that uses Transparent Database Encryption (TDE), select Upload Wallet File then click Browse and specify a zip file containing the source database’s TDE wallet directory, and the contents of that directory.

    Note:

    If the source database is from another Database Classic Cloud Service database deployment, its TDE wallet directory is /u01/app/oracle/admin/dbname/tde_wallet.

  • For a backup that uses password encryption, select Paste RMAN Key Value and paste the password (key value) used to encrypt the backup.

Cloud Storage Container

The URL where the existing backup is stored:

  • The URL of an Oracle Cloud Infrastructure Object Storage bucket. The URL is of the form: 

    https://swiftobjectstorage.region.oraclecloud.com/v1/account/bucket

    For example:

    https://swiftobjectstorage.us-phoenix-1.oraclecloud.com/v1/mycompany/mybucket

  • The URL of an Oracle Cloud Infrastructure Object Storage Classic container. The URL is of the general form: 

    rest-endpoint-url/container

    To determine the rest-endpoint-url value for your account, see Finding the REST Endpoint URL for Your Service Instance in Using Oracle Cloud Infrastructure Object Storage Classic. If this container doesn’t exist, use the Create Cloud Storage Container checkbox to create it.

Username

The Oracle Cloud user name of the administrator of the Oracle Cloud Infrastructure Object Storage Classic container specified in Cloud Storage Container.

Password

The password of the user specified in Username.

Source Service Name

From the list of possible alternatives, specify the database deployment that is associated with the source database backup that you want to use.

What You See in the Standby Database Section

Element Description

Standby Database Configuration

Controls where the standby database is placed in relation to the primary database:

  • High Availability—The standby database is placed in a different availability domain from the primary database, thus providing isolation at the infrastructure level.

  • Disaster Recovery—The standby database is placed in a different data center from the primary database, thus providing isolation at the infrastructure level and geographical separation to support availability despite catastrophic events.

See Using Oracle Data Guard in Database Classic Cloud Service for more information.

If you choose this option, the Enable Oracle GoldenGate option is disabled.