Atualizando (Patch) Server, Storage e Database em Oracle Database Appliance (ODA) X5-2 High Availability (HA)

Por Y. V. Ravi Kumar , Rodrigo Mufalani Oracle ACE e Shireesha Baddam (ODA Expert, OCP)
Publicado en Junio 2017


Revisado por Marcelo Pivovar

Introdução

O ODA patch bundle 12.1.2.10.0 inclui grid infrastructure, database e patches de outros componentes como ILOM, BIOS, firmware de Controladoras e disco. A interface de linha de comando OAKCLI (Oracle Appliance Kit Command Line Interface), é usada para aplicar esses pathes no ODA. Os componentes de Server e database são atualizados (patch) no ODA podem ser aplicados em node por node usando a opção –local ou rolling fashion.

Níveis e ordem dos Patches:

  • Server Patch
    $ oakcli update -patch 12.1.2.10.0 --server <--local>
  • Storage Patch
    $ oakcli update -patch 12.1.2.10.0 --storage
  • Database Patch
    $ oakcli update -patch 12.1.2.10.0 --database <--local>

Ambiente:

ODA Model:          BM Oracle Database Appliance (ODA) X5-2
Public interface:   COPPER
ODA Version:        12.1.2.9.0
Operating system:   Linux version 2.6 (Red Hat 4.4.7-16)
Databases:          Oracle Database 11g R2 (11.2.0.4.0)
                    Oracle Database 12c R1 (12.1.0.2.0)
Hostnames:          DBServer01, DBServer02

01

Pré-requisitos:

O Patch 12.1.2.10.0 pode ser aplicado em um ODA rodando a versão 12.1.2.6.0 ou superior.

Confira os espaço disponível nos seguintes diretórios e tenha certeza que possui espaço suficiente.

  • /u01
  • /tmp
  • /boot

Aplicando o patch 12.1.2.10.0

1. Faça o download do bundle patch do Oracle support. O patch bundle contém 2 arquivos zip.

  • p25499210_1212100_Linux-x86-64_1of2.zip
  • p25499210_1212100_Linux-x86-64_2of2.zip

Copie os arquivos do patch para todos os nodes do ODA para o /tmp ou qualquer outro diretório que desejar.

2. Logue-se em cada node como root e execute o comando unpack –package no patch bundle em ambos os nodes.

Logon no DBServer01

[root@dbserver01: Wed Apr 05, 03:52 PM : /tmp/patches/ODA ]
$ /opt/oracle/oak/bin/oakcli unpack -package 
/tmp/patches/ODA /p25499210_1212100_Linux-x86-64_1of2.zip

Unpacking will take some time,  Please wait...
Successfully unpacked the files to repository.
 [ root@dbserver01 : Wed Apr 05, 03:55 PM : /tmp/patches/ODA ]
$ /opt/oracle/oak/bin/oakcli unpack -package 
/tmp/patches/ODA /p25499210_1212100_Linux-x86-64_2of2.zip
 
Unpacking will take some time,  Please wait...
Successfully unpacked the files to repository.
[ root@dbserver01: Wed Apr 05, 03:56 PM : 
/tmp/patches/ODA ]
 
Logon no DBServer02
[root@dbserver02 : Wed Apr 05, 03:58 PM : /root ]
$ /opt/oracle/oak/bin/oakcli unpack -package 
/tmp/patches/ODA /p25499210_1212100_Linux-x86-64_1of2.zip
 
Unpacking will take some time,  Please wait...
Successfully unpacked the files to repository.
[ root@dbserver02 : Wed Apr 05, 03:58 PM : /root ]
$ /opt/oracle/oak/bin/oakcli unpack -package 
/tmp/patches/ODA /p25499210_1212100_Linux-x86-64_2of2.zip
 
Unpacking will take some time,  Please wait...
Successfully unpacked the files to repository.
3.  Em cada um dos nodes verifique se os componentes 
foram atualizados usando o a opção --verify.
$ /opt/oracle/oak/bin/oakcli update -patch  12.1.2.10.0 –verify

 
INFO: 2017-04-05 18:52:25: Reading the metadata file now...

