Creating a Customized Database Deployment

To create a customized database deployment on Oracle Database Classic Cloud Service, use the Create Instance wizard as described in the following procedure.

However, before using the Create Instance wizard, you need to make sure that you have all of the necessary information, as described in Before You Begin. Additionally, after your database deployment is created you need to perform a few follow-on tasks to make sure your deployment is accessible and up-to-date, as described in After Your Database Deployment Is Created.

Before You Begin

When you create a database deployment, you provide information used to create the deployment itself and the Oracle database it hosts. In addition, you may need to provide information about other resources:

• An SSH public/private key pair (Optional)

  You must associate an SSH public key with the compute infrastructure supporting the deployment. An SSH public key is used for authentication when you use an SSH client to connect to a compute node associated with the deployment. When you connect, you must provide the private key that matches the public key.

  You can have the wizard create a public/private key pair for you, or you can create one beforehand and upload or paste its private key value. If you want to create a key pair beforehand, you can use a standard SSH key generation tool. See Generating a Secure Shell (SSH) Public/Private Key Pair.

• A cloud storage backup location (Optional)

  If you want to automatically back up your database to cloud storage, you must associate it with a cloud storage backup location. The type of location you specify depends on the infrastructure the deployment is built on:

  • Oracle Cloud Infrastructure: cloud backups are stored in an Oracle Cloud Infrastructure Object Storage bucket. You must create a storage bucket before you create database deployments configured to back up to cloud storage.

  • Oracle Cloud Infrastructure Classic: cloud backups are stored in an Oracle Cloud Infrastructure Object Storage Classic container. You can create the container beforehand and provide the wizard with information about it, or you can have the wizard create the container for you.

    The container becomes associated with Oracle Database Backup Cloud Service, which Database Classic Cloud Service uses to perform backups to cloud storage. Once associated with Oracle Database Backup Cloud Service, the container becomes part of your Oracle Database Public Cloud Services subscription (or trial) rather than part of an Oracle IaaS Public Cloud Services subscription (or trial).

    Whether you create the container beforehand or have the wizard do it for you, you are prompted for the following information about the container:

    • The name of the container

    • The user name and password of a user who has read/write access to the container

• A existing cloud backup created using Oracle Database Backup Cloud Service (Optional)

  If you are creating a database deployment hosting a single-instance database, you can have the new database populated, or “instantiated”, from the data stored in the Database Backup Cloud Service backup of a 12.2.0.1, 12.1.0.2 or 11.2.0.4 Oracle database. You can use this instantiate-from-backup technique if:

  • The backed-up database is version 12.2.0.1, 12.1.0.2 or 11.2.0.4 with the latest PSU (patch set update) applied.

  • If the backed-up database is an Oracle 12c database, it must be multitenant (CDB). Database Classic Cloud Service does not support non-CDB Oracle 12c databases.

  • The backed-up database uses File System or ASM as its storage method for data files.

  • The database recovered from the backup will be smaller than 2 TB (1.2 TB if you plan to back up the new deployment to both cloud and local storage).

  If you use this instantiate-from-backup technique, you are prompted for the following information:

  • The database ID of the backed-up database

  • The password used when creating the backup (for backups that use password encryption)

  • A zip file containing the source database’s TDE wallet directory (for backups that use TDE encryption)

  • The name of the Oracle Cloud Infrastructure Object Storage Classic container where the backup is stored

  • The user name and password of an Oracle Cloud user who has read access to the container

  Note that after using this instantiate-from-backup technique, Oracle Application Express, DBaaS Monitor and ORDS (Oracle REST Data Services) may not be accessible. To restore accessibility, see Application Express, DBaaS Monitor and ORDS inaccessible after creating a database deployment using a cloud backup in Known Issues for Oracle Database Classic Cloud Service.

Procedure

To create a database deployment on Database Classic Cloud Service:

1. Open the Oracle Database Classic Cloud Service console.

   For detailed instructions, see Accessing the Oracle Database Classic Cloud Service Console.

2. Click Create Instance.

   The Create Instance wizard starts and the Instance page is displayed.

