[Oracle Cloud] - De-Installing TFA in Oracle Cloud environment using dbaascli

De-Installing TFA in Oracle Cloud using dbaascli


In the previous article[click here], we did look at how we install TFA on compute node in Oracle Cloud environment using dbaascli command line utility.

Here in this article, we will be de-installing TFA from Oracle cloud compute node using dbaascli command line utility.

First connect to compute node using opc user and then switch to root user. Check the current status of TFA.

[root@RAJDB121 opc]# ps -ef | grep tfa  
 root   2018   1 0 Feb03 ?    00:00:28 /bin/sh /etc/init.d/init.tfa run  
 root   14288   1 0 Feb03 ?    00:12:24 /var/opt/oracle/tfa/rajdb121/tfa_home/jre/bin/java -Xms128m -Xmx256m oracle.rat.tfa.TFAMain /var/opt/oracle/tfa/rajdb121/tfa_home  
 oracle  28260   1 0 18:54 ?    00:00:00 /usr/bin/perl /var/opt/oracle/misc/dbcsmonitor.pl /var/opt/oracle/tfa/rajdb121/tfa_home /var/opt/oracle/tfa/repository/suptools/rajdb121/dbcsmon /var/opt/oracle/tfa/repository/suptools/rajdb121/dbcsmon/oracle  
 root   28955 14288 0 18:59 ?    00:00:00 /bin/sh /var/opt/oracle/tfa/rajdb121/tfa_home/bin/tfactl rediscover -mode full -auto  
 root   28969 28955 35 18:59 ?    00:00:00 /u01/app/oracle/product/12.1.0/dbhome_1/perl/bin/perl /var/opt/oracle/tfa/rajdb121/tfa_home/bin/tfactl.pl rediscover -mode full -auto  
 root   29035 28800 0 18:59 pts/1  00:00:00 grep tfa  
 

[root@RAJDB121 opc]# cd /var/opt/oracle/tfa/rajdb121/tfa_home/bin  

 [root@RAJDB121 bin]# ./tfactl status  
 .-------------------------------------------------------------------------------------------------.  
 | Host   | Status of TFA | PID  | Port | Version  | Build ID       | Inventory Status |  
 +----------+---------------+-------+-------+------------+----------------------+------------------+  
 | rajdb121 | RUNNING    | 14288 | 59017 | 12.2.1.1.1 | 12211120170612181835 | COMPLETE     |  
 '----------+---------------+-------+-------+------------+----------------------+------------------'  
 [root@RAJDB121 bin]#  

Now, invoke dbaascli command line utility and run the tfa uninstall sub-command of dbaascli to de-install TFA from the compute node on which you are logged in.

 [root@RAJDB121 opc]# dbaascli  
 DBAAS CLI version 1.0.0  

 DBAAS>tfa uninstall  
 Executing command tfa uninstall  
 Deinstalling TFA  
 Removing TFA repository  
 Successfully uninstalled TFA  
 DBAAS>  

Once, TFA uninstall is done then exit from dbaascli utility, you would see a shell error as highlighted below(if your current working directory were TFA HOME before invoking dbaascli utility), that means when you uninstall TFA from the compute node then that also removes all related binaries and folders from the compute node. TFA HOME gets dropped.

 DBAAS>q  
 Exiting Command Line Interface  
 shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory  
 [root@RAJDB121 bin]# pwd  
 /var/opt/oracle/tfa/rajdb121/tfa_home/bin  
 [root@RAJDB121 bin]# ls  

[root@RAJDB121 ~]# cd /var/opt/oracle/tfa/rajdb121/tfa_home  
 bash: cd: /var/opt/oracle/tfa/rajdb121/tfa_home: No such file or directory 

[Oracle Cloud] - Installing TFA in Oracle Cloud environment using dbaascli

Installing TFA in Oracle Cloud using dbaascli


Here I would be demonstrating how we can install Oracle Trace File Analyzer(TFA) in Oracle Cloud environment using dbaascli utility in just a single hit. You have got so much simplicity provided by Oracle public cloud to play with database deployments by using Oracle provided cloud tooling.

TFA - Oracle Trace File Analyzer, collects all diagnostics data(which is composed of logs and traces referencing the problem or incident that we are supposed to diagnose) related to the problem or incident and combines all those diagnostic data in a single compressed zip file to upload to Oracle support service request to analyse the issue by Oracle support engineer.

If you are using Oracle Real Application Cluster then TFA will automatically collect all diagnostic data from both Grid and Oracle RDBMS Home that are related to the incident.

