Oracle DBaaS 1z0-160 part 16 :-Attach storage volume to the node from compute classic

The following points need to be considered when you add new storage volume.

A compute node can have a maximum of ten storage volumes attached to it.

You can create a storage volume from 1 GB to 2048 GB in size, in increments of 1 GB.

If the database deployment to which you attach this temporary storage is restarted or is stopped and then started, the storage volume becomes detached from the compute node and you must reattach it.

After reattaching the storage volume, you must then connect to the compute node and remount it.

If the compute node is rebooted, such as when following the instructions in Rebooting a Compute Node , the temporary storage becomes unmounted and you must remount it.

You can attach storage volume to the node from compute classic .You need to select correct site to show instance.

 

Now go to “Storage” tab and select “Create Storage Volume”

Please specify below input to create new stoarge

Now you can attach the storage volume to the instance using below option

Now /dev/xvdi storage volume will be appeared

The screen will explain how you can create partition

Please create file system and mount now

Please change the /etc/fstab entry to mount /u06 automatically after restart

Oracle DBaaS 1z0-160 part 14: Adding temporary storage/Scale up storage

Scale up storage consideration

When creating a database deployment on Oracle Database Cloud Service, you choose the amount of usable data storage you want for your database. You can create a database of up to 1200 GB with backups to both cloud and local storage or up to 2048 GB (2 TB) with backups to cloud storage only or no backups

By adding more storage, you can create much larger databases:

  • In Oracle Cloud Infrastructure Classic, which supports 5 scale-up operations, you can create a database of up to 4.7 TB with backups to both cloud and local storage or up to 10 TB (7.7 TB in Oracle RAC deployments) with backups to cloud storage only or no backups.
  • In Oracle Cloud Infrastructure, which supports 28 scale-up operations, you can create a database of up to 19 TB with backups to both cloud and local storage or up to 48 TB with backups to cloud storage only or no backups. However, if you need databases of such large sizes, you should consider using Oracle Database Exadata Cloud Service instead of Oracle Database Cloud Service.

You may use Scale Up/Down option to increase your storage volume

Please provide how much additional storage you need and select option “Create New Storage Volume”

Now your Scale up/down request accepted

Now please note your instance went is “Service maintenance” mode and storage is increased to 159GB

Please check status from “Activity” tab and refresh to reflect current status.

Please note your new storage mount point has been created as /u05 .This is very simple to add new stoarge.

Oracle DBaaS 1z0-160 part 13:Changing sys/system password in Oracle cloud

[oracle@ORCL admin]$ dbaascli database changepassword

DBAAS CLI version 1.0.0

Executing command database changepassword

Enter username whose password change is required: system

Enter new  password:

Re-enter new password:

Successfully changed the password for user system

[oracle@ORCL admin]$ sqlplus system/Bppimt#123@orcl

SQL*Plus: Release 12.1.0.2.0 Production on Tue Mar 27 12:03:55 2018

Copyright (c) 1982, 2014, Oracle.  All rights reserved.

Last Successful login time: Sun Mar 18 2018 06:06:12 +00:00

Connected to:

Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 – 64bit Production

With the Partitioning, Oracle Label Security, OLAP, Advanced Analytics

and Real Application Testing options

SQL>

Oracle DBaaS 1z0-160 part 12:Clone Oracle cloud database using Snapshot

On database deployments hosting a single-instance database, Oracle Database Cloud Service supports the creation of storage snapshots, which you can then use to create new database deployments called linked clones. When you create a storage snapshot, the database deployment is put into maintenance status and a snapshot of all the storage volumes for the deployment is taken. Then, when you create a linked clone deployment, Database Cloud Service creates a new database deployment whose storage volumes are from the snapshot. Using the “copy on write” technology that Oracle Compute Cloud Service supports for storage volume snapshots, the file data on the linked clone deployment can change without changing the snapshot itself. Thus, you can create several linked clones from the same snapshot to use for application testing or branched application development work.

You cannot delete a snapshot that has linked clone database deployments created from it. You must first delete the linked clone deployments, as described in Deleting a Database Deployment.

