Oracle DBaaS 1z0-160 part 26 :- Install RAC from console in oracle database cloud

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.

Oracle DBaaS 1z0-160 part 25 :- Recover database in oracle database cloud

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

DBAAS CLI version 1.0.0
Executing command orec –args -pitr TAG20180409T051640
–args : -pitr TAG20180409T051640
OREC version: 16.0.0.0
Starting OREC
Logfile is /var/opt/oracle/log/ORCL/orec/orec_2018-04-09_12:39:36.log
Config file is /var/opt/oracle/orec/orec.cfg
DB name: ORCL
OREC:: RUNNING IN NON DATAGUARD ENVIRONMENT
OREC:: Catalog mode:  Disabled
OREC:: Checking prerequirements before recovery process.
OREC:: DB Status : OPEN
OREC:: Changing instance to MOUNT stage.
OREC:: Shutting down the database… Completed.
OREC:: (RMAN) Startup MOUNT… Completed.
OREC:: PITR is within current incarnation 3
INFO : DB instance is up and running after recovery procedure.

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

DBAAS CLI version 1.0.0
Executing command 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

bkup_cfg_files=yes
bkup_disk=yes
bkup_disk_recovery_window=7
bkup_oss=yes
bkup_oss_url=https://surcloudworld.au.storage.oraclecloud.com/v1/Storage-surcloudworld/MYCLONE
bkup_oss_user=rsurajit@rediffmail.com
bkup_oss_passwd=Test#123
bkup_oss_recovery_window=30

For the Cloud Storage Only destination, enter:

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

bkup_cfg_files=yes
bkup_disk=no
bkup_oss=yes
bkup_oss_url=https://surcloudworld.au.storage.oraclecloud.com/v1/Storage-surcloudworld/MYCLONE
bkup_oss_user=rsurajit@rediffmail.com
bkup_oss_passwd=Test#123
bkup_oss_recovery_window=oss-days

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

using file : /var/opt/oracle/log/ORCL/bkup/temp.sh
Configuring Backup to disk
Common RMAN Config
Instantiating obkup
Instantiating dbcfg.spec
Configuring backup of Config File
Updating Control File Record Keep Time
Enabling block change tracking
Updating RMAN defaults
Adding entry to crontab
INFO: Archivelog management enabled.
Adding entry to crontab
Accessing to your Database ID ..
The DBaaS instance database id is: 1500760727

#### Completed Execution.

11.Details about parameters used for backup configuration

1.disk-days is the number of days for which backups and archived redo logs are maintained on local storage. The interval always ends with the current time and extends back in time for the specified number of days.

2.oss-url is the REST endpoint of the cloud storage container.

3.username is the username for accessing the cloud storage container.

4.password is the password for accessing the cloud storage container.

5.oss-days is the number of days for which backups and archived redo logs are maintained on cloud storage. The interval always ends with the current time and extends back in time for the specified number of days.

 12.Create database from existing backup

Please select “create instance from existing backup”

Now you get confirmation screen and proceed further

 

Oracle DBaaS 1z0-160 part 24 :- Backup in single instance oracle cloud

Backup types

When you create a database deployment, you choose one of the following backup destinations:

  • Both Cloud Storage and Local Storage. Backups are configured to be created automatically and stored both on local compute node storage and on an Oracle Storage Cloud Service container.
  • Cloud Storage Only. Backups are configured to be created automatically and stored on an Oracle Storage Cloud Service container.

Note:This choice is not currently available for database deployments that use Oracle Real Application Clusters (Oracle RAC).

  • None. No backup configuration is created.

Identify backup location from storage classic section

Please select “Storage Classic” section from customize dashboard

Please note REST end point

Please open service console after login to cloud account

Create the container

The storage container end point will look as below

https://surcloudworld.au.storage.oraclecloud.com/v1/Storage-surcloudworld/MyRACBKP

Backup configuration

The backup configuration created when you choose a destination other than None follows a set of Oracle best-practice guidelines:

  • Full (level 0) backup of the database followed by rolling incremental (level 1) backups on a seven-day cycle (a 30-day cycle for the Cloud Storage Only destination)
  • Full backup of selected database configuration files.
  • Full backup of selected system files.
  • Automatic backups daily at a time between 11 PM (23:00) and 3 AM (03:00), with the specific time set during the database deployment creation process.