Component Name            	Installed Version         	Proposed Patch Version
-------------------       	------------------          -----------------------
Controller_INT            	4.230.40-3739             	Up-to-date
Controller_EXT            	09.00.00.00               	10.00.00.00
Expander                  	0018                      	Up-to-date
SSD_SHARED {
[ c2d20,c2d21,c2d22,      	A29A                      	Up-to-date
c2d23,c2d44,c2d45,c2
d46,c2d47 ]
[ c2d16,c2d17,c2d18,      	A29A                      	Up-to-date
c2d19,c2d40,c2d41,c2
d42,c2d43 ]
}
HDD_LOCAL                 	A72A                      	Up-to-date
HDD_SHARED {
[ c2d24,c2d25,c2d26,      	P9E2                      	PAG1
c2d27,c2d28,c2d29,c2
d30,c2d31,c2d32,c2d3
3,c2d34,c2d35,c2d36,
c2d37,c2d38,c2d39 ]
[ c2d0,c2d1,c2d2,c2d      	A3A0                      	Up-to-date
3,c2d4,c2d5,c2d6,c2d
7,c2d8,c2d9,c2d10,c2
d11,c2d12,c2d13,c2d1
4,c2d15 ]
}
ILOM                      	3.2.7.26.a r112579        	3.2.8.24 r114580
BIOS                      	30090200                  	30100400
IPMI                      	1.8.12.4                  	Up-to-date
HMP                       	2.3.5.2.5                 	2.3.5.2.8
OAK                       	12.1.2.9.0                	12.1.2.10.0
OL                        	6.8                       	Up-to-date
GI_HOME                   	12.1.0.2.161018(2400        12.1.0.2.170117(2473
6101,23854735)            	2082,24828633)
DB_HOME {
[ OraDb11204_home1 ]      	11.2.0.4.161018(2400        Up-to-date
6111,23054319)
[ OraDb12102_home1 ]      	12.1.0.2.161018(2400        12.1.0.2.170117(2473
6101,23854735)              2082,24828633)
}
ASR                       	5.5.1                     	Up-to-date

4. Aplique o patch nos Server Components.

Execute o commando abaixo para atualizar os Server Components. A opção ’-local’ pode ser usada para fazer a aplicação nos nodes separadamente. Se a opção ‘-local’ não for utilizada, ambos os nodes serão atualizados.

$ oakcli update -patch  12.1.2.10.0 –server <-local>
 
[ root@dbserver01 : Wed Apr 05, 07:28 PM :/tmp/patches/ODA ]
$ oakcli update -patch  12.1.2.10.0 --server
 
****************************************************************************
*****                                                                  	
*****   For all X5-2 customers with 8TB disks, please make sure to      
*****   run storage patch ASAP to update the disk firmware to "PAG1".  	
*****                                                                  	
****************************************************************************
 
INFO: DB, ASM, Clusterware may be stopped during the patch if required
INFO: Both Nodes may get rebooted automatically during the patch if required
Do you want to continue: [Y/N]?: Y
INFO: User has confirmed for the reboot
INFO: Patch bundle must be unpacked on the second Node also before applying the patch
Did you unpack the patch bundle on the second Node? : [Y/N]? : Y
INFO: Running pre-install scripts
INFO: Running  prepatching on node 0
INFO: Running  prepatching on node 1
INFO: Completed pre-install scripts
INFO: Patching server component (rolling)
...
INFO: Patching the server on node: dbserver02
INFO: it may take upto 60 minutes. Please wait
INFO: Running postpatch on node dbserver02...
 
INFO: Infrastructure patching summary on node: dbserver01
 
INFO: Infrastructure patching summary on node: dbserver02
SUCCESS: 2017-04-05 20:21:15:  Successfully upgraded the HMP
SUCCESS: 2017-04-05 20:21:15:  Successfully updated the OAK
SUCCESS: 2017-04-05 20:21:15:  Successfully updated the JDK
INFO: 2017-04-05 20:21:15:  IPMI is already upgraded
SUCCESS: 2017-04-05 20:21:15:  Successfully upgraded the OS
SUCCESS: 2017-04-05 20:21:15:  Successfully updated the ILOM & BIOS
INFO: 2017-04-05 20:21:15:  Storage patching summary
SUCCESS: 2017-04-05 20:21:15:  There are no failures found during 
Storage upgrade
SUCCESS: 2017-04-05 20:21:15:  Successfully applied the patch on the 
Home /u01/app/12.1.0.2/grid
 
INFO: 2017-04-05 20:21:15: Some of the components patched on node 