First create storage snapshot and provide “snap1” name

Now press “create” to create storage snapshot

You can note that snap1 is created now

Now you can create database clone using “snap1” snapshot

Now you can create instance with this snapshot

Please review all information before create

 

Oracle DBaaS 1z0-160 part 11: Starting and Stopping Oracle Database deployment

What happens when you stop database in Oracle cloud

When you stop a Database Cloud Service database deployment, no access to it is possible and you can perform no management operations on it except to start it or to delete it.

Stopping a database deployment is similar to turning off your personal computer: it has no computing capabilities because the CPU and RAM have no power, but all its other resources—disk drives and the data they contain, static IP reservations, and so on—

remain and are ready to be put back into use when power is restored.

When database deployment is stopped, its CPU and RAM (an Oracle Compute Cloud Service instance) are stopped. As a consequence, it consumes no OCPU or memory resources and so metering and billing of these resources stop. However, all the other

resources of the database deployment continue to exist and so continue to be metered and billed, including:

  • Oracle Compute Cloud Service resources such as storage volumes and IP address reservations
  • Oracle Storage Cloud Service storage space used by the database deployment’s backups to the Oracle Cloud (if the database deployment was being backed up to cloud storage)

Additionally, when database deployment is stopped, backups of it are not performed.

What happens when you start database in oracle cloud

When you start a stopped Database Cloud Service database deployment, access to it becomes possible again and you can perform management operations on it such as scaling and patching.

Starting a stopped database deployment is similar to turning your personal computerback on: its computing capabilities are restored because the CPU and RAM again have power, and all its other resources are put back into use.

When database deployment is started:

1.An Oracle Compute Cloud Service instance of the appropriate compute shape (OCPU and memory) is allocated to it

2.All other Compute Cloud Service resources associated with it when it was created or as the result of a scaling operation are reattached to it.

3.The allocated Oracle Compute Cloud Service instance is started.

After these steps complete, the database deployment is running and available.Because the started database deployment again consumes OCPU and memory resources, metering and billing of these resources resume

The options for start/stop and restart

 

Oracle DBaaS 1z0-160 part 10 :VNC setup to connect directly to Oracle cloud database VM

1.Please install tigervnc-server using yum and create VNC user and password

[root@ORCL ~]# yum install tigervnc-server xorg-x11-fonts-Type1

[root@ORCL ~]# useradd elinuxbook

[root@ORCL ~]# passwd elinuxbook

[root@ORCL ~]# su – elinuxbook

[elinuxbook@ORCL ~]$ vncpasswd

2.Configure display to proper resolution and user “elinuxbook”

[root@ORCL ~]#vi /etc/sysconfig/vncservers

# VNCSERVERS=”2:myusername”

# VNCSERVERARGS[2]=”-geometry 800×600 -nolisten tcp -localhost”

VNCSERVERS=”1:elinuxbook”

VNCSERVERARGS[1]=”-geometry 1440×900″

[root@ORCL ~]# /etc/init.d/vncserver start

Creating default startup script /home/elinuxbook/.vnc/xstartup

Starting applications specified in /home/elinuxbook/.vnc/xstartup

Log file is /home/elinuxbook/.vnc/ORCL:1.log

[  OK  ]

[root@ORCL ~]# chkconfig –level 35 vncserver on

[root@ORCL ~]# chkconfig –list vncserver

vncserver       0:off   1:off   2:off   3:on    4:off   5:on    6:off

3.Now configure the private key in SSH

4.Please select tunnels with port number 5901

5.Now you can connect using localhost with port 5901 from vnc viewer

Oracle DBaaS 1z0-160 part 9:Enabling access to compute node using access rules and directly connect using 1521 to oracle cloud instance

Enabling access to compute node using “access rules”

