How to access DBaaS monitor from console

Please open port 443 (https) using “Access Rules”

Please enable oar_p2_httpssl

Now the port ora_p2_httpssl open now

If you do not want to enable port 443 from console,you need to enable port forwarding.

If you enable port forwarding,you need to open using localhost after enable putty session.

When prompted for a user name and password, enter dbaas_monitor as the user name and the password specified during the database deployment creation process, and then click OK

After logging to DBaaS monitor,You can see below

Using Oracle DBaaS Monitor

Oracle DBaaS Monitor provides monitoring and management of the Oracle database and listener on Oracle Database Cloud Service.

Note:

This section does not apply to database deployments that use Oracle Real Application Clusters. Such deployments do not currently include Oracle DBaaS Monitor.

The following are key things you can do using DBAAS Monitor

• Administering the Listener
• Starting and Stopping the Database Instance
• Viewing and Modifying Initialization Parameters
• Viewing User Account and Expiring Password Information
• Viewing Tablespace and Segment Space Usage
• Changing the TDE Keystore Password
• Viewing Alert Log Entries and Checking for Errors
• Viewing Real Time SQL Monitor
• Administering Pluggable Databases.

Oracle DBaaS Monitor provides monitoring and management of the Oracle database and listener on Oracle Database Cloud Service.

DBaaS Monitor provides quick and easy access to a variety of information about the database instance running on a database deployment:

• Overall, how much storage is allocated to tablespaces, and how much of that storage is used.
• For each tablespace, how much storage is allocated and how much of that storage is used, with additional drill-down capabilities to view segments.
• A real-time graph showing wait events across several selectable categories.
• The alert log, with log searching capabilities.
• A list of open user sessions, with drill-down capabilities to view session details such as the last SQL statement, explain plan, waits, contention, and so on.
• A list of initialization parameters, with the ability to change parameter values, both in memory and in the SPFILE.
• Indication of whether certain database options are enabled.
• Monitoring of current and past SQL Developer PDB uploads.
• A list of the SQL statements that are being monitored in the database, with real time display of details such as the status, duration, degree of parallelism, and so on.

You can use DBaaS Monitor to view information about the compute node:

• CPU utilization information in an interactive table format, with automatic refresh intervals
• OS process information, with filtering and automatic refresh capabilities DBaaS Monitor also provides the following management capabilities:
• Start up and shut down the database instance.
• Open and close a pluggable database.
• Create and drop a pluggable database.
• Plug in and unplug a pluggable database.
• Clone a pluggable database.
• Start and stop the listener.

There are various menus by which you can administer Database.

You can check status of listener and turn off if required

You may also stop/start database using this menu of DBaaS monitor

Please keep in my mind following notes when you shutdown database using DBaaS monitor

You can use DBaaS Monitor to shut down the database instance in IMMEDIATE mode. In this mode, no new connections are allowed. No new transactions are allowed to be started and any uncommitted transactions are rolled back.If you need to shut down the database instance in any other mode (ABORT,NORMAL, or TRANSACTIONAL), use SQL*Plus instead of DBaaS Monitor.

Backup and Recovery from DB Console

You may face problem in taking backup to oracle container for oracle cloud RAC. Please follow below link to troubleshoot.

https://clouddba.co/kbhs-00712-ora-29024-received-from-local-http-service-during-backup-in-rac-oracle-cloud/

Once you have resolved the issue,You can proceed with backup

Please proceed to take backup

Backup log location

You can find backup of RMAN log for oracle cloud in following location:-

[oracle@pocracdemo1 ~]$ cd /home/oracle/bkup/logs/rman/

Updating password by using RACCLI utility

1.Connect to the compute node as the opc user.Update the password:

2.$ raccli update backupconfig -params ‘{“cloudStorageUser”:”user-name“,”cloudStoragePwd”:”new-password“}’

where user-name is the user name of the Oracle Cloud user whose credentials are used to access the Storage Cloud Service container and new-password is this user’s new password.

If you have used the update rdk subcommand of the raccli utility to update the cloud tooling to 16.4.5 or later, you must manually update the opc installer for the Oracle Database Cloud Backup Module before you use the update backupconfig subcommand. For instructions, see in Updating the cloud tooling on a deployment hosting Oracle RAC requires manual update of the Oracle Database Cloud Backup Module in Known Issues for Oracle Database Cloud Service.

Customizing with files in RAC needs to be backed up

Customizing Which System Files Are Backed Up

1.Connect as the opc user to the compute node.

2.Edit the contents of the /opt/oracle/dcs/rdbaas/config/oscfg.spec file.

3.The backup feature provided by Oracle Database Cloud Service backs up the files and folders listed in this specification file.

Customizing Which Database Configuration Files Are Backed Up

1.Connect as the opc user to the compute node.

2.Edit the contents of the /opt/oracle/dcs/rdbaas/config/dbcfg.spec file.

3.The backup feature provided by Oracle Database Cloud Service backs up the files and folders listed in this specification file.

Customizing Which Grid Infrastructure Configuration Files Are Backed Up

1.Connect as the opc user to the compute node.

2.Edit the contents of the /opt/oracle/dcs/rdbaas/config/gicfg.spec file.

3.The backup feature provided by Oracle Database Cloud Service backs up the files and folders listed in this specification file.

RACCLI command to update disk recovery window

[opc@pocracdemo1 ~]$ raccli update backupconfig -params '{"diskRecoveryWindow" : 3}'

[opc@pocracdemo1 ~]$ raccli describe job 22

where days is the number of days for which you want to retain backups.

Changing recovery window in cloud storage

[opc@pocracdemo1 ~]$ raccli update backupconfig -params '{"ossRecoveryWindow" : 15}'

where days is the number of days for which you want to retain backups.

Please check now that retention policy got changed.

[oracle@pocracdemo1 ~]$ rman target /

RMAN> show all;

1.Connect as the opc user to the compute node.

2.Enter this raccli command:

     $ raccli update backupconfig -params '{"cronDate" : "time"}'

 where time is the time (using 24-hour, HH:MM format) when daily backups are to occur. For example, "02:45" is 2:45 AM, and "14:45" is 2:45 PM.

Changing backup configuration for RAC cloud storage

1.Connect as the opc user to compute node 1.

2.Use the raccli update backupconfig command to update the configuration.

3.To change the backup destination to Both Cloud Storage and Local Storage, enter the following command. Line breaks have been added for clarity; you must enter the command on a single line.

$ raccli update backupconfig -params '{"diskEnabled" : true, "ossEnabled" : true, 
  "cloudStorageUser" : "username", "cloudStoragePwd" : "password", 
  "cloudStorageContainerUrl" : "container-URL"}'

where:

• username is the user name of an Oracle Cloud user who has read/write access to the container.
• password is the password of the user specified in cloudStorageUser.
• container-URL is the URL of the Oracle Storage Cloud container.

Example:-raccli update backupconfig -params '{"diskEnabled" : true, "ossEnabled" : true, "cloudStorageUser" : "sadhuarun1980@gmail.com", "cloudStoragePwd" : "xxx", "cloudStorageContainerUrl" : "https://sadhuarun.eu.storage.oraclecloud.com/v1/Storage-sadhuarun/racbackup"}'

Restore latest backup in RAC

[opc@pocracdemo1 ~]$ raccli create recovery -latest

[opc@pocracdemo1 ~]$ raccli describe job 24

}

Now once it successfully restore,You can describe the job again

[opc@pocracdemo1 ~]$ raccli describe job 24

}

Restoring to specific point in time using RACCLI

[opc@pocracdemo1 ~]$ raccli create recovery -pitr -timestamp '04/13/2018 08:30:30'

cd /home/oracle/bkup/logs/rman

1.Connect as the opc user to the compute node.

2.Execute the raccli update rdk subcommand:

$ raccli update rdk -tag tag-number

where tag-number is the version of tooling you want to update to, without the dots in the version number. For example, to update to 17.2.5 tooling you would enter 1725.

If you are updating the cloud tooling on a database deployment that also uses Oracle Data Guard, you must also execute the update databasepassword command to store the password in the keystore (wallet) if you are updating from release 17.2.1 or earlier.

or

3.You can update cloud tool for RAC using below command.

Please select create instance after selecting “Database” option

Please select one of following options(I choose custom)

Please select the option to create RAC

Please provide SSH public key or create new key

SSH key will be generated now

Please provide other relevant information

The instance will be now creating and will take 2-3 hours

After installation you will get following screen

RAC characteristics

Database file storage: for each Oracle RAC database, storage for database data files, the fast recovery area, and the redo logs is created and managed using Oracle Automatic Storage Management (ASM) and Oracle Automatic Storage Management Cluster File System (ACFS) instead of Linux LVM.

Included software: Oracle Application Express, Oracle REST Data Services, and Oracle DBaaS Monitor are not currently included.

The following is storage distribution for this installation we carried in previous slide.

1.Recover database from console

2.Please select among below options

3.Please check the recovery progress now

4.Point in time recovery using PITR

[root@MYTST ORCL]#  dbaascli orec –args -list

[root@MYTST ORCL]#  dbaascli orec –args -pitr TAG20180409T051640

OREC:: PITR Completed.

5.Point in time recovery using SCN

# dbaascli orec –args -scn SCN

where SCN is the system change number (SCN) for the end point of the recovery.

The restore and recover process performs these steps:

• Shuts down the database
• Extracts and restores configuration files
• Prepares for recovery
• Performs the recovery
• Restarts the database instance after recovery.

6.In data guard configuration,you need to do following

1.Start a root-user command shell:

2.$ sudo -s
#

3.Run the duplicate option of orec.

4.# dbaascli orec –args -duplicate

5.Exit the root-user command shell and disconnect from the compute node:

6.# exit
$ exit

7.Switching backup from the None destination

8.Configuring TDE wallet and backup configuration file

[opc@MyCLONE ~]$ sudo su –

[root@MyCLONE ~]# /var/opt/oracle/dbaascli/dbaascli tde config –ks_login auto

[root@MyCLONE ~]# cd /var/opt/oracle/ocde/assistants/bkup/

[root@MyCLONE bkup]# ls bkup*.cfg

bkup.cfg

[root@MyCLONE bkup]# mv bkup.cfg bkup_bak.cfg

[root@MyCLONE bkup]# vi bkup.cfg

9.Changing parameter of backup configuration file

# The bkup.cfg file will hold all the config info for BKUP.This configuration for both cloud storage and local disk

For the Cloud Storage Only destination, enter:

# The bkup.cfg file will hold all the config info for BKUP

10.Run the backup assistant with the bkup.cfg file

[root@MyCLONE bkup]# chown root bkup.cfg

[root@MyCLONE bkup]# chmod 0600 bkup.cfg

[root@MyCLONE bkup]# ./bkup -cfg bkup.cfg

1.Please check status on primary

dbaascli dataguard status –details yes

2.Please check status of dataguard in standby

dbaascli dataguard status –details yes

3.Perform Switchover from primary to standby from console

4.Please note primary is standby and standby is now primary

5.Perform switchover from command line to switchover to primary again

Use the password option to supply the SYS user password if you changed it since creating the Data Guard configuration.

dbaascli dataguard switchover

Please restart ords service

[root@MYPRIM-dg02 ~]# /etc/init.d/ords restart

6.You may do failover in case of failure of primary database

Force option can be specified if Dataguard configuration is in warning or error state

Use the force option if the status subcommand shows that the Data Guard configuration is in a warning or error state. Use the password option to supply the SYS user password if you changed it since creating the Data Guard configuration.

Please start ords services

7.You may reinstate the dataguard again to return back normal state

If Flashback Database is enabled on the primary database, it can be reinstated as a standby for the new primary database once the reason for the failure is corrected. A failover is typically used only when the primary database becomes unavailable, and there is no possibility of restoring it to service within a reasonable period of time.

To determine whether the database can be reinstated, use the dataguard status subcommand as described in Checking the Status of the Oracle Data Guard Configuration. A status of ORA-16661: the standby database needs to be reinstated indicates the standby database can be reinstated.

dbaascli dataguard reinstate

8.Please check the dataguard status again

login as: opc

Authenticating with public key “rsa-key-20180316”

[opc@ORCL ~]$ sudo su –

[root@ORCL ~]# /var/opt/oracle/patch/dbpatchmsm -list_ospatches

INFO: non async case

INFO: cmd is: /var/opt/oracle/patch/dbpatchm -list_ospatches

Starting DBPATCHM

Logfile is /var/opt/oracle/log/dbpatchm/dbpatchm_2018-03-28_11:49:32.log

Config file is /var/opt/oracle/patch/dbpatchm.cfg

<json begin>{“available_ospatch”:”yes”,”severity_ospatch”:”Critical”,”packages_list”:””}<json end>

[root@ORCL ~]#  /var/opt/oracle/patch/dbpatchmsm -apply_ospatch_async

INFO: async case

INFO: patch number given is :

<start txn>4<end txn>

INFO: system cmd is: “nohup /var/opt/oracle/patch/dbpatchm -apply_ospatch_async”

[root@ORCL ~]# nohup /var/opt/oracle/patch/dbpatchm -apply_ospatch_async

nohup: ignoring input and appending output to `nohup.out’

[root@ORCL ~]#

[root@ORCL ~]#

Broadcast message from opc@ORCL

(unknown) at 11:57 …

The system is going down for reboot in 1 minute!

Rebooting to finalize the OS security patching.

[root@ORCL ~]#

Broadcast message from opc@ORCL

(unknown) at 11:58 …

The system is going down for reboot NOW!

Rebooting to finalize the OS security patching.

Please select the “Single Instance with Data Guard Standby” as Database Type in drop down.

–> 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 .

Please select standby database as “Disaster Recovery”

Please wait until it finish.You may check status from Details

Please check now both primary and standby databases are ready.