There are lots of things TFA does but those are not in scope of this article to discuss here so we will be concentrating on just installing it in Oracle cloud environment using dbaascli utility :-)


Following the are the sub-commands available with DBAAScli to work the TFA.

 DBAAS>tfa -help  
 Executing command tfa -help  
 Valid Subcommands:  
   install  
   uninstall 

Now, let go ahead and install TFA on compute node of our oracle cloud database deployment. In order to install it, you must be connect as root user, so first to connect to compute node with opc user and switch to root user as follows:

1 - Switch to root user once you are connected to compute node of oracle cloud database deployment.

 [opc@RAJDB121 ~]$ sudo -s  
 [root@RAJDB121 opc]# dbaascli  
 DBAAS CLI version 1.0.0  

2 - Please make a note that TFA is installed on Oracle cloud compute nodes and if you try to install it then it will just re-install the TFA or update it if latest TFA bundle is available.

 DBAAS>tfa install  
 Executing command tfa install  
 tfa.pm: WARNING: TFA already enabled. Reinstalling. <<<<< Already installed hence re-installing it
 Installing TFA.  
 Stopping dbcsmon  
 tfa.pm: INFO dbcsmon status is:  
 Stopping OSWatcher  
 tfa.pm: INFO OSWatcher status is:  
 Setting TFA's repository size to 300 MB  
 Enabling TFA auto startup  
 Enabling TFA auto collection  
 Setting TFA's minimal space for RTScan  
 Adding dbaastools log directories  
 Adding APEX log directories  
 Running tfactl stop command  
 Successfully installed TFA  
 Running tfactl start command  
 Starting dbcsmon  
 tfa.pm: INFO dbcsmon status is:  
 DBAAS>  

If TFA is not already install then it simply install it with latest version available as follows and it doesn't write any warning.

 DBAAS>tfa install  
 Executing command tfa install  
 Installing TFA.  
 Stopping dbcsmon  
 tfa.pm: INFO dbcsmon status is:  
 Stopping OSWatcher  
 tfa.pm: INFO OSWatcher status is:  
 Setting TFA's repository size to 300 MB  
 Enabling TFA auto startup  
 Enabling TFA auto collection  
 Setting TFA's minimal space for RTScan  
 Adding dbaastools log directories  
 Adding APEX log directories  
 Running tfactl stop command  
 Successfully installed TFA  
 Running tfactl start command  
 Starting dbcsmon  
 tfa.pm: INFO dbcsmon status is:  
 DBAAS>  

3 - Once, TFA is installed on compute node of Oracle database deployment of oracle cloud then you can validate its running status as follows:

 [root@RAJDB121 opc]# ps -ef | grep tfa  
 root   2018   1 0 18:52 ?    00:00:00 /bin/sh /etc/init.d/init.tfa run  
 root   14288   1 4 18:54 ?    00:00:06 /var/opt/oracle/tfa/rajdb121/tfa_home/jre/bin/java -Xms128m -Xmx256m oracle.rat.tfa.TFAMain /var/opt/oracle/tfa/rajdb121/tfa_home  
 oracle  14507   1 0 18:54 ?    00:00:00 /usr/bin/perl /var/opt/oracle/misc/dbcsmonitor.pl /var/opt/oracle/tfa/rajdb121/tfa_home /var/opt/oracle/tfa/repository/suptools/rajdb121/dbcsmon /var/opt/oracle/tfa/repository/suptools/rajdb121/dbcsmon/oracle  
 root   15965 26343 0 18:56 pts/1  00:00:00 grep tfa 

From above output, you can identify TFA HOME as /var/opt/oracle/tfa/rajdb121/tfa_home


Validate the status of TFA components by status sub-command of tfactl command line utility as follows:

 [root@RAJDB121 bin]# ./tfactl  
 tfactl> status  
 .-------------------------------------------------------------------------------------------------.  
 | Host   | Status of TFA | PID  | Port | Version  | Build ID       | Inventory Status |  
 +----------+---------------+-------+-------+------------+----------------------+------------------+  
 | rajdb121 | RUNNING    | 14288 | 59017 | 12.2.1.1.1 | 12211120170612181835 | COMPLETE     |  
 '----------+---------------+-------+-------+------------+----------------------+------------------'  
      

[Oracle Cloud] : Creating On-Demand Backup using bkup_api utility

Creating On-Demand Backup : Oracle Database Cloud Service

In this article, I will be demonstrating one way of taking On-Demand backup of Oracle Database Cloud Service Database Deployment in Oracle Public Cloud. You can create on-demand backup of single instance Oracle Cloud database deployment using bkup_api utility. We will talk about taking on-demand backup of Oracle Real Application(RAC) database in Oracle Cloud in another article.

It might be required to take on-demand backup of your oracle cloud database deployment in case if you have not configured automatic Oracle Database deployment backup while creating the database deployment in oracle cloud or before any maintenance operations going to happen in your database deployment.

Note - You can't configure an automatic backup for an existing Oracle Database Deployment in oracle cloud once that is created with  Backup option "none" to not automatically backup the Oracle cloud database deployment during service creation time, you would have to configure the backups manually and set it via cron jobs / or use bkup_api automated cloud backup utility.

Here we will be using the bkup_api oracle cloud backup utility to backup our single instance Oracle cloud database deployment to Oracle Storage Cloud Container(You should have Oracle Database Backup Cloud Service already activate and cloud storage container created in order to take database deployment backup to oracle cloud storage) 

1 - Connect to the Compute Node of DBaaS instance as opc user.

2 – Switch to root user to run bkp_api utility as it requires root privilege to run otherwise you would get following self-explanatory error if backup attempt is made with opc user.

[opc@RAJDB121 ~]$ /var/opt/oracle/bkup_api/bkup_api i bkup_start

API::ERROR Api requires root rights or sudoer

Switch to root user as below.

[opc@RAJDB121 ~]$ sudo -s
[root@RAJDB121 opc]#

3 – Run the bkup_api utility with bkup_start option to start taking backup of the Oracle cloud database deployment.

[root@RAJDB121 opc]# /var/opt/oracle/bkup_api/bkup_api bkup_start

DBaaS Backup API V1.5 @2016 Multi-Oracle home

DBaaS Backup API V1.5 @2015 Multi-Oracle home

-> Action : bkup_start

-> logfile: /var/opt/oracle/bkup_api/log/bkup_api.log

UUID 12eceb08-050f-11e8-a8f6-c6b062e43847 for this backup

** process started with PID: 1270

** see log file for monitor progress

4 – Once you start the backup job then you can monitor the backup progress using its log file - /var/opt/oracle/bkup_api/log/bkup_api.log .

[root@RAJDB121 opc]# tail -f /var/opt/oracle/bkup_api/log/bkup_api.log

Mon, 29 Jan 2018 16:11:51 -------------------------------------

Mon, 29 Jan 2018 16:11:51 12eceb08-050f-11e8-a8f6-c6b062e43847 -> Starting execution of backup log in background

Mon, 29 Jan 2018 16:11:51 12eceb08-050f-11e8-a8f6-c6b062e43847 STARTING BACKUP REQUEST

Mon, 29 Jan 2018 16:11:51 UUID 12eceb08-050f-11e8-a8f6-c6b062e43847 written with PID 1270

Mon, 29 Jan 2018 16:11:51 12eceb08-050f-11e8-a8f6-c6b062e43847 Checking if RCDB121 resource is available

Mon, 29 Jan 2018 16:11:51 12eceb08-050f-11e8-a8f6-c6b062e43847 has a lock RCDB121

Mon, 29 Jan 2018 16:11:51 12eceb08-050f-11e8-a8f6-c6b062e43847 The process is no longer running removing lock

Mon, 29 Jan 2018 16:11:51 12eceb08-050f-11e8-a8f6-c6b062e43847 registering request into the database

Mon, 29 Jan 2018 16:11:59 12eceb08-050f-11e8-a8f6-c6b062e43847 current backups 1904

Mon, 29 Jan 2018 16:11:59 12eceb08-050f-11e8-a8f6-c6b062e43847 command /var/opt/oracle/ocde/assistants/bkup/obkup

5 – Another way to monitor the currently running backup job with bkup_status option of bkup_api utility as below.

