The upgrade will be done in rolling mode.
PRECHECKS:
1. Note the output of below commands on each node.
crsctl stat res -t
crsctl check crs
2. Check activeversion, softwareversion and releaseversion:
crsctl query crs activeversion
crsctl query crs softwareversion
crsctl query crs releaseversion
activeversion:
This is the version of grid across all nodes of the cluster. If the rolling upgrade is not completed across all nodes of the cluster, it will show the previous version of grid.
releaseversion:
It shows the grid version installed in the binaries of the local node.
softwareversion [node_name]:
It gives the leverage to check the grid version of the remote node. It tell the grid version that has been successfully started on the specified node which is mentioned in the command. If not specified it shows the same for the local node.
crsctl query crs softwareversion [node_name]
If you do not provide a node name, then Oracle Clusterware displays the version of Oracle Clusterware running on the local server.
Example
The crsctl query crs softwareversion command returns output similar to the following:
Oracle Clusterware version on node [node1] is [11.2.0.2.0]
3. Apply required patches to your existing 12c grid.
4. Download the software and unzip on your first node.
5. Run the orachk tool as grid owner ( oracle)
orachk tool will generate a report for recommendation, that need to be taken care before upgrading.
export GRID_HOME=/u01/oracle/app/grid19c
cd /u01/oracle/app/grid19c/suptools/orachk/
./orachk –u -o pre
Analyze the html report for any recommendations.
6. Run cluvfy as grid owner ( oracle )
cd /u01/oracle/app/grid19c
syntax – >
./runcluvfy.sh stage -pre crsinst -upgrade -rolling -src_crshome -dest_crshome -dest_version 19.0.0.0.0 -fixup -verbose
i.e
./runcluvfy.sh stage -pre crsinst -upgrade -rolling -src_crshome /drcrs/app/oracle/product/grid12c -dest_crshome /u01/oracle/app/grid19c -dest_version 19.0.0.0.0 -fixup -verbose
In case any error reported, fix them before proceeding further.
DRY RUN PHASE
It may restart the cluster nodes so take downtime if possible to run it.
Dry run phase will not do any changes to the existing grid setup. It will just check the system readiness.
As per oracle note: Dry run does below activities:
· Validates storage and network configuration for the new release
· Checks if the system meets the software and hardware requirements for the new release.
· Checks for the patch requirements and apply necessary patches before starting the upgrade.
· Writes system configuration issues or errors in the gridSetupActions<timestamp>.log log file
— Run as grid owner ( oracle)
unset ORACLE_BASE
unset ORACLE_HOME
unset ORACLE_SID
cd /u01/oracle/app/grid19c
./gridSetup.sh –dryRunForUpgrade
Follow the Gui instructions.
The warnings for public network interface can be ignored.
It will ask to run rootupgrade.sh on local node only. Not to be run on the remote node.
The dry run upgrade is successful. Lets proceed with actual upgrade.
ACTUAL UPGRADE:
Now we will proceed with the actual upgrade in a rolling mode .
— Run as grid owner ( oracle )
unset ORACLE_BASE
unset ORACLE_HOME
unset ORACLE_SID
cd /u01/oracle/app/grid19c
./gridSetup.sh
Follow the Gui instructions
Or You can execute it using responsefile:
run gridsetup.sh script with the resonse file :
./gridSetup.sh -executeConfigTools -responseFile /u01/crsapp/grid19c/install/response/gridinstall_5_07_2019.rsp
This will skip the already executed tasks and complete the pending configuration.
It will ask to run rootupgrade.sh first on the local node. Then it can be executed parallely in subsequent nodes except the last node. Run this script in the end on the last node.
The rootupgrade.sh does the following:
1. Sets oracle_owner, oracle_home.
2. Put oraenv and coraenv in /usr/local/bin/ directory.
3. Add entires in /etc/oratab file.
4. Relinking will be done.
5. Check and validate the the crs confiruration which is present in /u01/oracle/app/grid19c/crs/install/crsconfig_params file.
6. Stop the TFA process.
Once rootupgade.sh script execution completed on both nodes. Proceed to resume.
We have successful upgraded the grid to 19c version.
POST CHECK :
7. Check activeversion, softwareversion and releaseversion:
crsctl query crs activeversion
crsctl query crs softwareversion
crsctl query crs releaseversion
oracle@node1:~$ crsctl query crs activeversion
Oracle Clusterware active version on the cluster is [19.0.0.0.0]
oracle@node1:~$ crsctl query crs softwareversion
Oracle Clusterware version on node [node1] is [19.0.0.0.0]
oracle@node2:~$ crsctl query crs activeversion
Oracle Clusterware active version on the cluster is [19.0.0.0.0]
oracle@node2:~$ crsctl query crs softwareversion
Oracle Clusterware version on node [node2] is [19.0.0.0.0]
8. Run the below commands on each node and compare the output of below commands with the prechecks.
crsctl stat res -t
crsctl check crs
TROUBLESHOOTING:
1. If rootupgrade.sh script failed on local node:
In case rootupgrade.sh script failed on local node either due to any error or system got rebooted during that time, Then analyze the error and fix it . Once fixed, resume the ugprade with below step.
–run rootupgrade.sh script again on node 1:
cd /u01/crsapp/grid19c
/u01/crsapp/grid19c/rootupgrade.sh
–run rootupgrade.sh script again on node 2
cd /u01/crsapp/grid19c
/u01/crsapp/grid19c/rootupgrade.sh
Now we will proceed with the actual upgrade in a rolling mode .
— Run as grid owner ( oracle )
unset ORACLE_BASE
unset ORACLE_HOME
unset ORACLE_SID
cd /u01/oracle/app/grid19c
./gridSetup.sh
Follow the Gui instructions
Or You can execute it using responsefile:
run gridsetup.sh script with the resonse file :
./gridSetup.sh -executeConfigTools -responseFile /u01/crsapp/grid19c/install/response/gridinstall_5_07_2019.rsp
This will skip the already executed tasks and complete the pending configuration.
It will ask to run rootupgrade.sh first on the local node. Then it can be executed parallely in subsequent nodes except the last node. Run this script in the end on the last node.
The rootupgrade.sh does the following:
1. Sets oracle_owner, oracle_home.
2. Put oraenv and coraenv in /usr/local/bin/ directory.
3. Add entires in /etc/oratab file.
4. Relinking will be done.
5. Check and validate the the crs confiruration which is present in /u01/oracle/app/grid19c/crs/install/crsconfig_params file.
6. Stop the TFA process.
Once rootupgade.sh script execution completed on both nodes. Proceed to resume.
We have successful upgraded the grid to 19c version.
POST CHECK :
7. Check activeversion, softwareversion and releaseversion:
crsctl query crs activeversion
crsctl query crs softwareversion
crsctl query crs releaseversion
oracle@node1:~$ crsctl query crs activeversion
Oracle Clusterware active version on the cluster is [19.0.0.0.0]
oracle@node1:~$ crsctl query crs softwareversion
Oracle Clusterware version on node [node1] is [19.0.0.0.0]
oracle@node2:~$ crsctl query crs activeversion
Oracle Clusterware active version on the cluster is [19.0.0.0.0]
oracle@node2:~$ crsctl query crs softwareversion
Oracle Clusterware version on node [node2] is [19.0.0.0.0]
8. Run the below commands on each node and compare the output of below commands with the prechecks.
crsctl stat res -t
crsctl check crs
TROUBLESHOOTING:
1. If rootupgrade.sh script failed on local node:
In case rootupgrade.sh script failed on local node either due to any error or system got rebooted during that time, Then analyze the error and fix it . Once fixed, resume the ugprade with below step.
–run rootupgrade.sh script again on node 1:
cd /u01/crsapp/grid19c
/u01/crsapp/grid19c/rootupgrade.sh
–run rootupgrade.sh script again on node 2
cd /u01/crsapp/grid19c
/u01/crsapp/grid19c/rootupgrade.sh
