Rolling back using DB console

Rolling backup using DB console

We can scale up/down memory/cpu and storage

Scale/UP or down the compute node

Now scale/up down request has been accepted

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

You also have option to Extend Data Storage volume without creating new volume

Once the extend operations complete,you can see your existing storage mount point will be increase.

[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>

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

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