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

 

Leave a Reply

Your email address will not be published. Required fields are marked *