Professional Documents
Culture Documents
Exadata Patch Staging and Prechecks: Solution
Exadata Patch Staging and Prechecks: Solution
Describe how to perform staging for an Exadata Platinum Patching event and
execute prechecks.
SOLUTION
Part 1 - Staging
Preparation
Before running the staging script you must download the required patches into a
directory (default is $HOME/patches) on the gateway (or to the patch base
(default /u01/patches) on the first node of the customer system). This directory
must conform to the Platinum Patching directory structure.
The top level directory maps to Patch Base and contains the Patch Utils zip file and
the following subdirectories:
YUM - This directory contains the Exadata compute node patch(es) as well as the
dbserver orchestrator patch
Execution
cd /tmp/20629335
./stage.sh -V
./stage.sh -h
Usage:
./stage.sh [-dbsgroup=<dbs_group-file>] [-patchbase=<patch-
base-direcory>]
The staging script has 3 phases. You have the option to skip or run each step
independently.
Once completed, move over to the PRECHECKS directory to proceed with prechecks.
dmiscdb01vm02
dmiscdb02vm02
Please enter your GUID on gateway machine: root
Please enter the gateway IP address or hostname: dmiscdb02
Please enter the directory containing patches on the gateway
(Default: /home/root/patches): /EXAVMIMAGES/ft/
VM List
-------
dmiscdb0[12]vm01 - EEST Lab 1 - 12.2.0.1.170814 Grid and RDBMS
dmiscdb0[12]vm02 - Platinum Lab 1 - 12.2.0.1.170814 Grid and
RDBMS
dmiscdb0[12]vm03 - EEST Lab 2 - 12.1.0.2.170814 Grid and RDBMS
dmiscdb0[12]vm04 - Platinum Lab 2 - 12.1.0.2.170814 Grid and
RDBMS
dmiscdb0[12]vm05 - SE Lab - SE-clu
dmiscdb0[12]vm06 - EEST Lab 3 - 11.2.0.4.170814 Grid and RDBMS
dmiscdb0[12]vm07 - Platinum Lab 3 - 11.2.0.4.170814 Grid and
RDBMS
root@dmiscdb02's password:
p26610322_121020_Linux-x86-64.zip 100% 2144MB 85.8MB/s 00:25
p26027495_122110_Linux-x86-64.zip 100% 2032MB 107.0MB/s 00:19
p23727148_121020_Generic.zip 100% 982KB 981.8KB/s 00:00
p26526726_12102170814ProactiveBP_Linux-x86-64.zip 100% 870KB
870.4KB/s 00:00
p26762083_12102170718ProactiveBP_Linux-x86-64.zip 100% 1718KB
1.7MB/s 00:00
p6880880_121010_Linux-x86-64.zip 100% 91MB 11.4MB/s 00:08
p20629338_121212_Linux-x86-64.zip 100% 36MB 35.9MB/s 00:00
p21634633_181100_Linux-x86-64.zip 100% 157MB 156.7MB/s 00:01
p26151721_122110_Linux-x86-64.zip 100% 959MB 106.6MB/s 00:09
2017-Nov-08 22:04:31 UTC [SUCCESS] Patches copied to
dmiscdb02vm02
Part 2 - Prechecks
Preparation
a. create a patch.conf file in the patch base directory. The required contents for
this file can be found on the "Precheck Automation" tab of the patch plan.
b. locate or create the required group files containing one node per line. The
group files are needed for
o compute nodes (dbs_group - default is
/opt/oracle.SupportTools/onecommand/dbs_group)
o cell nodes (cell_group - default is
/opt/oracle.SupportTools/onecommand/cell_group)
o IB switches (ibswitches.lst - default is ibswitches.lst in the cell patch
directory)
Execution
Change to the PRECHECKS directory under the patch base and execute the
precheck.sh script. In most cases you should not need to supply any arguments. Use
the -help flag to list all options.
# ./precheck.sh -V
# ./precheck.sh -h
./precheck.sh [options]
Options:
-patchbase=<dir> Default:/u01/patches
-dbsgroup=<file>
Default:/opt/oracle.SupportTools/onecommand/dbs_group
-cellgroup=<file>
Default:/opt/oracle.SupportTools/onecommand/cell_group
-switchgroup=<file>
Default:EXADATA_CELL_DIRECTORY/ibswitches.lst
-recheck_all Discards pass list and rechecks all
applicable checks
-skip_dbsrv Skips compute node checks
-skip_cells Skips cell checks
-skip_database Skips database checks
-skip_ib Skips infiniband checks
-skip_em Skips EM checks
-skip_data_collection Skips data collection
-event Discards pass list and rechecks all
applicable checks
except YUM, Cell, IB, and dbhomeupdate
prechecks
-critical Discards pass list and rechecks only
critical checks
You may execute the script as many times as needed. The script will remember the
last run for up to 24 hours. Upon re-execution, the script will, by default, only
recheck checks that have not already passed. If you want to redo all checks then
supply the -recheck_all flag.
Once completed, upload the resulting zip file the the patch event SR.