INFO: 2017-04-05 20:21:15: require node reboot. Rebooting the node
INFO: 2017-04-05 20:21:16: rebooting dbserver02 via /tmp/ pending_actions.......
INFO: 2017-04-05 20:26:46: dbserver02 is rebooting...
INFO: 2017-04-05 20:26:46: Waiting for dbserver02 to reboot... .........
INFO: 2017-04-05 20:34:46: dbserver02 has rebooted...
INFO: 2017-04-05 20:34:46: Waiting for processes on dbserver02 to start... ..
INFO: Patching server component on node: dbserver01
INFO: 2017-04-05 20:36:50: Patching Server Components (including Grid software)
INFO: 2017-04-05 20:36:51: -----------Patching HMP-------------
SUCCESS: 2017-04-05 20:37:01: Successfully upgraded the HMP
INFO: 2017-04-05 20:37:02: /usr/lib64/sun-ssm already exists.
INFO: 2017-04-05 20:37:02: ----------Patching OAK-------------
SUCCESS: 2017-04-05 20:37:35: Successfully upgraded OAK INFO: 2017-04-05 20:37:39: ----------
Patching JDK------------- SUCCESS: 2017-04-05 20:37:44: Successfully upgraded JDK
INFO: 2017-04-05 20:37:45: ----------Patching IPMI------------
INFO: 2017-04-05 20:37:45: IPMI is already upgraded or running with the latest version
INFO: 2017-04-05 20:37:45: ----------Patching OS--------------
INFO: 2017-04-05 20:37:57: Clusterware is running on local node
INFO: 2017-04-05 20:37:57: Attempting to stop clusterware and its resources locally
SUCCESS: 2017-04-05 20:41:11: Successfully stopped the clusterware on local node
INFO: 2017-04-05 20:41:53: Trying to recreate /boot/ initramfs-2.6.39-400.290.1.el6uek.x86_64.img
INFO: 2017-04-05 20:42:24: Successfully recreated / boot/initramfs-2.6.39-400.290.1.el6uek.x86_64.img
SUCCESS: 2017-04-05 20:42:26: Successfully upgraded the OS
INFO: 2017-04-05 20:42:26: -----------Patching ASR-------------
INFO: 2017-04-05 20:42:26: ASR is already upgraded or running with the latest version
INFO: 2017-04-05 20:42:29: -----------Patching ILOM & BIOS -----
INFO: 2017-04-05 20:42:29: Updating the ILOM using LAN over USB
INFO: 2017-04-05 20:42:32: Enabling Interconnect... INFO: 2017-04-05 20:43:00: Getting the SP IP address...
INFO: 2017-04-05 20:43:08: Updating the ILOM. It takes a while...
INFO: 2017-04-05 20:59:14: Verifying the updated ILOM Version.
It may take a while if the Service Processor is booting...
INFO: 2017-04-05 20:59:16: Waiting for the Service Processor to be up and running
INFO: 2017-04-05 21:03:53: Disabling Interconnect...
SUCCESS: 2017-04-05 21:05:41: Successfully updated the ILOM with the firmware version 3.2.8.24 r114580
INFO: 2017-04-05 21:06:00: ----------Patching Storage-----------
INFO: 2017-04-05 21:06:00: .......... Patching Local HDDs........
INFO: 2017-04-05 21:06:00: Disk : c0d0 is already running with : H109060SESUN600G A72A
INFO: 2017-04-05 21:06:00: Disk : c0d1 is already running with : H109060SESUN600G A72A
INFO: 2017-04-05 21:06:00: .........Patching Local Controllers...
INFO: 2017-04-05 21:06:00: No-update for the Controller: c0
INFO: 2017-04-05 21:06:00: --------Completed Storage Patching----
INFO: 2017-04-05 21:06:00: --------Patching Grid-----------------
INFO: 2017-04-05 21:06:03: Checking for available free space on /, /tmp, /u01
INFO: 2017-04-05 21:06:03: Shutting down Clusterware and CRS on local node.
INFO: 2017-04-05 21:06:03: Shutting down CRS on the node...
SUCCESS:2017-04-05 21:06:05: Successfully stopped CRS processes on the node
INFO: 2017-04-05 21:06:05: Checking for running CRS processes on the node.
INFO: 2017-04-05 21:06:06: Starting up CRS and Clusterware on the node
INFO: 2017-04-05 21:06:06: Starting up CRS on the node...
SUCCESS: 2017-04-05 21:07:47: CRS has started on the node
INFO: 2017-04-05 21:07:51: Patching the GRID Home on the local node...
INFO: 2017-04-05 21:07:51: Updating OPATCH... Verifying Opatch version
for home: on local node. Expecting version:<12.2.0.1.8>
Opatch version on local node is <12.2.0.1.8>
INFO: 2017-04-05 21:07:55: Patching the GRID Home on the local Node...
INFO: 2017-04-05 21:07:55: Performing local patching...
INFO: 2017-04-05 21:09:10: Performing the conflict checks...
SUCCESS: 2017-04-05 21:09:27: Conflict checks passed for all the Homes
INFO: 2017-04-05 21:09:27: Checking if the patch is already applied to the GRID homes
INFO: 2017-04-05 21:09:39: Home is not Up-to-date
SUCCESS: 2017-04-05 21:15:13: Successfully stopped the Database consoles
SUCCESS: 2017-04-05 21:15:44: Successfully stopped the EM agents
WARNING: 2017-04-05 21:15:49: A stale EM agent with 42850 is running. Trying to kill it...
INFO: 2017-04-05 21:15:49: Applying patch on /u01/app/12.1.0.2/ grid Homes
INFO: 2017-04-05 21:15:49: It may take upto 15 mins. Please wait...
SUCCESS: 2017-04-05 21:28:12: Successfully applied the patch on the Home : /u01/app/12.1.0.2/grid
SUCCESS: 2017-04-05 21:28:25: Successfully started the Database consoles
SUCCESS: 2017-04-05 21:29:02: Successfully started the EM Agents
INFO: 2017-04-05 21:29:04: ASM is running in Flex mode
INFO: Infrastructure patching summary on node: dbserver01
SUCCESS: 2017-04-05 21:29:04: Successfully upgraded the HMP
SUCCESS: 2017-04-05 21:29:04: Successfully updated the OAK
SUCCESS: 2017-04-05 21:29:04: Successfully updated the JDK
INFO: 2017-04-05 21:29:04: IPMI is already upgraded
SUCCESS: 2017-04-05 21:29:04: Successfully upgraded the OS
INFO: 2017-04-05 21:29:04: ASR is already upgraded or running with the latest version
SUCCESS: 2017-04-05 21:29:04: Successfully updated the ILOM &
BIOS INFO: 2017-04-05 21:29:04:Storage patching summary
SUCCESS: 2017-04-05 21:29:04: There are no failures found during Storage upgrade
SUCCESS: 2017-04-05 21:29:04: Successfully applied the patch on the Home
/u01/app/12.1.0.2/grid INFO: Infrastructure patching summary on node: dbserver02
SUCCESS: 2017-04-05 21:29:04: Successfully upgraded the HMP
SUCCESS: 2017-04-05 21:29:04: Successfully updated the OAK
SUCCESS: 2017-04-05 21:29:04: Successfully updated the JDK
INFO: 2017-04-05 21:29:04: IPMI is already upgraded
SUCCESS: 2017-04-05 21:29:04: Successfully upgraded the OS
SUCCESS: 2017-04-05 21:29:04: Successfully updated the ILOM & BIOS
INFO: 2017-04-05 21:29:04: Storage patching summary
SUCCESS: 2017-04-05 21:29:04: There are no failures found during Storage upgrade
SUCCESS: 2017-04-05 21:29:04: Successfully applied the patch on the Home /u01/app/12.1.0.2/grid
INFO: Running post-install scripts INFO: Skipping postpatch on node 1..
INFO: Running postpatch on node 0... ... ...
INFO: Started Oakd
INFO: 2017-04-05 21:30:26: Some of the components patched on node
INFO: 2017-04-05 21:30:26: require node reboot. Rebooting the node
INFO: Node will reboot now. INFO: Please check reboot progress via ILOM interface
INFO: This session may appear to hang, press ENTER after reboot
INFO: 2017-04-05 21:30:26: Rebooting node 0
INFO: Running /tmp/pending_actions on node 0 More robust algorithm supported. Chassis Power Control: Down/Off
Nota: A máquina irá reiniciar depois do patch ser aplicado. Verifique se todos os serviços
do Grid infrastructure estão online depois que a máquina ligar novamente. $crsctl check crs CRS-4638:
Oracle High Availability Services is online CRS-4537: Cluster Ready Services is online CRS-4529:
Cluster Synchronization Services is online CRS-4533: Event Manager is online

