My Oracle Support Banner

rootcrs.sh -prepatch either manually or as part of opatchauto apply ,do not stops and unlocks the GI HOME . (Doc ID 2703720.1)

Last updated on NOVEMBER 27, 2020

Applies to:

Oracle Database - Enterprise Edition - Version 19.6.0.0.0 and later
Information in this document applies to any platform.

Symptoms

If applying patch manually & executing 'rootcrs.sh -prepatch' it do not stop and unlock the GI HOME , though the command completes successfully.

or

opatchauto apply command fails as ,when it  runs rootcrs.sh -prepatch ,which  do not stop and unlock the GI HOME, this command will complete successfully.But when opatchauto apply will proceed further to  apply the patch it fails due to permission errors.

crspatch_<hostname>_<timestamp>.log log , which is located at <ORACLE_BASE>/crsdata/<node>/crsconfig/ shows that GI HOME is not stopped & unlocked.

2020-05-17 07:45:39: Performing the pre-patching steps required for GI stack ...
2020-05-17 07:45:39: Invoking "$GI_HOME/bin/cluutil -ckpt -oraclebase $ORACLE_BASE -chkckpt -name ROOTCRS_PREPATCH -status"
2020-05-17 07:45:39: trace file=$ORACLE_BASE/crsdata/nodename/crsconfig/cluutil1.log
2020-05-17 07:45:39: Running as user grid: $GI_HOME/bin/cluutil -ckpt -oraclebase $ORACLE_BASE -chkckpt -name ROOTCRS_PREPATCH -status
2020-05-17 07:45:45: Removing file /tmp/XXXXX
2020-05-17 07:45:45: Successfully removed file: /tmp/XXXXX
2020-05-17 07:45:45: pipe exit code: 0
2020-05-17 07:45:45: /bin/su successfully executed

2020-05-17 07:45:45: SUCCESS ---->

2020-05-17 07:45:45: The 'ROOTCRS_PREPATCH' status is SUCCESS
2020-05-17 07:45:45: prepatch has already been done successfully
2020-05-17 07:45:45: Executing cmd: $GI_HOME/bin/clsecho -p has -f clsrsc -m 671
2020-05-17 07:45:45: Executing cmd: $GI_HOME/bin/clsecho -p has -f clsrsc -m 671
2020-05-17 07:45:45: Command output:
> CLSRSC-671: Pre-patch steps for patching GI home successfully completed.
>End Command output
2020-05-17 07:45:45: CLSRSC-671: Pre-patch steps for patching GI home successfully completed.

 

 

 crspatch_<hostname>_<timestamp>.log which stops and unlocks the GI HOME will show output as below:

2020-05-17 06:23:32: Invoking "$GI_HOME/bin/cluutil -ckpt -oraclebase $ORACLE_BASE -chkckpt -name ROOTCRS_PREPATCH -status"
2020-05-17 06:23:32: trace file=$ORACLE_BASE/crsdata/nodename/crsconfig/cluutil1.log
2020-05-17 06:23:32: Running as user grid: $GI_HOME/bin/cluutil -ckpt -oraclebase $ORACLE_BASE -chkckpt -name ROOTCRS_PREPATCH -status
2020-05-17 06:23:33: START ------------->

2020-05-17 06:23:33: The 'ROOTCRS_PREPATCH' is either in START/FAILED state
2020-05-17 06:23:33: Destination CRS home:
2020-05-17 06:23:33: Configured GI home: $GI_HOME
2020-05-17 06:23:33: GI Home to be patched: $GI_HOME
..
..
2020-05-17 06:24:10: Command output:
> CRS-1151: The cluster was successfully set to rolling patch mode.
>End Command output
2020-05-17 06:24:10: Successfully set the cluster in rolling patch mode
2020-05-17 06:24:10: Stopping Oracle Clusterware stack ...
2020-05-17 06:24:10: Executing cmd: $GI_HOME/bin/crsctl stop crs -f
2020-05-17 06:24:51: Command output:
> CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on 'nodename'
> CRS-2673: Attempting to stop 'ora.crsd' on 'nodename'
..
.
> CRS-2793: Shutdown of Oracle High Availability Services-managed resources on 'nodename' has completed
> CRS-4133: Oracle High Availability Services has been stopped.
>End Command output
2020-05-17 06:24:51: The return value of stop of CRS: 0
2020-05-17 06:24:51: Executing cmd: $GI_HOME/bin/crsctl check crs
2020-05-17 06:24:52: Command output:
> CRS-4639: Could not contact Oracle High Availability Services
>End Command output
2020-05-17 06:24:52: Oracle CRS stack has been shut down
2020-05-17 06:25:02: Checking if there are still GI processes running ...
2020-05-17 06:25:02: Finding running GI processes ...
2020-05-17 06:25:02: Peek at the pid file <$ORACLE_BASE/crsdata/nodename/output/crsd.pid>
2020-05-17 06:25:02: PID in <$ORACLE_BASE/crsdata/nodename/output/crsd.pid> is: 16384382
2020-05-17 06:25:02: Peek at the pid file <$ORACLE_BASE/crsdata/nodename/output/crsd_jagent_grid.pid>
2020-05-17 06:25:02: PID in <$ORACLE_BASE/crsdata/nodename/output/crsd_jagent_grid.pid> is: 25231692
2020-05-17 06:25:02: Peek at the pid file <$ORACLE_BASE/crsdata/nodename/output/crsd_oraagent_grid.pid>
2020-05-17 06:25:02: PID in <$ORACLE_BASE/crsdata/nodename/output/crsd_oraagent_grid.pid> is: 13697334
..
..
..
2020-05-17 06:25:33: Done performing prepatch steps to patch GI home
2020-05-17 06:25:33: Invoking "$GI_HOME/bin/cluutil -ckpt -oraclebase $ORACLE_BASE -writeckpt -name ROOTCRS_PREPATCH -state SUCCESS"
2020-05-17 06:25:33: trace file=$ORACLE_BASE/crsdata/nodename/crsconfig/cluutil8.log
2020-05-17 06:25:33: Running as user grid: $GI_HOME/bin/cluutil -ckpt -oraclebase $ORACLE_BASE -writeckpt -name ROOTCRS_PREPATCH -state SUCCESS
..
..
2020-05-17 06:25:34:
2020-05-17 06:25:34: Succeeded in writing the checkpoint:'ROOTCRS_PREPATCH' with status:SUCCESS
2020-05-17 06:25:34: Executing cmd: $GI_HOME/bin/clsecho -p has -f clsrsc -m 671
2020-05-17 06:25:35: Executing cmd: $GI_HOME/bin/clsecho -p has -f clsrsc -m 671
2020-05-17 06:25:35: Command output:
> CLSRSC-671: Pre-patch steps for patching GI home successfully completed.
>End Command output
2020-05-17 06:25:35: CLSRSC-671: Pre-patch steps for patching GI home successfully completed.

 

 

 

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.