Category: Install Upgrade and Patches

How to Upgrade Linux OS In RAC Environment

This post introduces how to upgrade Linux OS from RHEL 5 to RHEL 7 with zero downtime for two nodes RAC. 

Subscribe to get access

Read more of this content when you subscribe today.

Subscribe

Deinstall 12.2.0.1 Grid Infrastructure Home After Being Upgraded to 18c GI

Grid Infrastructure 12.2.0.2 has been upgraded to 18c GI successfully. So 12.2.0.1 GI_HOME needs to be de-installed.  There are two ways to uninstall the old GI_HOME ( 12.2.0.1)

1) Detach GI_HOME and Remove the GI_HOME manually:

$ export ORACLE_HOME=/u01/app/grid/12.2.0.1
$ $ORACLE_HOME/OPatch/opatch lsinventory -all
$ cd $ORACLE_HOME/oui/bin
$ ./runInstaller -silent -detachHome ORACLE_HOME="/u01/app/grid/12.2.0.1"
$ unset ORACLE_HOME

-- as root user

# cd /u01/app/grid
# rm -fr 12.2.0.1

For any reason, if the above command fails, then on every node:

$ export ORACLE_HOME=/u01/app/grid/12.2.0.1 
$ $ORACLE_HOME/OPatch/opatch lsinventory -all 
$ cd $ORACLE_HOME/oui/bin 
$ ./runInstaller -silent -local -detachHome ORACLE_HOME="/u01/app/grid/12.2.0.1"
$ unset ORACLE_HOME
-- as root user
# cd /u01/app/grid
# rm -fr 12.2.0.1

2) Deinstall old GI_HOME by using “deinstall” tool :

a) Log in as root, change the permission and ownership of the old GI_HOME ( 12.2.0.1) on both nodes.

# chmod -R 755 /u01/app/12.2.0.1/grid
# chown -R grid /u01/app/12.2.0.1/grid
# chown grid /u01/app/12.2.0.1

b) Run “deinstall” under the to be deleted GI_HOME( /u01/app/12.2.0.1/grid).

$ /u01/app/12.2.0.1/grid/deinstall/deinstall

Checking for required files and bootstrapping ...
Please wait ...
Location of logs /u01/app/oraInventory/logs/

############ ORACLE DECONFIG TOOL START ############


######################### DECONFIG CHECK OPERATION START ################
## [START] Install check configuration ##
...
..
.

c) Refer and check the logs :

The Log of Deinstall 12.2.0.1 GI_HOME

How to Apply Grid Infrastructure RU/RUR Patches Before Upgrading GI from 12.2.0.1 to 18c

While upgrading GI from 12.2.0.1 to 18c, in order to minimize the downtime and reduce the impact on PROD environment,  Release Update(RU) or Release Update Reversion(RUR) patches can be applied onto new 18c GI image before setting up 18c GI.

Please note this way is different from what we normally do to apply RU/RUR patches according to patch README.html instruction.

  • RU/RUR can only be applied before 18c GI is configured (in other word, before root.sh or rootupgrade.sh is executed).
  • In this upgrade case, RU/RUR patches can only be applied onto the new 18c GI home,  patches are not to be applied to the existing (current) 12.2.0.1 GI home.
  • “opatchauto” and “opatch apply” must NOT be used as the new 18c GI home hasn’t been configured yet.

Here is the example of applying both RU/RUR patches sequentially against new 18c GI before starting to upgrade GI 12.2.0.1 to 18c.

Those following two patches will be applied on 18c GI gold imagine:

  • Patch 28828717 – GI Release Update 18.5.0.0.190115
  • Patch 29231062 – GI Release Update Revision 18.5.1.0.190416

Subscribe to get access

Read more of this content when you subscribe today.

Subscribe

Upgrade Oracle Grid Infrastructure from 12.2.0.1 to 18c

Contents

  • Pre-requisite checks
    • User ID for both oracle and grid user
    • Oracle ASM LIB configurations
    • Oracle Grid Infrastructure and Oracle RAC Packages
    • Stop Transparent HugePages
    • install cvuqdisk
    • grid/oracle profiles
    • Check and setup resource Limits
    • Run ORAchk utility to have pre-upgrading checks
    • run the command runcluvfy.sh stage -pre crsinst -upgrade to check the readiness of your Oracle Clusterware installation for upgrades
    • Download and apply the latest opatch utility onto GI home and DB homes
  • Upgrading Oracle Grid Infrastructure
  • Post Oracle Grid Infrastructure Upgrading
    • Check SCAN configuration
    • Post Upgrading Cluster Verification
    • Run Orachk -u -o post
    • Check all cluster resource status

Subscribe to get access

Read more of this content when you subscribe today.

Subscribe

Cleanup .patch_storage Directory under ORACLE_HOME

Now and then, DBA might experience disk space issues while patching and upgrading GI or DB. Under ORACLE_HOME there is a .patch_storage directory which uses huge disk space and stores all the patches already applied onto ORACLE_HOME.  Some are backup files and directories.

Following are the common methods to solve the disk space issues under ORACLE_HOME due to huge .patch_storage directory size.

Subscribe to get access

Read more of this content when you subscribe today.

Subscribe