5. Aplique o patch no Storage.

Depois que o server patch foi aplicado com sucesso, aplique o storage patch. Não há uma opção <-local> para atualiza o storage. O node1 é atualizado primeiro e então o node2 é atualizado. Execute o comando abaixo para realizar a atualização no Storage.

$ oakcli update -patch  12.1.2.10.0 –storage
 
 [ root@dbserver01 : Wed Apr 05, 09:47 PM : /tmp/patches/ODA ]
$ oakcli update -patch  12.1.2.10.0 --storage
INFO: DB, ASM, Clusterware may be stopped during the patch if required
INFO: Both Nodes may get rebooted automatically during the patch if required
Do you want to continue: [Y/N]?: Y
INFO: User has confirmed for the reboot
INFO: Running pre-install scripts
INFO: Running  prepatching on node 0
INFO: Running  prepatching on node 1
INFO: Completed pre-install scripts
INFO: Shared Storage components need to be patched
INFO: Stopping OAKD on both nodes...
INFO: Stopped Oakd
INFO: Attempting to shutdown clusterware (if required)..
INFO: 2017-04-05 21:49:23: Clusterware is running on one or more nodes of the cluster
INFO: 2017-04-05 21:49:23: Attempting to stop clusterware and its resources across the cluster
SUCCESS: 2017-04-05 21:50:05: Successfully stopped the clusterware
 