For database deployments created in Oracle Cloud Infrastructure Classic, Oracle Database Cloud Service uses access rules to provide secure network access to database deployments. You can use the Oracle Database Cloud Service console to perform network access operations such as enabling and disabling access rules and creating new access rules. When a database deployment is created, the following access rules are created, but set to a disabled status

  • ora_p2_dbconsole, which controls access to port 1158, the port used by Enterprise Manager 11g Database Control.
  • ora_p2_dbexpress, which controls access to port 5500, the port used by Enterprise Manager Database Express 12c.
  • ora_p2_dblistener, which controls access to the port used by SQL*Net.
  • ora_p2_http, which controls access to port 80, the port used for HTTP connections.
  • ora_p2_httpssl, which controls access to port 443, the port used for HTTPS connections, including Oracle REST Data Services, Oracle Application Express, and Oracle DBaaS Monitor.Please never touch following access control which is only used by oracle support.

I will now enable access to compute node.Please press button highlighted here

Please select “Access Rules” option

ADDITIONAL ACCESS RULES FOR RAC CONFIGURATION

Please enable port 1521 now.

Now you can directly connect to SQL Developer using port 1521 from your desktop.No need for creating SSH tunnel.

Defining a Custom Host Name or Domain Name for Database Cloud Service

You can associate a custom host name or domain name to the public IP address of a compute node associated with your Oracle Database Cloud Service environment.

To associate a custom host name to the public IP address of a compute node, please contact the administrator of your DNS (Domain Name Service) and request a custom DNS record for the compute node’s public IP address.

For example, if your domain is world.com and you wanted to use clouddba  as the custom host name for a compute node, you would request a DNS record that associates clouddba.world.com  to your compute node’s public IP address.

To associate a custom domain name to the public IP address of a compute node:

  1. Register your domain name through a third-party domain registration vendor, such as Register.com, Namecheap, and so on. For example, example.com.
  2. Resolve your domain name to the IP address of the Database Cloud Service compute node, using the third-party domain registration vendor console. For more information, refer to the third-party domain registration documentation.

Oracle DBaaS 1z0-160 part 8:How to connect your oracle cloud database from 1521 port using sql developer/TOAD

SSH tunneling to access port 1521

This assumes your port 1521 is not open.First you need to Load the putty session you saved in previous case(to enable SSH access).In the Category tree, click Tunnels. The Tunnels panel is displayed.

 

In the Source Port box, enter the number of an available port on your system. Specify a port number greater than 1023 and less than 49152 to avoid conflicts with ports that are reserved for the system. As a good practice, and for the sake of simplicity, you should specify the same port number as the one to which you are creating a tunnel.In the Destination box, enter the IP address of the target compute node, a colon, and the port number to which you want to create a tunnel; for example, 144.21.78.168:1521.

Please note the SID and SERVICE_NAME which will be required to connect to database

Open sql developer and provide below input to connect to PDB.

Please open SQL Developer and create new connection with following entry.Please use password provided during instance creation.Then Test connection.It should show status:Success

Now if you do not enable SSH Tunneling, you will get below error when you connect database using public ip

Oracle DBaaS 1z0-160 part 7:Connecting you Oracle cloud database server using SSH

Please identify public IP

Configure SSH connectivity:

  1. In Host Name (or IP address) box, enter the IP address of the target compute node.
  2. Confirm that the Connection type option is set to SSH.
  3. In the Category tree, expand SSH and then click Auth. The Auth panel is displayed.
  4. Click the Browse button next to the Private key file for authentication box.

Then, in the Select private key file window, navigate to and open the private key file that matches the public key used during the database deployment creation process.

Please provide your saved private key location .You can refer below url where I mentioned how to generate private key.

https://clouddba.co/oracle-dbaas-1z0-160-part-6creating-you-first-single-instance-database-in-oracle-cloud/

Please save this putty session.Now you can login using OPC user.

 

If you forget your private SSH key,You can again regenerate using following link

https://clouddba.co/oracle-dbaas-1z0-160-part-6creating-you-first-single-instance-database-in-oracle-cloud/

Please put public key generated from puttygen and keep private key secret

Please paste the public key generated using putty keygen

Now please modify your private key path in SSH saved connection and you will be able to connect again.