[root@RAJDB121 opc]# /var/opt/oracle/bkup_api/bkup_api bkup_status  
 DBaaS Backup API V1.5 @2016 Multi-Oracle home  
 DBaaS Backup API V1.5 @2015 Multi-Oracle home  
 -> Action : bkup_status  
 -> logfile: /var/opt/oracle/bkup_api/log/bkup_api.log  
  Warning: unable to get current configuration of: catalog  
 * Current backup settings:  
 * Last registered Bkup: 01-29 16:11 API::1270:: Starting dbaas backup process  
 * Bkup state: running  
 **************************************************  
 * API History: API steps  
  API:: NEW PROCESS 1270  
  API:: Starting dbaas backup process  
 *************************************************  
 * Backup steps  
  -> API:: Oracle database state is up and running  
  -> API:: DB instance: RCDB121  
  -> API:: Determining if the filesystem is not full  
  -> API:: ...... OK  
  -> API:: Validating the backup repository ......  
 *  
 * RETURN CODE:0  
 ##################################################  
 [root@RAJDB121 opc]# /var/opt/oracle/bkup_api/bkup_api bkup_status  
 DBaaS Backup API V1.5 @2016 Multi-Oracle home  
 DBaaS Backup API V1.5 @2015 Multi-Oracle home  
 -> Action : bkup_status  
 -> logfile: /var/opt/oracle/bkup_api/log/bkup_api.log  
  Warning: unable to get current configuration of: catalog  
 * Current backup settings:  
 * Last registered Bkup: 01-29 16:11 API::1270:: Starting dbaas backup process  
 * Bkup state: finished  
 **************************************************  
 * API History: API steps  
  API:: NEW PROCESS 1270  
  API:: Starting dbaas backup process  
  API:: Your new dbaas backup tag is TAG20180129T161948  
  API:: BKUP COMPLETE YOUR BKUP TAG TAG20180129T161948  
 *************************************************  
 * Backup steps  
  -> API:: Oracle database state is up and running  
  -> API:: DB instance: RCDB121  
  -> API:: Determining if the filesystem is not full  
  -> API:: ...... OK  
  -> API:: Validating the backup repository ......  
  -> API::   All backup pieces are ok  
  -> API:: Performing backup to local storage (primary backup)  
  -> API:: Executing rman instructions  
  -> API:: ...... OK  
  -> API:: Backup to local storage is completed  
  -> API:: Clean MOTD.  
  -> API:: Performing backup to cloud storage (secondary backup)  
  -> API:: Executing rman instructions  
  -> API:: ......OK  
  -> API:: Backup to cloud storage is completed  
  -> API:: Clean MOTD.  
  -> API:: Starting backup of config files  
  -> API:: Executing rman instructions  
  -> API:: at time: 2018-01-29:16:20:40  
  -> API:: Determining the oracle database id  
  -> API:: DBID: 3348210600  
  -> API:: Creating directories to store config files  
  -> API:: Determining the oracle database id  
  -> API:: DBID: 3348210600  
  -> API:: Compressing config files into tar files  
  -> API:: .... OK  
  -> API:: Uploading config files to cloud storage  
  -> API:: Completed at time: 2018-01-29:16:20:58  
  -> API:: at time: 2018-01-29:16:20:58  
  -> API:: Config files backup ended successfully  
  -> API:: Clean MOTD.  
  -> API:: All requested tasks are completed  
 *  
 * RETURN CODE:0  
 ##################################################  
 [root@RAJDB121 opc]#  

Again, you can review the bkup_api log file to check if backup has been succeeded.

 [root@RAJDB121 opc]# tail /var/opt/oracle/bkup_api/log/bkup_api.log  
 Mon, 29 Jan 2018 16:21:06 12eceb08-050f-11e8-a8f6-c6b062e43847@ backups after execution 1908  
 Mon, 29 Jan 2018 16:21:06 12eceb08-050f-11e8-a8f6-c6b062e43847 rman tag TAG20180129T162020  
 Mon, 29 Jan 2018 16:21:06 12eceb08-050f-11e8-a8f6-c6b062e43847 rman tag TAG20180129T162040  
 Mon, 29 Jan 2018 16:21:06 12eceb08-050f-11e8-a8f6-c6b062e43847 rman tag TAG20180129T162033  
 Mon, 29 Jan 2018 16:21:06 12eceb08-050f-11e8-a8f6-c6b062e43847 rman tag TAG20180129T161948  
 Mon, 29 Jan 2018 16:21:07 12eceb08-050f-11e8-a8f6-c6b062e43847 Backup succeded TAG20180129T161948  
 Mon, 29 Jan 2018 16:21:11 DBaaS Backup API V1.5 @2016 Multi-Oracle home  
 Mon, 29 Jan 2018 16:21:11 DBaaS Backup API V1.5 @2015 Multi-Oracle home  
 Mon, 29 Jan 2018 16:21:11 -> Action : bkup_status  
 Mon, 29 Jan 2018 16:21:11 -> logfile: /var/opt/oracle/bkup_api/log/bkup_api.log  
 [root@RAJDB121 opc]#  