INFO: Patching storage on node dbserver02
INFO: Patching storage on node dbserver01
 
INFO: 2017-04-05 22:13:02: ----------------Patching Storage-------------------
INFO: 2017-04-05 22:13:02: ....................Patching SSDs...............
INFO: 2017-04-05 22:13:02: Disk : d16  is already running with : HSCAC2DA4SUN400G A29A
INFO: 2017-04-05 22:13:02: Disk : d17  is already running with : HSCAC2DA4SUN400G A29A
INFO: 2017-04-05 22:13:02: Disk : d18  is already running with : HSCAC2DA4SUN400G A29A
INFO: 2017-04-05 22:13:02: Disk : d19  is already running with : HSCAC2DA4SUN400G A29A
INFO: 2017-04-05 22:13:02: Disk : d20  is already running with : HSCAC2DA6SUN200G A29A
INFO: 2017-04-05 22:13:03: Disk : d21  is already running with : HSCAC2DA6SUN200G A29A
INFO: 2017-04-05 22:13:03: Disk : d22  is already running with : HSCAC2DA6SUN200G A29A
INFO: 2017-04-05 22:13:03: Disk : d23  is already running with : HSCAC2DA6SUN200G A29A
INFO: 2017-04-05 22:13:03: Disk : d40  is already running with : HSCAC2DA4SUN400G A29A
INFO: 2017-04-05 22:13:03: Disk : d41  is already running with : HSCAC2DA4SUN400G A29A
INFO: 2017-04-05 22:13:03: Disk : d42  is already running with : HSCAC2DA4SUN400G A29A
INFO: 2017-04-05 22:13:04: Disk : d43  is already running with : HSCAC2DA4SUN400G A29A
INFO: 2017-04-05 22:13:04: Disk : d44  is already running with : HSCAC2DA6SUN200G A29A
INFO: 2017-04-05 22:13:04: Disk : d45  is already running with : HSCAC2DA6SUN200G A29A
INFO: 2017-04-05 22:13:04: Disk : d46  is already running with : HSCAC2DA6SUN200G A29A
INFO: 2017-04-05 22:13:04: Disk : d47  is already running with : HSCAC2DA6SUN200G A29A
INFO: 2017-04-05 22:13:04: ....................Patching Shared HDDs...............
INFO: 2017-04-05 22:13:04: Disk : d0  is already running with : H7280A520SUN8.0T PAG1
INFO: 2017-04-05 22:13:05: Disk : d1  is already running with : H7280A520SUN8.0T PAG1
INFO: 2017-04-05 22:13:05: Disk : d2  is already running with : H7280A520SUN8.0T PAG1
INFO: 2017-04-05 22:13:05: Disk : d3  is already running with : H7280A520SUN8.0T PAG1
INFO: 2017-04-05 22:13:05: Disk : d4  is already running with : H7280A520SUN8.0T PAG1
INFO: 2017-04-05 22:13:05: Disk : d5  is already running with : H7280A520SUN8.0T PAG1
INFO: 2017-04-05 22:13:05: Disk : d6  is already running with : H7280A520SUN8.0T PAG1
INFO: 2017-04-05 22:13:06: Disk : d7  is already running with : H7280A520SUN8.0T PAG1
INFO: 2017-04-05 22:13:06: Disk : d8  is already running with : H7280A520SUN8.0T PAG1
INFO: 2017-04-05 22:13:06: Disk : d9  is already running with : H7280A520SUN8.0T PAG1
INFO: 2017-04-05 22:13:06: Disk : d10  is already running with : H7280A520SUN8.0T PAG1
INFO: 2017-04-05 22:13:06: Disk : d11  is already running with : H7280A520SUN8.0T PAG1
INFO: 2017-04-05 22:13:06: Disk : d12  is already running with : H7280A520SUN8.0T PAG1
INFO: 2017-04-05 22:13:07: Disk : d13  is already running with : H7280A520SUN8.0T PAG1
INFO: 2017-04-05 22:13:07: Disk : d14  is already running with : H7280A520SUN8.0T PAG1
INFO: 2017-04-05 22:13:07: Disk : d15  is already running with : H7280A520SUN8.0T PAG1
INFO: 2017-04-05 22:13:07: Disk : d24  is already running with : H7240AS60SUN4.0T A3A0
INFO: 2017-04-05 22:13:07: Disk : d25  is already running with : H7240AS60SUN4.0T A3A0
INFO: 2017-04-05 22:13:07: Disk : d26  is already running with : H7240AS60SUN4.0T A3A0
INFO: 2017-04-05 22:13:08: Disk : d27  is already running with : H7240AS60SUN4.0T A3A0
INFO: 2017-04-05 22:13:08: Disk : d28  is already running with : H7240AS60SUN4.0T A3A0
INFO: 2017-04-05 22:13:08: Disk : d29  is already running with : H7240AS60SUN4.0T A3A0
INFO: 2017-04-05 22:13:08: Disk : d30  is already running with : H7240AS60SUN4.0T A3A0
INFO: 2017-04-05 22:13:08: Disk : d31  is already running with : H7240AS60SUN4.0T A3A0
INFO: 2017-04-05 22:13:08: Disk : d32  is already running with : H7240AS60SUN4.0T A3A0
INFO: 2017-04-05 22:13:09: Disk : d33  is already running with : H7240AS60SUN4.0T A3A0
INFO: 2017-04-05 22:13:09: Disk : d34  is already running with : H7240AS60SUN4.0T A3A0
INFO: 2017-04-05 22:13:09: Disk : d35  is already running with : H7240AS60SUN4.0T A3A0
INFO: 2017-04-05 22:13:09: Disk : d36  is already running with : H7240AS60SUN4.0T A3A0
INFO: 2017-04-05 22:13:09: Disk : d37  is already running with : H7240AS60SUN4.0T A3A0
INFO: 2017-04-05 22:13:09: Disk : d38  is already running with : H7240AS60SUN4.0T A3A0
INFO: 2017-04-05 22:13:10: Disk : d39  is already running with : H7240AS60SUN4.0T A3A0
INFO: 2017-04-05 22:13:10: ....................Patching Expanders...............
INFO: 2017-04-05 22:13:10: Expander : c1x0  is already running with : DE2-24C 0018
INFO: 2017-04-05 22:13:10: Expander : c1x1  is already running with : DE2-24C 0018
INFO: 2017-04-05 22:13:10: Expander : c2x0  is already running with : DE2-24C 0018
INFO: 2017-04-05 22:13:10: Expander : c2x1  is already running with : DE2-24C 0018
INFO: 2017-04-05 22:13:10: ..............Patching Shared Controllers...............
INFO: 2017-04-05 22:13:10: Updating the  Controller : c1 with the Firmware : 0x0097 10.00.00.00
SUCCESS: 2017-04-05 22:15:32: Successfully updated the Firmware on  Controller : c1 to 0x0097 10.00.00.00
INFO: 2017-04-05 22:15:32: Updating the  Controller : c2 with the Firmware : 0x0097 10.00.00.00
SUCCESS: 2017-04-05 22:17:58: Successfully updated the Firmware on  Controller : c2 to 0x0097 10.00.00.00
INFO: 2017-04-05 22:17:58: ------------ Completed Storage Patching------------
 
