rootupgrade.sh got stuck on step 5 of 19 on first node during GI Upgrade from 12.1. to 12.2
(Doc ID 2337641.1)
Last updated on FEBRUARY 19, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 12.2.0.1 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
This is 2 nodes RAC, running on GI 12.1.0.2. During upgrading Grid Infrastructure to 12.2.0.1, seems like rootupgrade.sh got stuck at step #5 of 19 Oracle Grid Infra upgrade rolling Upgrade from 12.1. to 12.2 Appears stuck
File: gridSetupActions2017-12-09_16-03-42-40PM.log
The log of current session can be found at:
<ORACLE_BASE>/crsconfig/rootcrs_racnode1_2017-12-09_03-40-41PM.log
...
...
2017/12/09 15:49:47 CLSRSC-595: Executing upgrade step 1 of 19: 'UpgradeTFA'.
2017/12/09 15:49:48 CLSRSC-4015: Performing install or upgrade action for Oracle Trace File Analyzer (TFA) Collector.
2017/12/09 15:53:37 CLSRSC-4003: Successfully patched Oracle Trace File Analyzer (TFA) Collector.
2017/12/09 15:53:38 CLSRSC-595: Executing upgrade step 2 of 19: 'ValidateEnv'.
2017/12/09 15:54:03 CLSRSC-595: Executing upgrade step 3 of 19: 'GenSiteGUIDs'.
2017/12/09 15:54:06 CLSRSC-595: Executing upgrade step 4 of 19: 'GetOldConfig'.
2017/12/09 15:54:06 CLSRSC-464: Starting retrieval of the cluster configuration data
2017/12/09 15:54:25 CLSRSC-515: Starting OCR manual backup.
2017/12/09 15:54:38 CLSRSC-516: OCR manual backup successful.
...
...
2017/12/09 15:55:24 CLSRSC-465: Retrieval of the cluster configuration data has successfully completed.
2017/12/09 20:52:49 CLSRSC-595: Executing upgrade step 5 of 19: 'UpgPrechecks'. <<<<<<<<<<<<<<<<<<<<<<<<<< Here got stuck
From rootcrs.log it is showing asmcmd --nocp chkdg command taking long time on BIGDATA diskgroup which is 45 TB diskgroup.
File: rootcrs_racnode1_2017-12-09_03-40-41PM.log
2017-12-09 16:47:04: Invoking asmcmd chkdg DATA
2017-12-09 16:47:04: Running as user oracle: <Grid Infrastructure Home>/bin/asmcmd --nocp chkdg DATA
2017-12-09 16:47:04: s_run_as_user2: Running /bin/su oracle -c ' echo CLSRSC_START; <Grid Infrastructure Home>/bin/asmcmd --nocp chkdg DATA '
2017-12-09 20:52:49: Removing file /tmp/DT2ZtYpfbT
2017-12-09 20:52:49: Successfully removed file: /tmp/DT2ZtYpfbT
2017-12-09 20:52:49: pipe exit code: 0
2017-12-09 20:52:49: /bin/su successfully executed
2017-12-09 20:52:49: Chkdg Output: Diskgroup altered.
2017-12-09 20:52:49: Invoking asmcmd chkdg RECO
2017-12-09 20:52:49: Running as user oracle: <Grid Infrastructure Home>/bin/asmcmd --nocp chkdg RECO
2017-12-09 20:52:49: s_run_as_user2: Running /bin/su oracle -c ' echo CLSRSC_START; <Grid Infrastructure Home>/bin/asmcmd --nocp chkdg BIGDATA '
From ASM alert log:
several executions of the command 'ALTER DISKGROUP <DGNAME> CHECK NOREPAIR' is observed in the alert log.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |