2521053.1

Exadata Cloud Service Software Version (Doc ID 2333222.1)

Apply batch using dbaascli

How to upgrade DBAAS Cloud Tooling using dbaascli (Doc ID 2350471.1)

Administering Oracle Database Cloud Service ( https://docs.oracle.com/en/cloud/paas/database-dbaas-cloud/csdbi/index.html)
The dbaascli Utility ( https://docs.oracle.com/en/cloud/paas/database-dbaas-cloud/csdbi/dbaascli.html )

#######################################################
https://www.youtube.com/watch?v=SGZZzGr9X5E
#######################################################


============================
as root
============================

- Check the current version of cloud tooling
rpm -qa | grep -i dbasstools

- check for cloud tooling updates
dbbascli patch tools list

- Upgrade to Latest Cloud Tooling
dbbascli patch tools apply -patchid LATEST

- Configure automatic Tooling Updates
dbbascli patch tools auto enable

- Disable automatic Tooling Updates
dbbascli patch tools auto disable


============================
Steps to Apply RDBMS Patch
============================

-- List all available patches
sudo dbaascli patch db list  --oh hostname:/db_home_path_x

-- Check the pre-Req ( Instance wise or DB wise)
sudo dbaascli patch db prereq --patchid nnnnn --instance HOST:/db_home_x
sudo dbaascli patch db prereq --patchid nnnnn --dbnames YYYY

--  apply Patches
sudo dbbascli patch db apply --patchid NNNN -dbnames YYYYY

select * from sys.registry$history order by action_time;


-- Rollback patch
sudo dbaascli patch db switchback --patchid NNN --dbnames YYYY

-- list applied patches

a) for RDBMS
   sudo su - oracle
   run the Env Source File  or     export ORACLE_HOME=??    
   $ORACLE_HOME/OPatch/opatch lspatches


a) for GRID
   
   become a grid user
   su - grid
   $ORACLE_HOME/OPatch/opatch lspatches


========================
patch log location
========================

/var/opt/oracle/log/
/var/opt/oracle/log/exadbcpatchmulti
/var/opt/oracle/log/exadbcpatchsm
/var/opt/oracle/log/exadbcpatcpatch


###########################
Exadata Check
###########################
exachk -loclonly -dball >  <node>_exachk_output.txt