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 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
Cluster	Specifies the VM cluster to host the database deployment. This option is only available if your Exadata Cloud at Customer system environment is enabled to configure multiple VM clusters.
DB Name	The name for the database instance.
PDB Name	The name for the default pluggable database (PDB). This option is available only for Oracle Database 12c, or later. This option is not available if Create Instance from Existing Backup is set to Yes.
Administration Password Confirm Password	The administration password, which is used to configure administration accounts and functions in the database deployment, including the password for the Oracle Database SYS and SYSTEM users.
Oracle Homes	Specifies the option to create a new Oracle Home directory location, or an existing Oracle Home location.
Oracle Home Name	(Optional) If you previously selected the option to create a new Oracle Home directory location, you can specify a name prefix for the new Oracle Home location. If specified, the value becomes the first part of the full Oracle Home name, which also includes a string identifying the Oracle Database release and latest applied bundle patch, along with numeric identifiers that are used to uniquely identify the Oracle Home location. If you do not specify a value, then the new Oracle Home location is given a system-generated name.
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. Note: The SSH Public Key field will not be displayed if the selected Exadata Cloud at Customer environment already contains a previously specified SSH key.
Advanced Settings: Application Type	Specifies how the database deployment is configured: Transactional (OLTP) — configures the database for a transactional workload, with a bias towards high volumes of random data access. Decision Support or Data Warehouse — configures the database for a decision support or data warehouse workload, with a bias towards large data scanning operations. Note: The Application Type field is only displayed when you create the first database deployment on an Exadata system. Subsequent database deployments are created with a standardized database configuration.
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	Configures the database for use as the replication database of an Oracle GoldenGate Cloud Service instance. See Using Oracle GoldenGate Cloud Service with Exadata Cloud at Customer.

What You See in the Backup and Recovery Configuration Section

Element	Description
Backup Destination	Controls the destination and configuration of automatic backups: Both Cloud Storage and Exadata Storage — enables two separate backup sets containing periodic full (RMAN level 0) backups and daily incremental backups. The backup to cloud storage uses an Oracle Storage Cloud container, with a seven day cycle between full backups and an overall retention period of 30 days. The backup to Exadata storage uses space in the RECO disk group, with a seven day cycle between full backups and a seven day retention period. Note: This option is only available if you provisioned for database backups on Exadata storage. See Exadata Storage Configuration. Cloud Storage Only — uses an Oracle Storage Cloud container to store periodic full (RMAN level 0) backups and daily incremental backups, with a seven day cycle between full backups and an overall retention period of 30 days. Note: To eliminate possible confusion or contention, do not use a single cloud storage container as a backup destination for multiple database deployments. ZDLRA Storage Only — uses the Recovery Appliance to store one full (RMAN level 0) backup and daily incremental (RMAN level 1) backups. The Recovery Appliance creates virtual full backups from each daily incremental and validates those backups to ensure that they are always recoverable. Note: This option is only available if you configured your Exadata Cloud at Customer environment to enable database backups on ZDLRA. See Creating an Exadata Cloud at Customer Instance. None — no automatic backups are configured. For more information about backups and backup configurations, see About Backing Up Database Deployments on Exadata Cloud at Customer.
Cloud Storage Container	The name of an existing Oracle Storage Cloud Service container or a new one to be created in the format: instance-id_domain/container where `instance` is the name of the Oracle Storage Cloud Service instance, `id_domain` is the id of the identity domain, and `container` is the name of the container. This field is only displayed if cloud storage is included in your Backup Destination choice.
Username	The user name of a user who has read/write access to the specified Cloud Storage Container. This field is only displayed if cloud storage is included in your Backup Destination choice.
Password	The password of the user specified in Username. This field is only displayed if cloud storage is included in your Backup Destination choice.
Create Cloud Storage Container	Create a new Oracle Storage Cloud Service container as part of the database deployment creation. Specify the container name and the Cloud Storage user name and password in the preceding fields. This field is only displayed if cloud storage is included in your Backup Destination choice.
Zdlra Storage Container	The TNS connect string to connect to the Oracle Zero Data Loss Recovery Appliance (ZDLRA). This field is only displayed if your Backup Destination choice is ZDLRA Storage Only.
Username	The virtual private catalog (VPC) user name for the ZDLRA specified in Zdlra Storage Container. This field is only displayed if your Backup Destination choice is ZDLRA Storage Only.
Password	The password of the user specified in Username. This field is only displayed if your Backup Destination choice is ZDLRA Storage Only.

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 Exadata Cloud at Customer 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 Exadata Cloud at Customer 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 Exadata Cloud at Customer database deployment, its TDE wallet directory is `/u02/app/oracle/admin/dbname/tde_wallet` or `/var/opt/oracle/dbaas_acfs/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 name of the Oracle Cloud Infrastructure Object Storage Classic container where the existing backup is stored; use this format: instance-id_domain/container where `instance` is the name of the Oracle Cloud Infrastructure Object Storage Classic instance, `id_domain` is the id of the identity domain, and `container` is the name of the container.
Username	The user name of an Oracle Cloud user who has read access to the 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 — indicates that the standby database is placed on a different Exadata system in the same region (data center) as the primary database, thus providing isolation at the Exadata system infrastructure level. Disaster Recovery — indicates that the standby database is placed in a different region (data center) from the primary database, thus providing isolation at the Exadata system infrastructure level and geographical separation to protect against catastrophic data center failure. See Using Oracle Data Guard in Exadata Cloud at Customer for more information.
Exadata System	Select an available Oracle Exadata Database Machine configuration to host the standby database. The list contains the Oracle Exadata Database Machines that are associated with your active Exadata Cloud at Customer instances.
Cluster	Specifies the VM cluster to host the standby database. This option is only available if your Exadata Cloud at Customer system environment is enabled to configure multiple VM clusters.
Hostnames	Specify one or more compute nodes that you want to host the database instances for the standby database.