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.
Category: GI and RAC
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 :
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.
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.
CLSRSC-488: Patching the Grid Infrastructure Management Repository database failed
opatchauo failed when applying GI release update.
[root@racnode1 ~]# /u01/app/12.2.0.1/grid/OPatch/opatchauto
apply /media/sf_Software/12201-190115/30501932
...
..
.
CRS-4123: Oracle High Availability Services has been started.
Oracle Clusterware active version on the cluster is [12.2.0.1.0].
The cluster upgrade state is [ROLLING PATCH].
The cluster active patch level is [1477401644].
CRS-2672: Attempting to start 'ora.drivers.acfs' on 'racnode1'
CRS-2676: Start of 'ora.drivers.acfs' on 'racnode1' succeeded
SQL Patching tool version 12.2.0.1.0 Production on Sat Mar 7 15:46:51 2020
Copyright (c) 2012, 2019, Oracle. All rights reserved.
Connecting to database...OK
Note: Datapatch will only apply or rollback SQL fixes for PDBs
that are in an open state, no patches will be applied to closed PDBs.
Please refer to Note: Datapatch: Database 12c Post Patch SQL Automation
(Doc ID 1585822.1)
Bootstrapping registry and package to current versions...done
Determining current state...done
Adding patches to installation queue and performing prereq checks...done
Installation queue:
For the following PDBs: CDB$ROOT PDB$SEED GIMR_DSCREP_10
The following patches will be rolled back:
29708478 (DATABASE JAN 2019 RELEASE UPDATE REVISION 12.2.0.1.190716)
The following patches will be applied:
30593149 (DATABASE JAN 2020 RELEASE UPDATE 12.2.0.1.200114)
Installing patches...
Patch installation complete. Total patches installed: 6
Validating logfiles...
Patch 29708478 rollback (pdb CDB$ROOT): WITH ERRORS
logfile: /u01/app/grid/cfgtoollogs/sqlpatch/29708478/22988073/
29708478_rollback__MGMTDB_CDBROOT_2020Mar07_15_47_52.log (errors)
Error at line 25435: Warning: Package Body created with compilation errors.
Error at line 25442: 24/12 PLS-00323: subprogram or cursor 'GET_OPTIONAL_PRIVILEGES' is
Error at line 25446: 2727/5 PL/SQL: Statement ignored
Error at line 25447: 2727/21 PLS-00306: wrong number or types of arguments in call to
Error at line 36437: Warning: Package Body created with compilation errors.
Error at line 36444: 18788/3 PL/SQL: Statement ignored
Error at line 36445: 18788/6 PLS-00201: identifier
Error at line 36448: 18792/3 PL/SQL: Statement ignored
Error at line 36449: 18792/3 PLS-00201: identifier
Patch 29708478 rollback (pdb PDB$SEED): WITH ERRORS
logfile: /u01/app/grid/cfgtoollogs/sqlpatch/29708478/22988073/
29708478_rollback__MGMTDB_PDBSEED_2020Mar07_15_50_23.log (errors)
Error at line 36419: Warning: Package Body created with compilation errors.
Error at line 36426: 18788/3 PL/SQL: Statement ignored
Error at line 36427: 18788/6 PLS-00201: identifier
Error at line 36430: 18792/3 PL/SQL: Statement ignored
Error at line 36431: 18792/3 PLS-00201: identifier
Patch 29708478 rollback (pdb GIMR_DSCREP_10): WITH ERRORS
logfile: /u01/app/grid/cfgtoollogs/sqlpatch/29708478/22988073/
29708478_rollback__MGMTDB_GIMR_DSCREP_10_2020Mar07_15_50_23.log (errors)
Error at line 52094: Warning: Package Body created with compilation errors.
Error at line 52101: 18788/3 PL/SQL: Statement ignored
Error at line 52102: 18788/6 PLS-00201: identifier
Error at line 52105: 18792/3 PL/SQL: Statement ignored
Error at line 52106: 18792/3 PLS-00201: identifier
Please refer to MOS Note 1609718.1 and/or the invocation log
/u01/app/grid/cfgtoollogs/sqlpatch/sqlpatch_9475_2020_03_07_15_46_51/sqlpatch_invocation.log
for information on how to resolve the above errors.
SQL Patching tool complete on Sat Mar 7 15:54:51 2020
2020/03/07 15:54:51 CLSRSC-488: Patching the Grid Infrastructure
Management Repository database failed.
After fixing the cause of failure Run opatchauto resume
]
OPATCHAUTO-68061: The orchestration engine failed.
OPATCHAUTO-68061: The orchestration engine failed with return code 1
OPATCHAUTO-68061: Check the log for more details.
OPatchAuto failed.
OPatchauto session completed at Sat Mar 7 15:54:52 2020
Time taken to complete the session 22 minutes, 24 seconds
opatchauto failed with error code 42
[root@racnode1 ~]#
Subscribe to get access
Read more of this content when you subscribe today.
Make DBA Life Easy 