Retention period and Encryption in backup

Retention period:

– Both Cloud Storage and Local Storage: 30 days, with the 7 most recent days’ backups available on local storage

– Cloud Storage Only: 30 days

Encryption:

– Both Cloud Storage and Local Storage: All backups to cloud storage are encrypted; backups of Enterprise Edition databases to local storage are encrypted; backups of Standard Edition databases to local storage are not encrypted.

– Cloud Storage Only: All backups to cloud storage are encrypted.

How to get existing backup configuration

[root@MYTST ~]# /var/opt/oracle/bkup_api/bkup_api get_config_info –all

DBaaS Backup API V1.5 @2016 Multi-Oracle home
DBaaS Backup API V1.5 @2015 Multi-Oracle home
-> Action : get_config_info
-> logfile: /var/opt/oracle/bkup_api/log/bkup_api.log
{
    “bkup_cfg_db_spec”: “dbcfg.spec”,
    “bkup_cfg_files”: “yes”,
    “bkup_cfg_os_spec”: “oscfg.spec”,
    “bkup_cfg_recovery_window”: “30”,
    “bkup_cron_entry”: “yes”,
    “bkup_daily_time”: “2:53”,
    “bkup_disk”: “yes”,
    “bkup_disk_recovery_window”: “7”,
    “bkup_nfs_mount_dir”: “/mnt/dbaas_backup”,
    “bkup_oss”: “yes”,
    “bkup_oss_recovery_window”: “30”,
“bkup_oss_url”: “https://surcloudworld.au.storage.oraclecloud.com/v1/Storage-surcloudworld/MYRACBKP”,
    “bkup_oss_user”: “rsurajit@rediffmail.com”,
    “bkup_rman_retention”: “8”,
    “bkup_script_loc”: “/home/oracle/bkup/ORCL”,
    “bkup_type”: “diskoss”,
    “fra_loc”: “/u03/app/oracle/fast_recovery_area”,
    “opc_oss_url”: “https://surcloudworld.au.storage.oraclecloud.com/v1/Storage-surcloudworld”,
    “oss_base”: “MYRACBKP”,
    “oss_url”: “https://surcloudworld.au.storage.oraclecloud.com/v1/Storage-surcloudworld/MYRACBKP”,
    “oss_user”: “rsurajit@rediffmail.com”

}

Checking latest backup from DB console

Taking ad hoc backup

Make a selection for the Keep Forever option and then click Backup.

The Keep Forever option controls the backup retention policy, as follows:

  • No — specifies that the backup is produced and maintained in accordance with the automatic backup retention policy  that is associated with the database deployment.
  • Yes — specifies that the backup is a long-term backup, which is produced and maintained independently of the automatic backup retention policy that is associated with the database deployment.

Long-term backups remain until you explicitly remove them  from the system.

 

Start backup using command line

[root@MYTST ~]# /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 0a9b991c-3bb6-11e8-a931-021ff53ddc9b for this backup
** process started with PID: 29350
** see log file for monitor progress

————————————-

Mon, 09 Apr 2018 05:28:55 -> logfile: /var/opt/oracle/bkup_api/log/bkup_api.log

Mon, 09 Apr 2018 05:28:55 -> Listing all backups
Mon, 09 Apr 2018 05:28:55   Backup Tag             Completion Date (UTC)            Type          keep
Mon, 09 Apr 2018 05:28:55 ———————-   ———————–      ———–    ——–
Mon, 09 Apr 2018 05:28:55    TAG20180403T025607     04/03/2018 02:56:07       incremental        False
Mon, 09 Apr 2018 05:28:59 API::7238:: Backup list synchronization in background.

Mon, 09 Apr 2018 05:29:08 API::7238:: Backup list synchronization completed.

Backup status check from command line

To create a long-term backup that persists until you delete it, enter the following bkup_api command:

# /var/opt/oracle/bkup_api/bkup_api bkup_start –keep

[root@MYTST ~]# /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: 04-09 05:23 API::29350:: Starting dbaas backup process

* Bkup state: finished

**************************************************

Listing all backup

 [root@MYTST ~]#  /var/opt/oracle/bkup_api/bkup_api list –keep

DBaaS Backup API V1.5 @2016 Multi-Oracle home
DBaaS Backup API V1.5 @2015 Multi-Oracle home
-> Action : list
-> logfile: /var/opt/oracle/bkup_api/log/bkup_api.log
-> Listing all backups
  Backup Tag             Completion Date (UTC)            Type          keep
———————-   ———————–      ———–    ——–

[root@MYTST ~]#  /var/opt/oracle/bkup_api/bkup_api list

DBaaS Backup API V1.5 @2016 Multi-Oracle home
DBaaS Backup API V1.5 @2015 Multi-Oracle home
-> Action : list
-> logfile: /var/opt/oracle/bkup_api/log/bkup_api.log
-> Listing all backups
  Backup Tag             Completion Date (UTC)            Type          keep
———————-   ———————–      ———–    ——–
   TAG20180409T051640     04/09/2018 05:16:40       incremental        False
   TAG20180409T052528     04/09/2018 05:25:28       incremental        False

Delete backup with tag

[root@MYTST ~]# /var/opt/oracle/bkup_api/bkup_api bkup_delete –bkup=TAG20180409T051640

DBaaS Backup API V1.5 @2016 Multi-Oracle home
DBaaS Backup API V1.5 @2015 Multi-Oracle home
-> Action : bkup_delete
-> logfile: /var/opt/oracle/bkup_api/log/bkup_api.log
UUID 841a5e78-3bdd-11e8-bc4d-021ff53ddc9b for delete backup
Notes:
 *)  Only keep forever backups can be deleted
 *)  Regular backups are part of the retention policy
 *)  Regular backups are hot and incremental and they share their backup pieces
-> Verifying if the specified backup is a keep forever backup
Starting delete of backup
841a5e78-3bdd-11e8-bc4d-021ff53ddc9b command /var/opt/oracle/ocde/assistants/bkup/obkup -keep -delete=TAG20180409T051640
841a5e78-3bdd-11e8-bc4d-021ff53ddc9b The delete process failed
*
* RETURN CODE:1
##################################################

Updating the Password by Using the bkup_api Utility

You use the bkup_api utility to update the Oracle Wallet file containing the backup user’s password:

  1. Connect to the compute node as the opc user.
  2. Start a root-user command shell: $ sudo -s
  3. Create a file that contains the updated password. The file must contain only the following entry: password=new-password (where new-password is the backup user’s updated password).

Also, the file permissions must be set as follows:

# chmod 600 password-file (where password-file is the name of the file that contains the updated password.)

  1. Update the password. # /var/opt/oracle/bkup_api/bkup_api update_wallet –cfg=password-file where password-file is the name of the file that contains the updated password.

Checking retention period of backup and changing it.

RMAN> show all;
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 30 DAYS;
#/var/opt/oracle/bkup_api/bkup_api bkup_chgcfg –retention=15
INFO: Backups that are older than 15 days will be deleted during next bkup.
* Update
INFO: Updating the policy with the following parameters:
 -> Backup policy : 15 days (rman retention period)
 -> Backup cycle  : 8 days (obkup retention period)
INFO: Update RMAN retention policy:
 -> configure retention policy to recovery window of 30 days;
 -> New value: 15 days
INFO: Update bkup_oss_recovery_window:
 -> Old value: 30 days
 -> New value: 15 days
I* RETURN CODE: 0

Customizing which system files are backed up

 Login to oracle user and Edit the contents of the /home/oracle/bkup/ORCL/oscfg.spec file. The backup feature provided by Oracle Database Cloud Service backs up the files and folders listed in this specification file. An example of an oscfg.spec file with a default configuration is as follows:

# Directories

/etc/rc.d
/home/oracle/bkup

# Single files

/home/oracle/.bashrc
/etc/crontab
/etc/sysctl.conf
/etc/passwd
/etc/group
/etc/oraInst.loc
/etc/oratab
/etc/fstab

Customizing Which Database Configuration Files Are Backed Up

 Please edit /home/oracle/bkup/ORCL/dbcfg.spec using oracle user

# Directories

/u01/app/oracle/product/12.1.0/dbhome_1/admin/ORCL/xdb_wallet
/u01/app/oracle/admin/ORCL/xdb_wallet
/u01/app/oracle/admin/ORCL/db_wallet

# Note: tde_wallet must be backed up in a different location than DATA bkup.

/u01/app/oracle/admin/ORCL/tde_wallet
/u01/app/oracle/admin/ORCL/cat_wallet