3. On the Instance page, provide a name and description for the database deployment, and provide information about its high-level characteristics. When you are finished, click Next to advance to the Instance Details page.

   Element	Description
   Instance Name	The name for the new database deployment. The name: Must not exceed 50 characters. Must start with a letter. Must contain only letters, numbers, or hyphens. Must not contain any other special characters. Must be unique within the identity domain.
   Description	(Optional) A description for the new database deployment.
   Notification Email	(Optional) An email address where you would like updates about the deployment-creation operation to be sent.
   Region	(Available only if your identity domain is enabled for regions.) The region for the database deployment. 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 Classic Cloud Service choose an Oracle Cloud Infrastructure Classic region for you.
   Availability Domain	(Available only on Oracle Cloud Infrastructure) The availability domain (within the region) where the database deployment will be placed.
   Subnet	(Available only on Oracle Cloud Infrastructure) The subnet (within the availability domain) that will determine network access to the database deployment.
   IP Network	(Available only if you have selected an Oracle Cloud Infrastructure Classic region and you have defined one or more IP networks created in that region using Oracle Cloud Infrastructure Compute Classic.) 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. For more information about IP networks, see these topics in Using Oracle Cloud Infrastructure Compute Classic: About IP Networks Creating an IP Network
   Assign Public IP	(Available only if you have selected an IP network.) Choose whether to assign public IP addresses to the compute nodes in your database deployment. If you select this check box (default), then any node added during deployment creation, or later added as part of a scaling operation, will have a public IP address assigned to it. You will be able to directly access the nodes from the public Internet. If you deselect this check box, then any node added during deployment creation, or later added as part of a scaling operation, will not have a public IP address assigned to it. You will not be able to directly access the nodes from the public Internet. This selection is for use cases where you intend to access the nodes and the database only from within your IP network or from your on-premises data center over a VPN network.
   License Type	(Available only in accounts that use the Universal Credits payment model) Controls how the right to use Oracle Database on the new deployment is established. To use the "Bring Your Own License" (BYOL) feature, which enables you to use an existing perpetual Oracle Database license to establish the right to use Oracle Database on a deployment, select My organization already owns Oracle Database software licenses. Bring my existing database software license to the Oracle Database Cloud Service. Your Oracle Cloud account will be charged a lesser amount for the new deployment because the right to use Oracle Database is covered by your perpetual license agreement. To use your Oracle Cloud account, select Subscribe to a new Oracle Database software license and the Oracle Database Cloud Service. Your account will be charged for the new deployment according to your Oracle Database Cloud Service agreement.
   Service Level	(Available only in accounts that include Oracle Database Exadata Cloud Service or old accounts that predate the Universal Credits payment model.) The service level for the new deployment: Oracle Database Cloud Service is the service level you should choose for Database Classic Cloud Service. Oracle Database Cloud Service - Virtual Image (Not available on Oracle Cloud Infrastructure)
   Metering Frequency	(Available only in old accounts that predate the Universal Credits payment model.) The metering frequency for the new deployment: Hourly Monthly
   Software Release	The release version of Oracle Database for the new deployment: Oracle Database 11g Release 2 Oracle Database 12c Release 1 Oracle Database 12c Release 2 Oracle Database 18c See Oracle Database Software Release.
   Software Edition	The Oracle Database software package for the new deployment: Standard Edition Enterprise Edition Enterprise Edition - High Performance Enterprise Edition - Extreme Performance See Oracle Database Software Edition.
   Database Type	The type of deployment to create: Single Instance—A single Oracle Database instance and database data store hosted on one compute node. For more information about this type, see Characteristics of a Single Instance Database Deployment. Database Clustering with RAC—A two-node clustered database using Oracle Real Application Clusters technology; two compute nodes each host an Oracle Database instance, and the two instances access the same shared database data store. For more information about this type, see Characteristics of a Database Clustering with RAC Database Deployment. (Not available on Oracle Cloud Infrastructure or on Oracle Cloud at Customer) Single Instance with Data Guard Standby—Two single-instance databases, one acting as the primary database and one acting as the standby database in an Oracle Data Guard configuration. For more information about this type, see Characteristics of a Single Instance with Data Guard Standby Database Deployment. Database Clustering with RAC and Data Guard Standby—Two two-node Oracle RAC databases, one acting as the primary database and one acting as the standby database in an Oracle Data Guard configuration. For more information about this type, see Characteristics of a Database Clustering with RAC and Data Guard Standby Database Deployment. (Not available on Oracle Cloud Infrastructure or on Oracle Cloud at Customer) Data Guard Standby for Hybrid DR — Single-instance database acting as the standby database in an Oracle Data Guard configuration. The primary database is on your own system. (Not available on Oracle Cloud Infrastructure or on Oracle Cloud at Customer) Not all types are available with all combinations of service level and software edition: Single Instance is the only type supported by the Standard Edition software edition. The two types that use Oracle RAC are available only with Enterprise Edition - Extreme Performance software edition.

4. On the Instance Details page, complete the Database Configuration section by providing information about the Oracle Database you want to create.

   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.

5. On the Instance Details page, complete the Backup and Recovery Configuration section, choosing a backup option for the database deployment and, depending on your choice, providing information about the Oracle Storage Cloud Service container where cloud backups are to be stored.

   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.

6. On the Instance Details page, complete the Initialize Data From Backup section if you are having the new database populated, or “instantiated”, from the data stored in the Database Backup Cloud Service backup.

   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.

7. On the Instance Details page, complete the Standby Database Configuration section. When you are finished, click Next to advance to the Confirmation page.

   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.

8. On the Confirmation page, review the information listed. If you are satisfied with the information, click Create.

   If you need to change the information, use the navigation bar or Back button at the top of the wizard to step back through the pages in the wizard. Click Cancel to cancel out of the wizard without creating a new database deployment.

After Your Database Deployment Is Created

After your database deployment is created, you should perform the following actions:

• Enable network access to the deployment

  By default, strict security restrictions limit network access to database deployments. To open access to applications and management tools, you need to enable predefined network security rules or create and enable your own network security rules. See Enabling Access to a Compute Node Port.

• Update cloud tooling

  While the base images used to create Database Classic Cloud Service database deployments are updated regularly, it is possible that even more recent updates to the cloud tooling are available. Therefore, you should check for and apply any updates to the cloud tooling. See Updating the Cloud Tooling on Database Classic Cloud Service.

• Apply database patches

  While the base images used to create Database Classic Cloud Service database deployments are updated regularly, it is possible that a newer patch set update (PSU) or bundle patch (BP) is available. Therefore, you should check for and apply any database patches that are available. See Applying a Patch.