Fleet: UPDATE_GI fails with "CLSRSC-725: The rootcrs script is not running from the home being patched"
(Doc ID 3077875.1)
Last updated on MARCH 25, 2025
Applies to:
Enterprise Manager for Oracle Database - Version 13.5.1.0.0 and laterInformation in this document applies to any platform.
Symptoms
In Cloud Control Enterprise Manager using Fleet, When running the UPDATE_GI command in RAC cluster environment, the process fails in JobStepsLog_Switch_Clusterware_Instance step with the following error.
JobStepsLog_Switch_Clusterware_Instance_Last_Node
025-03-13 14:03:06: Executing cmd: /u01/app/19c/grid_19.26/crs/install/rootcrs.sh -prepatch -dstcrshome /u01/app/19c/grid_19.26
Using configuration parameter file: /u01/app/19c/grid/crs/install/crsconfig_params
The log of current session can be found at:
/u01/app/grid/crsdata/xxxxxx/crsconfig/crs_prepatch_apply_oop_xxxxxx_2025-03-13_02-03-07PM.log
2025/03/13 14:03:14 CLSRSC-725: The rootcrs script is not running from the home being patched, which should be '/u01/app/19c/grid_19.26'.
Died at /u01/app/19c/grid/crs/install/crspatch.pm line 2986.
The command '/u01/app/19c/grid/perl/bin/perl -I/u01/app/19c/grid/perl/lib -I/u01/app/19c/grid/crs/install -I/u01/app/19c/grid/xag /u01/app/19c/grid/crs/install/rootcrs.pl -prepatch -dstcrshome /u01/app/19c/grid_19.26' execution failed
|******************** BEGIN FUNCTION CALL gridupdate::update_check_point_file ******************************************|
Function call: gridupdate::update_check_point_file ("PREPATCH" ,"/u02/tmp/62908544504954746/xxxxx" ,"FAILED")
|***********************************************************************************************************************|
Updating checkpoint...
2025-03-13 14:03:14: Executing perl -pi -e 's=PREPATCH:NOT_EXECUTED=PREPATCH:FAILED=g' /u02/tmp/62908544504954746/xxxxxx/check_point_file
2025-03-13 14:03:14: Executing cmd: perl -pi -e 's=PREPATCH:NOT_EXECUTED=PREPATCH:FAILED=g' /u02/tmp/62908544504954746/xxxxx/check_point_file
Updated checkpoint successfully.
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 |
Cause |
Solution |