INFO: 2017-04-05 22:17:58: Completed patching of shared_storage
INFO: Patching completed for component Storage
INFO: Running post-install scripts
INFO: Running postpatch on node 1...
INFO: Running postpatch on node 0...
INFO: 2017-04-05 22:18:00: Some of the components patched on node <192.168.16.25>
INFO: 2017-04-05 22:18:00: require node reboot. Rebooting the node
INFO: 2017-04-05 22:18:00: Some of the components patched on node <192.168.16.24>
INFO: 2017-04-05 22:18:00: require node reboot. Rebooting the node
INFO: Rebooting node 1
INFO: 2017-04-05 22:18:00: Running /tmp/pending_actions on node 1
INFO: Node will reboot now.
INFO: Please check reboot progress via ILOM interface
INFO: This session may appear to hang, press ENTER after reboot
INFO: 2017-04-05 22:18:20: Rebooting node 0
INFO: Running /tmp/pending_actions on node 0
Chassis Power Control: Cycle

Nota: Depois de atualizar o storage, ambos os nodes irão reiniciar. Logue-se no dbserver01,dbserver02 e verifique se o storage foi atualizado usando a interface de linha de comando oakcli. Execute o comando abaixo para verificar a atualização do storage.

[ root@dbserver01 : Tue Apr 18, 01:13 PM : /root ]
$ oakcli update -patch 12.1.2.10 --verify