# Single files

/u01/app/oracle/admin/ORCL/opcORCL.ora
/u01/app/oracle/product/12.1.0/dbhome_1/dbs/opcORCL.ora
/u01/app/oracle/product/12.1.0/dbhome_1/dbs/orapwORCL
/u01/app/oracle/product/12.1.0/dbhome_1/network/admin/listener.ora
/u01/app/oracle/product/12.1.0/dbhome_1/network/admin/sqlnet.ora
/u01/app/oracle/product/12.1.0/dbhome_1/network/admin/tnsnames.ora
/u01/app/oracle/product/12.1.0/dbhome_1/rdbms/lib/env_rdbms.mk
/u01/app/oracle/product/12.1.0/dbhome_1/rdbms/lib/ins_rdbms.mk

# Creg

/var/opt/oracle/creg/ORCL.ini

The backup feature provided uses the Linux cron job scheduler to perform automatic backups

[root@MYTST ORCL]# cat /etc/crontab

SHELL=/bin/bash
PATH=/sbin:/bin:/usr/sbin:/usr/bin
MAILTO=””
HOME=/

# For details see man 4 crontabs

# Example of job definition:

# .—————- minute (0 – 59)

# |  .————- hour (0 – 23)

# |  |  .———- day of month (1 – 31)

# |  |  |  .——- month (1 – 12) OR jan,feb,mar,apr …

# |  |  |  |  .—- day of week (0 – 6) (Sunday=0 or 7) OR sun,mon,tue,wed,thu,fri,sat

# |  |  |  |  |

# *  *  *  *  * user-name command to be executed

15 03 * * 6 oracle /var/opt/oracle/cleandb/cleandblogs.pl
53 2 * * * root /var/opt/oracle/bkup_api/bkup_api bkup_start –dbname=ORCL
0,30 * * * * root /var/opt/oracle/bkup_api/bkup_api bkup_archlogs –dbname=ORCL

Disabling and Enabling automatic backup

If some activity you want to perform requires you to temporarily disable regularly scheduled backups of a database deployment, you can do so by removing the scheduling information from the system-wide /etc/crontab file.

Currently, disabling and re-enabling scheduled backups is not supported for Database Cloud Service database deployments that use Oracle Real Application Clusters (RAC).

  1. Start a root-user command shell: $ sudo -s #
  2. Navigate to the /etc directory, which contains the system-wide crontab file: # cd /etc.
  1. Make a copy of the crontab file to preserve the configuration, for example: # cp crontab crontab.bak.
  2. Edit the original crontab file and remove the lines related to backup from the file.

To re-enable automatic backup , Copy the crontab.bak file you created when disabling scheduled backups to its original name,

# cp /etc/crontab.bak /etc/crontab

Oracle DBaaS 1z0-160 part 23 :- Dataguard Administration in oracle cloud

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

INFO: Stopping Oracle REST Data Services…
INFO: Oracle REST Data Services stopped
INFO: Starting Oracle REST Data Services…
INFO: Oracle REST Data Services bound to ports 8080 27834
INFO: Oracle REST Data Services started with PID 27834

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

dbaascli dataguard failover

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

Oracle DBaaS 1z0-160 part 22 :- OS Patching in oracle cloud

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.

Oracle DBaaS 1z0-160 part 21 :- Patching in dataguard oracle cloud

Please check pre-requisites first

You need to run the following command to check latest available patch

dbaascli dbpatchm –run -list patches

You may patch to be applied from dataguard side as well

Please go to database console and check the Administration section

Please run the prereq now for checking all pre-requisites already applied and check log as in screenshot

