ODA (Oracle Database Appliance): Pre-Upgrade Check Script

Asset ID:	1-79-2219973.1
Update Date:	2017-01-18
Keywords:

Solution Type Predictive Self-Healing Sure

Solution 2219973.1 : ODA (Oracle Database Appliance): Pre-Upgrade Check Script

Applies to:

Oracle Database Appliance
Oracle Database Appliance Software
Information in this document applies to any platform.

Purpose

This document explains how to use the Pre-Upgrade Check Script - a tool used to verify if various necessary conditions and checks are complete before attempting an upgrade.

At times, the ODA automated patching process may fail that could otherwise have been prevented if problems were detected prior to patching. This script is the first step to make sure that all potential problems are flagged before patching.

Scope

Basic ODA (Oracle Database Appliance) knowledge is required.

Details

This script is used to ensure that all basic checks are complete before an upgrade is attempted. This is a Python script, and as a first step, it needs paramiko package to be installed. Here is how you would do it:

1. wget http://public-yum.oracle.com/repo/OracleLinux/OL6/latest/x86_64/getPackage/python-paramiko-1.7.5-2.1.el6.noarch.rpm
2. wget http://public-yum.oracle.com/repo/OracleLinux/OL6/latest/x86_64/getPackage/python-crypto-2.0.1-22.el6.x86_64.rpm
3. rpm -i python-paramiko-1.7.5-2.1.el6.noarch.rpm python-crypto-2.0.1-22.el6.x86_64.rpm

Below is a list of checks that the script does:

1. Check for enough free space in /opt, /u01, /boot, /root and /tmp. Cleanup files on both nodes until you match and/or exceed expected storage free space.
2. Check that all the HDDs are in ONLINE/Good status.
3. Compare GI Home permissions on both nodes
4. Check that directories like /etc/init* are writeable
5. Check to see if any kernel* RPMs have been installed since last deployment.
6. Clean up old and temporary files using "oakcli manage cleanrepo"
7. Check that the VMs and Repos are stopped before starting patching
8. Check each node to verify if key services such as ASM, Cluster and Listener services are ONLINE
9. Check if both nodes version are the same and identical using "oakcli validate -d"
10. Check Flex ASM configuration
11. Check OPatch versions are same on both nodes
12. Check lspatches to see if patches installed are same on both nodes
13. Check GI versions are same on both nodes
15. Check if Dom 0 Agent is online on both nodes
15. Check if patch levels are same on both the nodes
16. Check if SSDs are not Write Protected (V1 only)

Usage

Download the attached upgrade_precheck.zip file and unzip on any one of the ODA nodes. This script makes use of purgeODALog tool (Doc ID: 2081655.1). Please copy the purgeODALog tool to the same folder that you unzip the precheck script in. Run this pre-check script before unzipping the patch bundle

Update precheck.conf with the node names of the ODA system. Run the following command:

#python upgrade_precheck.py

Log files would be in /tmp/upgrade_precheck.log

Risk

It does two things that affect storage space:

1. It cleans up repositories of older ODA software versions

2. If using purgeODALog tool, it removes logs/traces/cores from several components such Grid Infrastructure, RDBMS, TFA (Trace File Analyzer Collector), OSWatcher, OAK (Oracle Appliance Kit)

Abundant caution is expected when removing files manually.

References

<NOTE:2081655.1> - ODA (Oracle Database Appliance): Cleanup trace and log files Using purgeODALog Tool
<NOTE:2140853.1> - ODA Supplemental Pre-Patch Heath Check

Attachments

This solution has no attachment