The system that I will upgrade to 12.2.0.1 GI to 19.7.0.0 GI; Oracle Linux 7.7 on ExaCC (Exadata Cloud at Customer) QR machine.
Pre Upgrade:
- You can get VM node backups before upgrading.
- Execute rootupgrade.sh on each node
- Run the Cluster verify utility
[grid@node1 ]$ unzip -q /u02/app/oracle/exadata_patch/19c_grid/V982068-01.zip -d /u02/app/19.0.0.0/grid
Run the Cluster verify utility (runcluvfy.sh) and tell you the points to fix
[grid@node1 ]$ cd /u02/app/19.0.0.0/grid ./runcluvfy.sh stage -pre crsinst -upgrade -rolling -src_crshome /u01/app/12.2.0.1/grid -dest_crshome /u02/app/19.0.0.0/grid -dest_version 19.0.0.0.0 -fixup -verbose
We have applied GI Update OCT2019 (12.2.0.1.191015)- 30116802 before GI upgrade
Upgrade:
[grid@node1]$ /u02/app/19.0.0.0/grid/oui/bin/runInstaller -nowait -waitforcompletion -ignoreSysPrereqs -updateNodeList ORACLE_HOME=/u02/app/19.0.0.0/grid "CLUSTER_NODES={node1,node2}" CRS=true LOCAL_NODE=node1
You can see what you did during the upgrade process by following the log instantly.
Post Upgrade:
- Verify cluster status
- Change GRID_HOME in scripts
- Verify flex ASM cardinality is set to “ALL”
srvctl modify asm -count ALL
- Check pass file is in ASM or not
srvctl config asm
- Disable diagsnap for exadata on each node
/u02/app/19.0.0.0/grid/bin/oclumon manage -disable diagsnap
- Set compatible.asm attribute to 19.7.0.0.0
ALTER DISKGROUP ACFSC1_DG1 SET ATTRIBUTE 'compatible.asm'='19.7.0.0.0'; ALTER DISKGROUP ACFSC1_DG2 SET ATTRIBUTE 'compatible.asm'='19.7.0.0.0'; ALTER DISKGROUP RECOC1 SET ATTRIBUTE 'compatible.asm'='19.7.0.0.0'; ALTER DISKGROUP DATAC1 SET ATTRIBUTE 'compatible.asm'='19.7.0.0.0';