Precheck failed for patch [26609783-SE]. Error [please upgrade to recommended dbaastools version… (Doc ID 2367349.1)

You will be able to successfully complete pre-check

[root@TestDB-dg02 ~]#  rpm -qa|grep -i dbaastools

Dbaastools-1.0-1+18.1.4.1.0_180312.1800.x86_64

Please start patching now

Please select “Switchover” option to minimize downtime

You may check patch progress status

Now you have successfully applied the patches

Oracle DBaaS 1z0-160 part 20 :- Dataguard Setup for Single Instance in oracle cloud

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.

 

Oracle DBaaS 1z0-160 part 18:- Patching single instance in oracle cloud

Patching from DB console

1.Please select highlighted option for checking availability patches using DB Console

2.Please check using “Precheck” option

3.PreCheck result may fail due to below errors

4.Upgrade the DBPATCHM version from server to make precheck successful

[root@ORCL dbpatchm]# rpm -qa|grep -i dbaastools

dbaastools-1.0-1+18.1.4.0.0_180123.1336.x86_64

[root@ORCL dbpatchm]# dbaascli dbpatchm –run -list_tools -cli

DBAAS CLI version 1.0.0
Executing command dbpatchm –run -list_tools -cli -cli
/var/opt/oracle/patch/dbpatchm -list_tools -cli -cli
Starting DBPATCHM
Logfile is /var/opt/oracle/log/dbpatchm/dbpatchm_2018-03-19_03:26:16.log
Config file is /var/opt/oracle/patch/dbpatchm.cfg
INFO: patching type : psu
Patchid : 18.1.4.1.0_180309.0546
Patchid : 18.1.4.1.0_180312.1800
dbpatchm Execution completed

[root@ORCL dbpatchm]# dbaascli dbpatchm –run -toolsinst -rpmversion=18.1.4.1.0_180312.1800

DBAAS CLI version 1.0.0

Executing command dbpatchm –run -toolsinst -rpmversion=18.1.4.1.0_180312.1800 -cli
/var/opt/oracle/patch/dbpatchm -toolsinst -rpmversion=18.1.4.1.0_180312.1800 -cli
where patch-id is the patch ID you located earlier.
Note: if you get a warning message indicating that the toolsinst parameter is invalid, you can ignore the message.

[root@ORCL dbpatchm]# rpm -qa|grep -i dbaastools

Dbaastools-1.0-1+18.1.4.1.0_180312.1800.x86_64

5.Now run Precheck again and it will show successful now

6.Now you are ready for starting actual patching

7.Proceed for patching

If you want errors to be ignored during the patching operation, select the Force apply patch option. Then, click Patch.

If the Force apply patch option is selected, patch conflicts or errors discovered during the precheck stage of the patching operation are ignored and the patch will be applied (space permitting). If the option is not selected and conflicts or errors are discovered, the patch will not be applied.

 

8.Please check status of patch apply progress from “Activity” tab.

9.You may check the log file while instance being patched

[root@MYTST dbpatchm]# pwd

/var/opt/oracle/log/dbpatchm

[root@MYTST dbpatchm]# tail -100f dbpatchm_2018-04-03_03:39:26.log

inflating: 26925311/26713565/files/lib/libserver12.a/ktsp.o

inflating: 26925311/26713565/files/lib/libserver12.a/kkpo.o

inflating: 26925311/26713565/files/lib/libserver12.a/kjp.o

creating: 26925311/26713565/files/lib/libasmclntsh12.a/

10.Please check the final status after patching

Patching manually from server command line.

1.Please check available patches

[root@MYTST ~]# dbaascli dbpatchm –run -list_patches

DBAAS CLI version 1.0.0

Executing command dbpatchm –run -list_patches -cli

/var/opt/oracle/patch/dbpatchm -list_patches -cli

Starting DBPATCHM

Logfile is /var/opt/oracle/log/dbpatchm/dbpatchm_2018-04-06_11:06:52.log

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

INFO: cdb is set to : yes

INFO: dbversion detected : 12102

INFO: patching type : psu

12.1.0.2.171017, ee

Available patches :26925311-EE

2.Please change the PSU number to 26925311-EE in below configuration file.

[root@MYTST ~]# vi /var/opt/oracle/patch/dbpatchm.cfg

[root@MYTST ~]# dbaascli dbpatchm –run -apply

DBAAS CLI version 1.0.0

Executing command dbpatchm –run -apply -cli

/var/opt/oracle/patch/dbpatchm -apply -cli

3.The dbpatchm.cfg Configuration File

To perform a patching operation, the dbpatchm subcommand reads and acts on the content of the /var/opt/oracle/patch/dbpatchm.cfg patching configuration file. This file, which is created when the database deployment is created, provides information about the locations of various files that may be used in patching operations.

Before using dbpatchm to perform a patching operation, set the value of the psunum key in the dbpatchm.cfg file to the patch ID of the patch to apply.

The dbpatchm.cfg file contains additional keys you can edit to customize the patching  operation, and comment lines describing the purpose of each key and how to set its value