Beruflich Dokumente
Kultur Dokumente
Copyright © 2017, Oracle and/or its affiliates. All rights reserved. Oracle and Java are registered trademarks of Oracle and/or its affiliates.
Copyright Other and/or
© 2017, Oracle names its
may be trademarks
affiliates. All rightsofreserved.
their respective
| owners.
Proactive Resources for Training, Tools and Social Channels
Get Proactive
Social Channels
Stay informed via:
MOS Community here
Blogs here
Oracle Support MOS How To Advisor Product Oracle Support Get Proactive Examples: EBS / Database
Essentials Video Series Webcasts Accreditation Portfolio Twitter here
Doc 553747.1 Doc 603505.1 Doc 749066.1 Doc 1583898.1 Doc 432.1 Examples: EBS / Database
Self-paced
Session playback
Live, interactive
High-level (concepts)
Learning is ongoing. Select and use learning options to meet your needs.
Saravanan Subburaj
Principal Software Engineer
Saravanan Subburaj
Principal Software Engineer
• Desupport of Direct File System(shared file system ) Placement for Oracle Cluster Registry (OCR) and
Voting Files
– Need to Move OCR/Votedisk to ASM
HUB 3
Leaf Node 1 Leaf Node 3
Application Tier
Application Tier
Orcl1 Orcl2
+ASM1 +ASM2
HUB 1 HUB 2
HUB 4
Database Tier
Copyright © 2017, Oracle and/or its affiliates. All rights reserved. |
Upgrade Readiness
12.2.0.x
Oracle Grid Infrastructure 12c 12.2.0.x
Copyright © 2017, Oracle and/or its affiliates. All rights reserved. | Upgrade Readiness 16
Pre Upgrade Checks
Generic
• unset the environment variables
– $ORACLE_HOME , $ORACLE_SID and ORA_CRS_HOME
*Ensure all your Existing databases are upgraded to 11.2 and above else you will not be able to use earlier databases with 12.2 GI
Copyright © 2017, Oracle and/or its affiliates. All rights reserved. | Upgrade Readiness 17
12.2 Considerations before upgrade
• Same user that owned the earlier release Oracle Grid Infrastructure software must perform the GI 12.2
upgrade.
• Running srvctl, crsctl, and other commands from the new Grid homes are not supported until the final
rootupgrade.sh script is run and the upgrade is complete across all nodes.
• Verify if you need to apply any mandatory patches for upgrade to succeed.
• Ensure to scale up the Hardware resources viz., CPU, MEMORY, .. before upgrade process
• Ensure to keep adequate free disk space available in GI Home mount point.
• Take a manual backup of OCR from the existing home.
• If Oracle Cluster Registry (OCR) and voting files are stored on Network File System (NFS), then move these
files to Oracle ASM disk groups before upgrading Oracle Grid Infrastructure.
Move OCR , Vote File , ASM SPILE to new Diskgroup (Doc ID 1638177.1)
Copyright © 2017, Oracle and/or its affiliates. All rights reserved. | Upgrade Readiness 18
Pre Upgrade Checks
CLUVFY - Upgrade Validation
• Run (OUI), and allow the Cluster Verification Utility (CVU) validation built into OUI to perform system
checks and generate fixup scripts.
• Run the CVU manual script runcluvfy.sh to perform system checks and generate fixup scripts.
Copyright © 2017, Oracle and/or its affiliates. All rights reserved. | Upgrade Readiness 19
Pre Upgrade Checks
ORACHK - Upgrade Readiness Assessment
• Download ORAchk from Document 1268927.2.
• Log in to the system as the Root user and unzip orachk.zip kit in same directory.
• Ensure Permission for orachk are 755 (-rwxr-xr-x). Else modify using command:
• $ chmod 755 orachk
• execute ORAchk in pre-upgrade mode and follow the on-screen prompts:
• $ ./orachk -u -o pre
• Review the HTML report generated by the ORAchk pre-upgrade execution and implement
the recommended changes as necessary.
Copyright © 2017, Oracle and/or its affiliates. All rights reserved. | Upgrade Readiness 20
Pre-Upgrade Patching
• Unzip Grid Infrastructure Gold Image to the Desired GI Home Location on the Local Node as the Grid user
• Download and Install the latest OPatch Version (Patch 6880880) to the extracted GI Gold Image as the
Grid user
– $ unzip -d $GI_HOME p6880880_<platform version info>.zip
• Apply the patch to the Gold Image by running the following as the Grid user
– For Release Updates:
$GI_HOME/gridSetup.sh -applyPSU <PATCH_LOCATION>
– For Non-Release Update patches:
$GI_HOME/gridSetup.sh -applyOneOffs <PATCH_LOCATION>
How to Apply a Grid Infrastructure Patch Before root script (root.sh or rootupgrade.sh) is Executed? (Doc ID 1410202.1)
Copyright © 2017, Oracle and/or its affiliates. All rights reserved. | Upgrade Readiness 21
Standard Upgrade Procedure
• Grid_home/gridSetup.sh
• Upgrade Oracle Grid Infrastructure: Select this option to upgrade Oracle Grid Infrastructure
(Oracle Clusterware and Oracle ASM).
Copyright © 2017, Oracle and/or its affiliates. All rights reserved. | Upgrading Oracle Grid Infrastructure to 12.2 (1) 23
Upgrading Oracle Grid Infrastructure to 12.2
4. On the Node Selection page
• Select all nodes.
5. Select installation options as prompted.
• Oracle recommends that you configure root script automation, so that the rootupgrade.sh script can
be run automatically during the upgrade.
Copyright © 2017, Oracle and/or its affiliates. All rights reserved. | Upgrading Oracle Grid Infrastructure to 12.2 (2) 24
DEMO
2. Rerun rootupgrade.sh script on first node from new home and thereafter on all remaining nodes.
• [root@node1]# ./rootupgrade.sh
3. After reboot, OUI will no longer exists, configure a response file, and provide passwords for the installation
• Sample response file : Oracle_home/install/response/product_timestamp.rsp
•oracle.install.crs.config.ipmi.bmcPassword=password
•oracle.install.asm.SYSASMPassword=password
•oracle.install.asm.monitorPassword=password
•oracle.install.config.emAdminPassword=password
1. Force upgrade the GRID infrastructure from any successful nodes to finish upgrade
2. Remove the Oracle Grid Infrastructure software from the failed nodes:
• Grid_home/deinstall/deinstall -local
3. As root user, from a node where Oracle Clusterware is already upgraded, delete the failed nodes using the delete
node command:
• Grid_home/bin/crsctl delete node -n node_name ( node_name is the node to be deleted )
4. Run the Oracle Grid Infrastructure installation wizard and follow the steps in the wizard to add the nodes after fixing
the cause of the issue:
• Grid_home/gridSetup.sh
• Alternatively, you can also add the nodes by running the addnode script:
• Grid_home/addnode/addnode.sh
Copyright © 2017, Oracle and/or its affiliates. All rights reserved. | 29
Downgrading Oracle Grid Infrastructure
2. Run “rootcrs.sh –downgrade” to downgrade Oracle Grid Infrastructure on all nodes except the first node.
• # /u01/app/12.2.0/grid/crs/install/rootcrs.sh -downgrade
3. Downgrade the last node after you downgrade all other nodes
• # /u01/app/12.2.0/grid/crs/install/rootcrs.sh -downgrade
4. Set Oracle Grid Infrastructure 11gRelease 2 (11.2) Grid home as the active Oracle Clusterware home
• $ cd /u01/app/11.2.0/grid/oui/bin
• $ ./runInstaller -nowait -waitforcompletion -ignoreSysPrereqs -updateNodeList -silent CRS=true
ORACLE_HOME=/u01/app/11.2.0/grid
5. Start the 11.2 Oracle Clusterware stack on all nodes.
• # crsctl start crs
2. Unset the Oracle ASM rolling migration mode from any other node running GI other then first node
• SQL> ALTER SYSTEM STOP ROLLING MIGRATION;
3. Run below command from any other node running GI other then first node (applies to 12.1.0.2 only)
• # clscfg -nodedowngrade -h <hostname_firstnode>
4. From the later release Grid home, run the command to downgrade Oracle Clusterware
• # rootcrs.sh -downgrade -online
5. Start Oracle Grid Infrastructure stack on the first node from the earlier release Grid home
• # crsctl start crs
4. Start Oracle Grid Infrastructure stack on the remote node from the earlier release Grid home
5. After all remote nodes are downgraded, downgrade the last remaining node (First Node)
If the cluster has Hub and Leaf Nodes, then the last node to be
downgraded must be a Hub Node.
Leaf nodes from the Oracle Grid Infrastructure 12c Release 2 (12.2)
cluster will not be a part of the Oracle Grid Infrastructure
11g Release 2 (11.2) standard cluster after the downgrade.
SYMPTOMS(gridSetup.sh reported)
INFO: [24/03/2017 10:57:16 AM] The required space in MB is : 33482 and the
diskgroup CRS has 5768 space
SEVERE: [24/03/2017 10:57:16 AM] [FATAL] [INS-43100] Installer has detected
that the free space available in the ASM diskgroup CRS is 5,768 MB, and it is
insufficient to proceed with the upgrade. To upgrade Oracle Grid
Infrastructure you should have at least 33,482 MB free space in this
diskgroup.
ACTION: Add additional disks to the diskgroup such that the total size
should be at least 33,482 MB.
SYMPTOMS(Rootupgrade.sh execution)
Use below command to ensure no other process is using 1525 before starting upgrade
$netstat -nap|grep 1525
SYMPTOMS
• Resolution : Mount the diskgroup in restricted mode and then set the compatible.asm attribute for the
diskgroup
Twitter:
https://twitter.com/oracleDBsupport
Facebook
https://www.facebook.com/OracleDatabaseSupport