02

6. Aplique o Database Patch

O Database patch pode ser aplicado usando a opção ‘-local’. Se a opção ‘-local’ não for utilizada, o database patch irá ser aplicado usando rolling fashion. O Node1 é atualizado e então o node2 é atualizado. Emita o comando abaixo para aplicar o patch no database.

$ oakcli update -patch  12.1.2.10.0  --database <--local>
 
 [ root@dbserver01 : Wed Apr 05, 10:25 PM : /tmp/patches/ODA ]
 
$ /opt/oracle/oak/bin/oakcli update -patch  12.1.2.10.0  
--database
INFO: 2017-04-05 22:25:35: Clusterware is not running on 
one or more nodes of the cluster
INFO: 2017-04-05 22:25:35: Attempting to start clusterware 
and its resources across the cluster
INFO: 2017-04-05 22:25:36: Sleeping for 30 seconds waiting 
for clusterware to start
SUCCESS: 2017-04-05 22:26:06: Successfully started the 
clusterware
 
INFO: Running pre-install scripts
INFO: Running  prepatching on node 0
INFO: Running  prepatching on node 1
INFO: Completed pre-install scripts
...
...
INFO: 2017-04-05 22:26:41: ----------Patching DB-----------
INFO: 2017-04-05 22:26:41: Getting all the possible Database 
Homes for patching
...
INFO: 2017-04-05 22:27:00: Patching 11.2.0.4 Database Homes 
on the Node dbserver01
 
Found the following 11.2.0.4 homes possible for patching:
 
HOME_NAME                       HOME_LOCATION
---------------------           ----------------------------
OraDb11204_home1                /u01/app/oracle/product/
11.2.0.4/dbhome_1
 
[Please note that few of the above Database Homes may be 
already up-to-date. They will be automatically ignored]
 
Would you like to patch all the above homes: Y | N ? : Y
INFO: 2017-04-05 22:27:09: Updating OPATCH
Verifying Opatch version for home:.
Expecting version:<11.2.0.3.15>
Opatch version on node  is <11.2.0.3.15> Opatch version on node  is <11.2.0.3.15> INFO: 2017-04-05 22:28:02: 
Performing the conflict checks... SUCCESS: 2017-04-05 22:28:10: Conflict checks passed for all the Homes
INFO: 2017-04-05 22:28:10: Checking if the patch is already applied on any of the Homes
INFO: 2017-04-05 22:28:14: Following Homes are already Up-to-date /u01/app/oracle/product/11.2.0.4/dbhome_1
INFO: 2017-04-05 22:28:14: Patching 11.2.0.4 Database Homes on the Node dbserver02 ...
INFO: 2017-04-05 22:29:13: Patching 12.1.0.2 Database Homes on the Node dbserver01
Found the following 12.1.0.2 homes possible for patching: HOME_NAME
HOME_LOCATION ------------------- -------------------------- OraDb12102_home1
/u01/app/oracle/product/ 12.1.0.2/dbhome_1
[Please note that few of the above Database Homes may be already up-to-date. They will be automatically ignored]
Would you like to patch all the above homes: Y | N ?: Y
INFO: 2017-04-05 22:29:21: Updating OPATCH Verifying Opatch version for home:.
Expecting version:<12.2.0.1.8> Opatch version on node is <12.2.0.1.8>
Opatch version on node is <12.2.0.1.8> INFO: 2017-04-05 22:30:55:
Performing the conflict checks... SUCCESS: 2017-04-05 22:31:04: Conflict checks passed for all the Homes
INFO: 2017-04-05 22:31:04:Checking if the patch is already applied on any of the Homes
INFO: 2017-04-05 22:31:08: Home is not Up-to-date
SUCCESS: 2017-04-05 22:31:31: Successfully stopped the Database consoles
SUCCESS: 2017-04-05 22:31:58: Successfully stopped the EM agents
INFO: 2017-04-05 22:32:03: Applying patch on /u01/app/ oracle/product/12.1.0.2/dbhome_1 Homes
INFO: 2017-04-05 22:32:03: It may take upto 15 mins. Please wait...
SUCCESS: 2017-04-05 22:37:29: Successfully applied the patch on the Home:/u01/app/oracle/product/12.1.0.2/dbhome_1
SUCCESS: 2017-04-05 22:37:29: Successfully started the Database consoles
SUCCESS: 2017-04-05 22:37:56: Successfully started the EM Agents
INFO: 2017-04-05 22:38:10: Patching 12.1.0.2 Database
Homes on the Node dbserver02 INFO: DB patching summary on node: dbserver01
INFO: 2017-04-05 22:45:41: The Homes /u01/app/oracle/ product/11.2.0.4/dbhome_1 are already Up-to-date
SUCCESS: 2017-04-05 22:45:41: Successfully applied the patch on the Home /u01/app/oracle/product/12.1.0.2/dbhome_1
INFO: DB patching summary on node: dbserver02
INFO: 2017-04-05 22:45:41: The Homes /u01/app/oracle/ product/11.2.0.4/dbhome_1 are already Up-to-date
SUCCESS: 2017-04-05 22:45:41: Successfully applied the patch on the Home /u01/app/oracle/product/12.1.0.2/dbhome_1
INFO: Executing /tmp/pending_actions on both nodes

Pós instalação:

O comando oackcli show é usado para verificar se os patches foram aplicados. Emita o comando para verificar os patches. Logue-se como root em cada node e execute o comando abaixo:

$ oakcli show version –detail

03

Conclusão:

As atualizações (patches) do ODA são aplicados e verificados com a interface de linha de comando oakcli. A aplicação do bundle patch para o ODA inclui grid infrastructure, database e outros componentes de infra como ILOM, BIOS, firmware de Controladores e discos. Server Components e o database patches em ODA podem ser aplicados in rolling fashion (node por node).


Y V Ravi Kumar é um Oracle ACE e Oracle Certified Master (OCM) com 18 anos de experiência em instituições financeiras, serviços financeiros e seguros (BFSI) e atuou em diversos papeis como Senior Database Architect e Production DBA. Ele também é OCP em Oracle 8i, 9i, 10g, 11g & 12c e Certificado em Golden Gate, RAC, Performance Tuning & Oracle Exadata. Ele continua motivando muitos DBAs e ajudando a Oracle Community publicando suas dicas /ideias/sugestões/soluções em seu blog. Ele escreveu 40+ artigos OTN sobre Oracle Exadata, Oracle RAC e Oracle GoldenGate para a OTN em Espanhol, OTN em Português e OTN em inglês e 19 artigos para a TOAD World, 2 Artigos para o UKOUG, 3 Artigos para OTech Magazine e 2 Artigos para a Redgate. Ele é membro do All India Oracle User Group (AIOUG) e frequente Oracle speaker in @NYOUG, @OTN, AIOUG, Sangam e IOUG. Ele desenha, projeta e implementa Core Banking System (CBS) Databases para o Central Banks em dois países – India e Mahe, Seychelles. Ele é Co-Founder do OraWorld (www.oraworld.com). Leia mais sobre o seu perfil na LaserSoft

Rodrigo Mufalani é um DBA Sr. com mais de 10 anos de experiência, começou com o Oracle 8i, mas teve a oportunidade de dar suporte a Oracle 7.3.4 em diante. É especialista em banco de dados Oracle com foco principal em Performance & Tuning e RAC. É palestrante em eventos de Oracle como: OTN LAD TOUR e outros. Atualmente trabalha como consultor diversas empresas no segmento de variados ramos como: Educação, Saúde, Tecnologia, Seguros e etc. Foi o terceiro Oracle ACE a ser nomeado no Brasil e é OCP DBA nas versões 10g e 11g. Atualmente trabalha na Mufalani. Twitter @mufalani / blog www.mufalani.com.br/blog

Shireesha Baddam é uma profissional Oracle com mais de 8 anos de experiência em TI, nos ramos de serviços financeiros, eletrônicos e de logística. Trabalha como DBA Sênior e também como consultora de TI para dar suporte a diferentes aplicações. É expert em Oracle RAC, ASM, ODA e nas versões de Oracle 9i, 10g, 11g e 12c.

Este artigo foi revisto pela equipe de produtos Oracle e está em conformidade com as normas e práticas para o uso de produtos Oracle.