Hope you would find it informative........keep reading......

[Oracle Cloud] - Creating SSH Tunnel to Oracle Cloud Compute Node using PuTTY on Windows

Creating SSH Tunnel to Oracle Cloud Compute Node using PuTTY on Windows


In this blog post, I would demonstrate the steps and SSH client configuration details to enable access to Oracle Public Cloud compute node where your Oracle Database Deployment is running.

First of all, you should note down the Oracle Compute Cloud Node's IP for your target database deployment you want to connect to. Go to Oracle Database Cloud Service service page and click on the Database Deployment service name you have created, now on the Database deployment details page, you would find the IP address of its compute node.

Second, you must have the private key saved in .ppk format locally on your client machine that you downloaded while creating the database deployment or the one you might have generated on your own and equivalent to the public key used during database deployment service creation.

• Run the PuTTY SSH client program on your local machine and enter the Public IP address of the compute Node as depicted below. Make sure you have select SSH in the connection Type region of this page.

In category tree at left panel of the page, expand the Connection and click on Data. you would be depicted the following page. In Login Details section, you can enter oracle as a user or leave it blank if you want to enter the username at connection time over PuTTY console. Make sure you have selected "Prompt" radio box under "When username is not specified" section so that it asks for username during the SSH connection request to the compute node.

In category tree at left panel, expand SSH and click on "Auth" , following page appears then.

Click on the Browse button under Private Key file for authentication and select the private key file(.ppk format) which is equivalent to the public key of your target cloud Compute Node.

Now, in category tree at left panel, click on the "Tunnels", following page appears. I am giving here an example of port 22. In the "Add new forwarded Port" enter 22 for "Source Port" and enter the IP Address following port number in the "Destination" box in format "ip-address:port_number and click on Add.

In the Left panel of Category tree, click on the SSH and make sure you have not selected "Don't start a shell or command at all" under Protocal options in case if you are tunneling for port 22, otherwise, you won't get a prompt to enter username and shell to play with compute Node. In case of tunneling for other ports i.e. 1521, 5500, 1158, you can check that box not to start the cell and you can access the applications running on the port.

Now, go back to the "Category" tree and click on the Sessions on the TOP, and save the SSH configuration session setting so that you won't have to do these all shit every time you want to connect to compute node or any application port.

Once you saved the SSH Tunnel configuration setting, click on "Open" button at the bottom to connect to the Compute Node, and there you are at DBAAS compute node box. 

Enter the username you want to connect with, in my case, I am connecting with oracle user.

Now, you can play with dbaascli and all other things on Oracle Public Cloud Compute Node.

Twitter : @rajsoft8899
Linkedin : https://www.linkedin.com/in/raj-kumar-kushwaha-5a289219/

[Oracle Cloud] : START/STOP Oracle DBAAS Cloud Database Instance using dbaascli

STOP/START/RESTART Oracle DBAAS Cloud Database Service Database Instance using dbaascli command line utility.

In this blog post, I will demonstrate the dbaascli database sub-commands to play with oracle database instance that how we stop, start, bounce(here bounce means, your oracle database cloud instance will me stopped with immediate option and then it starts back normally in read-write mode).

You can also change the password of SYS user from the dbaascli command line:


Login to the Oracle cloud compute node using oracle user:

Invoke dbaascli command line utility:

[oracle@RAJDB121 ~]$ dbaascli
DBAAS CLI version 1.0.0
DBAAS>

You can check options of database sub-command of dbaascli command as following:

DBAAS>database -h
Executing command database -h
Valid Subcommands:
   bounce
   stop
   changepassword
   status
   start
DBAAS>

You can check the status of current oracle database cloud service instance:

DBAAS>database status
Executing command database status
Database Status:
Database is open
Database name: RCDB121

Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
PL/SQL Release 12.1.0.2.0 - Production
CORE    12.1.0.2.0      Production
TNS for Linux: Version 12.1.0.2.0 - Production
NLSRTL Version 12.1.0.2.0 - Production


DBAAS>

You can restart/bounce the oracle database cloud service instance using the database bounce command of dbaascli command line utility as below:

bounce option of database sub-command is actually shuts down the oracle database cloud service database instance with immediate option and starts it up normally in read-write mode.

DBAAS>database bounce
Executing command database bounce
Executing command database stop
Database stopped in immediate
Executing command database start
Database started
DBAAS>

You can shutdown the oracle cloud database service database instance using following command, it shuts down the oracle cloud database instance with immediate option.

