ODA 3 Patching

Oracle Database Appliance
Patching - What's new in 12.1.2.6.0 & 12.1.2.7.0
Ruggero Citton
Product Development Technical Manager
RACPack Team ODA Product Development
June 2016
Copyright 2015, Oracle and/or its affiliates. All rights reserved. | Oracle Confidential Restricted
Safe Harbor Statement
The preceding is intended to outline our general product direction. It is intended for
information purposes only, and may not be incorporated into any contract. It is not a
commitment to deliver any material, code, or functionality, and should not be relied upon
in making purchasing decisions. The development, release, and timing of any features or
functionality described for Oracles products remains at the sole discretion of Oracle.
Copyright 2015, Oracle and/or its affiliates. All rights reserved. | Confidential Oracle Internal/Restricted/Highly Restricted 3
ODA Patching
Patching modes
Local Patching
Local patching is already available in 12.1.2.6.0
Rolling Patching
Rolling Patching will be available from 12.1.2.7.0
Copyright 2015, Oracle and/or its affiliates. All rights reserved. | Oracle Confidential Internal/Restricted/Highly Restricted 4
Local Patching in 12.1.2.6.0
Overview
This requirement came from several big customers. There have several
critical databases running on their ODA systems. While patching the ODA
systems in the past, the databases were being brought down. The
downtime for these databases at times extended for a few hours. It has
become increasingly important that the customers have access to the
databases while patching. Hence the need to patch the two ODA nodes
locally.
Limitation: Minimum required version for local patching is 12.1.2.5.0
Re-image to 12.1.2.6.0 will not update ILOM, BIOS, HBA, Expander, disk
firmware either. Before re-imaging, please make sure these components
are all up-to-date.
Overview
The concept for local patching is simple. Upgrade those components that
do not require the CRS stack to be brought down on both nodes. It is ok to
stop and start the CRS on the local node. The option '--local is added for
this.
The user is not expected to input the password for root, grid, database
users when patching using '--local'.
For local patching we bring down the VMs, shared repos, oakd and CRS
stack on the local node only (not across cluster). So there will be no
downtime for the second node.
Components
--infra
--gi
--database
Note: In 12.1.2.6 local patching can patch only one component at a time.
What's new
OL 5.11 to OL 6.7
HMP, IPMI, ASR, OAK, JDK also patched
No ILOM, BIOS, HBA, expander, disk firmware updates
New --local option, mandatory for --infra, optional for --gi and --
database
Offline validateOL6.zip, available thru OTN download
./validateOl6PreChecks
Online oakcli validate c ol6upgrade --prechecks
Online oakcli validate c ol6upgrade --postchecks
What's new
InfiniBand Enhancement infiniFixSetup.py
Oracle Database (PSU) 12.1.0.2.160119, 11.2.0.4.160119 and 11.2.0.3.15.
ODA ACFS bundle patches were rolled into GI PSU packages
12.1.2.2 Jan 2015 USM_PT.PERF
12.1.2.3 Apr 2015 USM_PT.ODA1
12.1.2.4 July 2015 USM_PT.ODA2
12.1.2.5 Oct 2015 USM_PT.ODA3
12.1.2.6 Jan 2016 USM_PT.ODA4
12.1.2.7 Jan 2016, no ODA ACFS bundle patches
/u01/app/12.1.0.2/grid/bin/acfsdriverstate -orahome /u01/app/12.1.0.2/grid version
dmesg | grep USM
USM_PT.ODA*_LINUX.X64_<labelDate>
Infrastructure (--infra)
oakcli update -patch 12.1.2.6.0 --infra -- local

patch the infra components OS, HMP, IPMI, ASR, OAK, JDK
only on local node
can be run from any node
No ILOM, BIOS, HBA, expander, disk firmware updates in this quarterly release only
Note: Customers using white paper ib_change_steps_v*.pdf implemented the

workaround for bug 20650201, please roll back the changes as steps in the white paper.
Grid (--gi)
oakcli update -patch 12.1.2.6.0 --gi
patches the grid home on both the nodes
same as earlier release
needs to be run from node-0
oakcli update -patch 12.1.2.6.0 --gi local

patch the grid home only on local node
can be run from any node
Database
oakcli update -patch 12.1.2.6.0 --database
patches the database homes on both the nodes
same as earlier release
needs to be run from node-0
oakcli update -patch 12.1.2.6.0 --database --local (patch the database
home only on local node, can be run from any node)
Note: The customer will be given the option to select, what database
homes they do not want to patch on the local node. It is their
responsibility to ensure the same database homes are patched on the
other node too (when specifying the local option).
Patching in 12.1.2.7.0
What's new
Rolling Patch in 12.1.2.7.0

