The name for the new database deployment. The name:
(Available only if your identity domain is enabled for regions.)
If you choose a region that supports Oracle Cloud Infrastructure, the Availability Domain and Subnet fields are displayed, and the deployment will be created on Oracle Cloud Infrastructure. Otherwise, the deployment will be created on Oracle Cloud Infrastructure Classic. Choose No Preference to let Database Cloud Service choose an Oracle Cloud Infrastructure Classic region for you.
Note: If you are creating a database deployment that uses Oracle Data Guard on Oracle Cloud Infrastructure Classic, choose the value No Preference. Currently, region specification is not supported for deployments that use Oracle Data Guard on Oracle Cloud Infrastructure Classic.
(Available only on Oracle Cloud Infrastructure) The availability domain (within the region) where the database deployment will be placed.
(Available only on Oracle Cloud Infrastructure) The subnet (within the availability domain) that will determine network access to the database deployment.
The service level for the new deployment:
Oracle Database Cloud Service
Oracle Database Cloud Service – Virtual Image (Not available in accounts that use the Universal Credits payment model) (Not available on Oracle Cloud
Infrastructure)
Select the IP network where you want the database deployment placed.
Choose
No Preference to use the default
shared network provided by Oracle Cloud Infrastructure Compute Classic.
Note:
Currently, the following limitations apply to IP networks:
SSH is a cryptographic network protocol that uses two keys, one public and one private, to provide secure communication between two networked computers. Port 22 is the standard TCP/IP port that is assigned to SSH servers, and on Database Cloud Service instances this port is accessible to external clients by default.
When creating a database deployment, you specify the public key on the Service page of the Create Instance wizard by:
When you access a compute node using SSH, you must provide the private key that matches the public key specified when the database deployment was created.
During creation of database deployment you choose the usable amount of data storage increment upto maximum 2TB.You may add space after creation of instance too.
By adding more space you can increase storage upto 4.6 TB with local backup and 12 TB without local backup.7.6 TB for deployment hosting for oracle RAC database backup.
Scaling up storage is responsibility for CLoud Dabatase Admin.
Controls how backups for the deployment are to be configured:
—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.
— 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).
—Backups are not configured for the deployment.