DBAAS>database stop
Executing command database stop
Database stopped in immediate
DBAAS>

You can start the oracle database cloud service database instance using following command.

DBAAS>database start
Executing command database start
Database started
DBAAS>

Finally, after starting the oracle cloud database service database instance, you can check its status.

DBAAS>database status
Executing command database status
Database Status:
Database is open
Database name: RCDB121

Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
PL/SQL Release 12.1.0.2.0 - Production
CORE    12.1.0.2.0      Production
TNS for Linux: Version 12.1.0.2.0 - Production
NLSRTL Version 12.1.0.2.0 - Production


DBAAS>

[Oracle Cloud] - Creating an Oracle Database Deployment

Creating an Oracle Database Deployment in Oracle Public Cloud:

In this blog post, I will illustrate the steps to deploy an Oracle Database Deployment in Oracle Public Cloud. Assuming you have access to Oracle identity account and have the DBAAS Database Administrator role assigned to your service account to start creating database deployments in Oracle Public Cloud.

After login to the My Services Console, select the “Oracle Database Cloud Service” from the hamburger option just left to the services pages. 

Initially when you don’t have any Database deployments created then you would be shown the page like one depicted below. Here there is no Oracle Database Deployment is created and we will start creating a Oracle Database Deployment now.

Step: 1 – Click on the “Create Service” option in the services region of the “Oracle Database Cloud Service” page

Step : 2 – Once you click on the Create Service option, you will be displayed the following screen where you specify the Service Name, Service Description about the service being created, select Region in which you would like your Oracle Database Deployment to be hosted in.

Select appropriate Software Release and Software Edition and Database Type(there are multiple options to select from Database Type i.e. Single Instance, Database Clustering with RAC, Hybrid DR….)

In this demo article, I am creating a Single Instance database deployment, Oracle Database 12c Release 2 Enterprise Edition Database Deployment.

Choose the option as per your need and click on Next.

Step : 3 – Now you would be moved to the following “Service Details” page to provide your Database Configurations, Backup and Recovery Configuration(In this case, I choose the value “none” for Backup Destination as I don’t want my Oracle Database Deployment to be backed up automatically, There are other options as well to choose from whether you want to backup your Database Deployment to both Cloud Storage and Local Storage or Cloud Storage only).

In the SSH Public Key field, click on the Edit button, Here you would be required to assign one Public key for the database deployment . You will be given three options for Public key here as explained here under.

1 - Choose "Key File Name", if you have already generated the key pairs on your client machine then browse to select the Public key to upload here on Compute Node.

2 - Select the "Key Value" option. Open the public key file in one of the text editor on your client machine and copy the complete public key contents and paste in the right area of this option without any line breaks.

3 -  Choose option "Create a New Key" if you have not already generated the key pairs beforehand. Oracle Database Deployment Create Service wizard provides you flexibility to generate the key pairs here itself. Click on "Enter" then this GUI will generate public/private key pairs for you automatically and give you the option to download the key pairs on your client machine for future use.

Please remember that private key in the downloaded key pair will be used when you connect to the Compute Node using SSH/Putty.

Once you are one with the key pairs work, you can click on the "Advanced Settings" if you would like to change the Listener Port to a none-default port, you can also change Timezone, Database Character Set, Database Deployment National Character Set.

You can check the "Enable Oracle Golden Gate" option if you wish to enable Oracle Golden Gate replication settings, etc.

Click Next.

Step 4 - Now, you will be displayed the summary page of options you have selected for your Oracle database deployment to review once before actually creating the Oracle database deployment, This is the last chance for you to review the configurations selected for your Oracle Database Deployment and go back and change a setting for the database deployment if required, before clicking on "Create Service" tab.

Once you clicked on "Create Service" tab, Oracle database deployment service creation starts now. You would see that status of database deployment is in "Creating service" status now.

You can go and grab a cup of coffee while the service is being created, oh yeah, Oracle doesn't prohibit you from getting one :-)

When Oracle Database Deployment Service Creation starts, then a New Virtual Machine is created for your and one Public IP is assigned to the VM/Compute Node. Oracle Linux is then automatically installed to the Compute Node, Oracle Software gets installed, and Oracle Database instance gets created for you.

In the end, when service creation completes then Oracle database deployment service status changes to "Ready", you can connect to the Compute Node where database deployment is running using the Public IP assigned to your Host name and starts playing with Oracle Database Cloud Service.......

Hope it would help in understanding how we create a Oracle Database Deployment in Oracle Public Cloud.....!!