Switching the train from PSU to BP (opatch able to patch BP on top of
PSU)
GI/RDBMS PSU 12.1.0.2.160419
Overview
Rolling patching is very similar to local patching Local Patching, but it is
going to patch the given component on all nodes of the cluster one after
the other.
Apart from the currently patching node, all other nodes are up and
running, so there will be no downtime required for any services that are
running from the non-patching nodes.
Rolling patching is available for only Server and Database, not storage.
Server (infra + local storage + gi)
Storage (all shared hba, expander, hdd)
Database
Syntax
oakcli update --patch <version> --<component> [--rolling]
Example:
oakcli update -patch 12.1.0.2.7 --server
oakcli update -patch 12.1.0.2.7 --database
Note: 'rolling' is the default behavior for the 'oakcli update'
Order of the Operations on 2 nodes ODA
Patch the given component (server / database) on the second node
If reboot is required, reboot the node (second node)
Wait till the second node is rebooted and stack started (GI / database are
started)
Patch the given component on the first node (If the second node didn't
come-up within the time limit or GI stack failed to start on the second
node, we do not attempt to patch the first node)
Summarize the patching status
If reboot is required, reboot the first node.
ODA Patching Components
Patching components:
Server
Infra excluding shared storage, including local controller and local OS disks
GI
Shared Storage
Controller
Expander
HDDs
SSDs
Database
Server Patching
All the software components local to a ODA node comes into this
category. Most of the time patching these components may not require
any downtime for the database.
Server can be invoked in both the modes 'local / rolling'.
Server Patching Components
HMP
IPMI
ASR
OAK
JDK
OS
ILOM/BIOS
Local disks
GRID
Server Patching Syntax
oakcli update --patch <version> --server [--local | --rolling]
Note: by default it runs in rolling mode and update both the nodes.
Storage Patching 1/3
Patch all the storage components (JBOD), shared disks, controllers,
expanders on all nodes of the cluster one after the other node. The user is
expected to input 'root' password to login to remote node.
It requires complete downtime
No Local / Rolling option.
Server component must be upgraded before the storage component.
Its recommended to setup sudo for root password, please refer to
Managing OAKCLI Privileges and Security with SUDO in Database
Appliance Administration and Reference Guide.
While patching the Storage components IO needs to be stopped to avoid data
corruption. In case of shared storage, databases on all the nodes need to be stopped
to avoid the IO from remote nodes.
This causes the complete downtime of the database as long the storage patching is in
progress. So far (till 12.1.2.7) we integrated the storage patching along with the other
server components.
Many customers want to upgrade the server components (like OAK, OS, grid e.t.c)
which doesn't enforce the complete downtime more frequently than the storage
components which require the complete downtime.
To achieve this 'storage' is separated from the other infrastructure components from
12.1.2.7.
1. Stop the Clusterware stack across all the nodes in the cluster.
2. Patch shared disks from Node1
3. Patch Expanders on Node1
4. Patch Controllers on Node1
5. Logon to the second node
6. Patch Expanders on Node2
7. Patch Controllers on Node2
8. Reboot both the nodes .
Storage Patching - Syntax
oakcli update --patch <version> --storage
Note: This operation is idempotent. Patches only the un-patched

components in each run. If none of the components is patched it doesn't
reboot the system.
Patching Logging
/opt/oracle/oak/log/<nodename>/
/opt/oracle/oak/onecmd/tmp
Copyright 2015, Oracle and/or its affiliates. All rights reserved. |

ODA 3 Patching

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

ODA 3 Patching

Caricato da

Copyright:

Formati disponibili

Oracle Database Appliance

Patching - What's new in 12.1.2.6.0 & 12.1.2.7.0

oakcli update -patch 12.1.2.6.0 --infra -- local

Note: Customers using white paper ib_change_steps_v*.pdf implemented the

oakcli update -patch 12.1.2.6.0 --gi local

Rolling Patch in 12.1.2.7.0

oakcli update --patch <version> --<component> [--rolling]

Note: 'rolling' is the default behavior for the 'oakcli update'

oakcli update --patch <version> --storage

Note: This operation is idempotent. Patches only the un-patched

Potrebbero piacerti anche