Oracle Grid Infrastructure – Deinstallation of Old Grid Home
Server: ora26
Operating System: CentOS Stream 9
Activity: Deinstallation of old Oracle Grid Infrastructure home
Old Grid Home:/u01/app/26.0.0/grid
New Grid Home:/u01/app/26.4.0/grid
Software Owner: grid1. Objective
The objective of this activity is to safely deinstall the old Oracle Grid Infrastructure home (
26.0.0) after successfully switching to the new Grid Infrastructure home (26.4.0).The new Grid home must remain operational throughout this activity. ASM and its associated disk groups must not be affected.
2. Important Considerations
The new Grid home
/u01/app/26.4.0/gridis the active Grid Infrastructure home.The old Grid home
/u01/app/26.0.0/gridis no longer configured as an active Grid Infrastructure home.The previous
deinstall -checkonlyoperation reported that the old home was not a configured Grid Infrastructure home.ASM was not detected in the old Grid home.
Do not deinstall or modify the new Grid home.
Ensure the active ASM instance and disk groups remain operational.
3. Pre-Deinstallation Checks
3.1 Verify Grid Infrastructure status
Run as the grid user:
/u01/app/26.4.0/grid/bin/crsctl check crsCheck the active version:
/u01/app/26.4.0/grid/bin/crsctl query crs activeversionCheck the installed software version:
/u01/app/26.4.0/grid/bin/crsctl query crs softwareversionAll required Grid Infrastructure services should be operational.
3.2 Verify Oracle Local Registry location
cat /etc/oracle/olr.locConfirm that the active Grid home points to:
/u01/app/26.4.0/gridDo not proceed if the OLR still references the old Grid home.
3.3 Verify ASM status
ps -ef | grep [a]sm_pmonConnect to ASM:
export ORACLE_HOME=/u01/app/26.4.0/grid export ORACLE_SID=+ASM export PATH=$ORACLE_HOME/bin:$PATH sqlplus / as sysasmCheck ASM instance status:
SELECT instance_name, status FROM v$instance;Check disk group status:
SELECT name, state, type FROM v$asm_diskgroup;Exit SQL*Plus:
EXIT;3.4 Verify Oracle Inventory
cat /etc/oraInst.locCheck registered Oracle homes:
grep -i '26.0.0\|26.4.0' \ /u01/app/oraInventory/ContentsXML/inventory.xml3.5 Check /etc/oratab
cat /etc/oratabCurrent entries may include:
+ASM:/u01/app/26.0.0/grid:N +ASM:/u01/app/26.4.0/grid:NThe active ASM entry must ultimately reference the new Grid home.
3.6 Check whether any processes are using the old home
ps -ef | grep '/u01/app/26.0.0/grid' | grep -v grepAlso check open files:
lsof +D /u01/app/26.0.0/gridIf
lsofis unavailable, install or use an alternative process inspection method.Investigate any remaining processes before proceeding.
4. Deinstallation Check
The following command was previously executed:
/u01/app/26.0.0/grid/deinstall/deinstall -checkonlyThe check reported:
Active GI home:
/u01/app/26.4.0/gridSelected old home:
/u01/app/26.0.0/gridOld home is NOT a configured Grid Infrastructure home.
ASM was not detected in the old home.
This confirms that the old home is not identified as the active Grid Infrastructure configuration.
5. Deinstall Old Grid Home
Log in as the grid user.
Set the old Grid home:
export ORACLE_HOME=/u01/app/26.0.0/grid export PATH=$ORACLE_HOME/bin:$PATHRun the deinstallation utility:
/u01/app/26.0.0/grid/deinstall/deinstallReview all prompts and proposed changes carefully.
Important: If the deinstallation utility proposes removing the active Grid Infrastructure configuration, ASM configuration, OCR/OLR, disk groups, or resources associated with
/u01/app/26.4.0/grid, cancel the operation.Only proceed when the utility is targeting the old home.
Review the deinstallation logs under:
/u01/app/oraInventory/logs/6. Post-Deinstallation Verification
6.1 Verify new Grid home
ls -ld /u01/app/26.4.0/grid6.2 Verify Clusterware services
/u01/app/26.4.0/grid/bin/crsctl check crs6.3 Verify ASM
ps -ef | grep [a]sm_pmonConnect to ASM and check disk groups:
SELECT name, state FROM v$asm_diskgroup;6.4 Verify old Grid home
ls -ld /u01/app/26.0.0/gridConfirm the deinstallation completed successfully and that the old home is no longer registered in Oracle Inventory.
Do not manually delete the old directory if the deinstallation utility has reported errors or left registered components behind.
6.5 Clean up /etc/oratab
After confirming successful deinstallation, remove the obsolete entry:
+ASM:/u01/app/26.0.0/grid:NRetain the active entry:
+ASM:/u01/app/26.4.0/grid:N7. Success Criteria
The activity will be considered successful when:
Old Grid home
26.0.0has been successfully deinstalled.New Grid home
26.4.0remains operational.Clusterware services are running successfully.
ASM instance is running.
All ASM disk groups are mounted and accessible.
Oracle Inventory no longer contains the old Grid home.
/etc/oratabcontains the correct active ASM entry.No database or ASM availability issues are observed.
8. Rollback / Recovery Considerations
This is a deinstallation activity, not a Grid home switch.
If deinstallation fails:
Stop further cleanup activities.
Do not remove the new Grid home.
Do not manually modify OLR or OCR.
Preserve the deinstallation logs.
Investigate Oracle Inventory and the deinstall error messages.
If necessary, reinstall or restore the old software home using the appropriate Oracle installation media and configuration procedures.
Note: Reinstalling the old software home does not automatically restore its previous configuration.
Expected Final State
Component Expected state Old Grid home – 26.0.0 Deinstalled New Grid home – 26.4.0 Active ASM instance Running ASM disk groups Mounted Clusterware Operational Oracle Inventory Old home removed /etc/oratab New home retained
Anuj Singh Oracle DBA
Search This Blog
Total Pageviews
Wednesday, 18 November 2026
Oracle Grid Infrastructure – Deinstallation
Wednesday, 11 November 2026
Patch 40014665 - Grid Infrastructure Release Update Gold Image 23.26.4.0.0
Oracle Grid Infrastructure Installation and Grid Home Switch
Patch 40014665: GI RELEASE UPDATE 23.26.4.0.0 (GOLD IMAGE)
[grid@ora26 ~]$ ls -lh p40014665_230000_Linux-x86-64.zip -rw-r--r--. 1 grid oinstall 1.1G Nov 8 07:38 p40014665_230000_Linux-x86-64.zip [grid@ora26 ~]$
Extract Gold Image | v Prepare new Grid Home (-setupHome) | v Run prerequisite checks | v Switch Grid Home (-switchGridHome) | v Verify Oracle Restart and ASM
1. Overview
This document describes the procedure followed to prepare and switch an existing Oracle Grid Infrastructure (Oracle Restart) installation to a new Grid Home.
Environment details
Parameter
Value
Server
ora26
Operating system
Linux x86-64
Installation type
Oracle Restart (Standalone)
Existing Grid Home
/u01/app/26.0.0/grid
New Grid Home
/u01/app/26.4.0/grid
Software installation user
grid
Installation group
oinstall
ASM disk discovery
/dev/sd*
ASM diskgroup
DATA
2. Prerequisites
Before starting the installation:
Confirm the existing Oracle Grid Infrastructure installation is operational.
Confirm the new Grid Infrastructure installation image has been downloaded.
Ensure sufficient disk space is available for the new Grid Home.
Confirm the Grid user and required operating system groups.
Take an appropriate backup of the existing configuration.
Schedule a maintenance window.
Record the existing ASM configuration, disk groups, SPFILE and password file locations.
Check the existing Grid Infrastructure status:
[grid@ora26 grid]$ grep -E 'oinstall|dba|oper|asmadmin|asmdba|asmoper' /etc/group oinstall:x:54321:oracle dba:x:54322:oracle,grid oper:x:54323:oracle backupdba:x:54324:oracle dgdba:x:54325:oracle kmdba:x:54326:oracle racdba:x:54330:oracle
/u01/app/26.0.0/grid/bin/crsctl check has
/u01/app/26.0.0/grid/bin/crsctl stat res -t
/u01/app/26.0.0/grid/bin/crsctl check has /u01/app/26.0.0/grid/bin/crsctl stat res -t /u01/app/26.0.0/grid/bin/srvctl config asm
check resources crsctl status res | grep -v "^$" | awk -F "=" 'BEGIN {print " "} {printf("%s",NR%4 ? $2"|" : $2"\n")}' | sed -e 's/ *, /,/g' -e 's/, /,/g' | awk -F "|" 'BEGIN { printf "%-40s%-35s%-20s%-50s\n","Resource Name","Resource Type","Target","State" } { split ($3,trg,","); split ($4,st,","); for (i=1; i<=length(trg); i++) { printf "%-40s%-35s%-20s%-50s\n",$1,$2,trg[i],st[i] } }'Check ASM configuration:
su - grid
export ORACLE_HOME=/u01/app/26.0.0/grid
export PATH=$ORACLE_HOME/bin:$PATH
srvctl config asm
srvctl status asm
Check the existing Grid version:
crsctl query has releaseversion
crsctl query has softwareversion
Check Oracle Local Registry location:
cat /etc/oracle/olr.loc
3. Extract the new Grid Infrastructure software
Log in as the Grid Infrastructure software owner.
su - grid
Extract the downloaded installation image into the new Grid Home:
unzip -q /home/grid/p40014665_230000_Linux-x86-64.zip
The target installation directory is: /u01/app/26.4.0/grid
mkdir -p /u01/app/26.4.0/grid [grid@ora26 ~]$ mkdir -p /u01/app/26.4.0/grid [grid@ora26 ~]$ chmod 775 -R /u01/app/26.4.0/grid [grid@ora26 ~]$ chown grid:oinstall -R /u01/app/26.4.0/grid [grid@ora26 ~]$ unzip p40014665_230000_Linux-x86-64.zip -d /u01/app/26.4.0/grid
Check the directory:
ls -ld /u01/app/26.4.0/grid
ls -l /u01/app/26.4.0/grid/gridSetup.sh
[grid@ora26 grid]$ ls -ld /u01/app/26.4.0/grid ls -l /u01/app/26.4.0/grid/bin/crsctl ls -l /u01/app/26.4.0/grid/gridSetup.sh ls -l /u01/app/26.4.0/grid/oui/bin/
4. Configure the new Grid Home environment
Set the environment variables:
export ORACLE_HOME=/u01/app/26.4.0/grid
export LD_LIBRARY_PATH=$ORACLE_HOME/lib
export PATH=$ORACLE_HOME/bin:/usr/bin:/bin
Verify:
echo $ORACLE_HOME
echo $LD_LIBRARY_PATH
echo $PATH
Important: Ensure LD_LIBRARY_PATH does not point to the old Grid Home.
5. Validate the new Grid Home binaries
Check the CRSCTL binary:
ls -l $ORACLE_HOME/bin/crsctl*
If the image contains crsctl.bin, test its dependencies:
ldd $ORACLE_HOME/bin/crsctl.bin
Confirm that Oracle libraries resolve from: /u01/app/26.4.0/grid/lib/
Test the binary:
$ORACLE_HOME/bin/crsctl.bin query has releaseversion
6. Configure the new Grid Home
Run the prerequisite validation:
$ORACLE_HOME/gridSetup.sh \
-setupHomeAs /u01/app/26.0.0/grid \
-executePrereqs
Review the prerequisite results and resolve any reported failures.
Once validation is successful, configure the new Grid Home:
$ORACLE_HOME/gridSetup.sh \
-setupHomeAs /u01/app/26.0.0/grid
Allow the operation to complete successfully. This step uses the existing Grid Home configuration, including the configured operating system groups.
7. Switch the Grid Home
After successful preparation of the new Grid Home, execute:
$ORACLE_HOME/gridSetup.sh -switchGridHome
Follow the installer instructions and execute any required root scripts when prompted. Allow the Grid Home switch operation to complete. Do not manually modify ASM configuration or copy Oracle libraries between Grid Homes.
8. Post-installation validation
After the switch, verify the Grid Infrastructure configuration.
Check the active Grid Home
cat /etc/oracle/olr.loc
Confirm the active Grid Home points to the new installation.
Check Oracle High Availability Services
/u01/app/26.4.0/grid/bin/crsctl check has
Check resource status
/u01/app/26.4.0/grid/bin/crsctl stat res -t
Check Grid Infrastructure version
/u01/app/26.4.0/grid/bin/crsctl query has releaseversion
/u01/app/26.4.0/grid/bin/crsctl query has softwareversion
Check and start ASM status
Verify /etc/oratab entry (+ASM:/u01/app/26.4.0/grid:N), set the environment, and start ASM if not running:
+ASM:/u01/app/26.4.0/grid:N
[grid@ora26 ~]$ . oraenv
ORACLE_SID = [grid] ? +ASM
The Oracle base has been set to /u01/app/grid
[grid@ora26 ~]$ srvctl status asm
ASM is not running.
[grid@ora26 ~]$ srvctl start asm
[grid@ora26 ~]$ srvctl status asm
ASM is running on ora26
[grid@ora26 ~]$
Additional ASM checks:
/u01/app/26.4.0/grid/bin/srvctl status asm
/u01/app/26.4.0/grid/bin/srvctl config asm
Check ASM disk groups
Connect to ASM:
sqlplus / as sysasm
Run:
SELECT name, state, type, total_mb, free_mb
FROM v$asm_diskgroup;
Check listener
/u01/app/26.4.0/grid/bin/srvctl status listener
Check installed patches
/u01/app/26.4.0/grid/OPatch/opatch lsinventory
Confirm the expected software version and patches are present.
9. Troubleshooting encountered during installation
Issue 1: INS-41881 – OSDBA group mismatch
Error: INS-41881: The group specified for OSDBA is not same as the group 'oinstall' retrieved from the current configuration of grid software.
Cause: The OSDBA group selected during installation did not match the existing Grid Infrastructure configuration.
Resolution: Use the -setupHomeAs operation with the existing Grid Home to inherit the existing configuration rather than manually selecting inconsistent groups.
Issue 2: CRSCTL undefined symbol error
Error: undefined symbol: clssgsDumpCSSGrpInfo
Cause: The new CRSCTL executable was loading libraries from the old Grid Home because LD_LIBRARY_PATH pointed to /u01/app/26.0.0/grid/lib.
Resolution:
unset LD_LIBRARY_PATH
export ORACLE_HOME=/u01/app/26.4.0/grid
export LD_LIBRARY_PATH=$ORACLE_HOME/lib
export PATH=$ORACLE_HOME/bin:/usr/bin:/bin
Verify library resolution using ldd $ORACLE_HOME/bin/crsctl.bin. All Oracle libraries should resolve from the new Grid Home.
Issue 3: CRSCTL could not find libhasgen.so
Error: error while loading shared libraries: libhasgen.so: cannot open shared object file
Cause: The library search path was unset without replacing it with the new Grid Home library directory.
Resolution:
export LD_LIBRARY_PATH=$ORACLE_HOME/lib
10. Important operational considerations
Do not delete the old Grid Home immediately after switching.
Retain the old Grid Home until the new installation is fully validated.
Do not copy Oracle libraries manually between Grid Homes.
Do not manually create CRSCTL symlinks.
Do not change ASM disk discovery or ASM SPFILE configuration during the switch.
Verify ASM, disk groups, listener and Oracle Restart resources after completion.
Keep installation logs for audit and troubleshooting purposes.
Follow Oracle's documented rollback procedure if the switch fails.
11. Completion checklist
New Grid Infrastructure software extracted.
New Grid Home environment configured.
CRSCTL binary and library dependencies validated.
Prerequisite checks completed successfully.
-setupHomeAs completed successfully.
-switchGridHome completed successfully.
OLR points to the new Grid Home.
OHAS is online.
ASM is online.
ASM disk groups are mounted.
Listener is online.
Oracle Restart resources are healthy.
OPatch inventory verified.
Old Grid Home retained for rollback until acceptance.
Installation status: Completed successfully on ora26.
Target Grid Home: /u01/app/26.4.0/gridgrep -iE "error|fatal|failed|success" \ /u01/app/oraInventory/logs/installActions2026-11-17_08-49-31AM.log | tail -50 [grid@ora26 grid]$check logfind /u01/app/26.4.0/grid/cfgtoollogs/oui \ -type f -printf '%TY-%Tm-%Td %TH:%TM %p\n' | sortfor d in 09-11-09AM 09-12-35AM 09-15-54AM do echo "===== $d =====" grep -E 'The command passed is:|OSDBA =|OSASM =|OSOPER =|INS-41881|INS-04008' \ /u01/app/26.4.0/grid/cfgtoollogs/oui/GridSetupActions2026-11-17_${d}/gridSetupActions2026-11-17_${d}.log done[root@ora26 ~]# /u01/app/26.4.0/grid/root.sh Performing root user operation. The following environment variables are set as: ORACLE_OWNER= grid ORACLE_HOME= /u01/app/26.4.0/grid Enter the full pathname of the local bin directory: [/usr/local/bin]: The contents of "dbhome" have not changed. No need to overwrite. The contents of "oraenv" have not changed. No need to overwrite. The contents of "coraenv" have not changed. No need to overwrite. Entries will be added to the /etc/oratab file as needed by Database Configuration Assistant when a database is created Finished running generic part of root script. Now product-specific root actions will be performed. Executing command '/u01/app/26.4.0/grid/perl/bin/perl -I/u01/app/26.4.0/grid/perl/lib -I/u01/app/26.4.0/grid/crs/install /u01/app/26.4.0/grid/crs/install/roothas.pl -dstcrshome /u01/app/26.4.0/grid -prepatch ' Using configuration parameter file: /u01/app/26.4.0/grid/crs/install/crsconfig_params The log of current session can be found at: /u01/app/grid/crsdata/ora26/crsconfig/hapatch_2026-11-17_11-03-09AM.log 2026/11/17 11:03:36 CLSRSC-347: Successfully unlock /u01/app/26.4.0/grid 2026/11/17 11:03:36 CLSRSC-671: Pre-patch steps for patching GI home successfully completed. Executing command '/u01/app/26.4.0/grid/perl/bin/perl -I/u01/app/26.4.0/grid/perl/lib -I/u01/app/26.4.0/grid/crs/install /u01/app/26.4.0/grid/crs/install/roothas.pl -dstcrshome /u01/app/26.4.0/grid -postpatch ' Using configuration parameter file: /u01/app/26.4.0/grid/crs/install/crsconfig_params The log of current session can be found at: /u01/app/grid/crsdata/ora26/crsconfig/hapatch_2026-11-17_11-03-37AM.log 2026/11/17 11:04:00 CLSRSC-329: Replacing Clusterware entries in file 'oracle-ohasd.service' 2026/11/17 11:04:25 CLSRSC-672: Post-patch steps for patching GI home successfully completed. [root@ora26 ~]# ps -ef|grep -i asm grid 23462 23436 7 10:59 pts/2 00:00:38 /u01/app/26.4.0/grid/jdk/bin/java -cp /u01/app/26.4.0/grid/install/jlib/installcommons_1.0.0b.jar:/u01/app/26.4.0/grid/install/jlib/instcommon.jar:/u01/app/26.4.0/grid/install/jlib/instcrs.jar:/u01/app/26.4.0/grid/install/jlib/pilot_1.0.0b.jar:/u01/app/26.4.0/grid/install/jlib/instdb.jar:/u01/app/26.4.0/grid/install/jlib/instclient.jar:/u01/app/26.4.0/grid/install/jlib/instgsm.jar:/u01/app/26.4.0/grid/install/jlib/invctl-common-lib.jar:/u01/app/26.4.0/grid/install/jlib/invctl-inventory-api.jar:/u01/app/26.4.0/grid/install/jlib/invctl-inventory-plugins.jar:/u01/app/26.4.0/grid/jlib/cvu.jar:/u01/app/26.4.0/grid/jlib/srvmhas.jar:/u01/app/26.4.0/grid/jlib/commons-compress.jar:/u01/app/26.4.0/grid/jlib/commons-io.jar:/u01/app/26.4.0/grid/jlib/commons-lang3.jar:/u01/app/26.4.0/grid/jlib/commons-codec.jar:/u01/app/26.4.0/grid/jlib/srvmasm.jar:/u01/app/26.4.0/grid/jlib/gns.jar:/u01/app/26.4.0/grid/jlib/srvm.jar:/u01/app/26.4.0/grid/jlib/oraclepki.jar:/u01/app/26.4.0/grid/jlib/mgmtca.jar:/u01/app/26.4.0/grid/jlib/mgmtua.jar:/u01/app/26.4.0/grid/jlib/clscred.jar:/u01/app/26.4.0/grid/jlib/oracle.dbtools-common.jar:/u01/app/26.4.0/grid/jlib/jmxspi.jar:/u01/app/26.4.0/grid/jlib/emca.jar:/u01/app/26.4.0/grid/jlib/jackson-annotations.jar:/u01/app/26.4.0/grid/jlib/jackson-core.jar:/u01/app/26.4.0/grid/jlib/jackson-databind.jar:/u01/app/26.4.0/grid/jlib/jaxb-api.jar:/u01/app/26.4.0/grid/jlib/jaxb-core.jar:/u01/app/26.4.0/grid/jlib/jaxb-impl.jar:/u01/app/26.4.0/grid/lib/jakarta.activation.jar:/u01/app/26.4.0/grid/lib/activation.jar:/u01/app/26.4.0/grid/jlib/entityManager_proxy.jar:/u01/app/26.4.0/grid/jlib/javax.security.jacc_1.0.0.0_1-1.jar:/u01/app/26.4.0/grid/jlib/orai18n-collation.jar:/u01/app/26.4.0/grid/jlib/orai18n-mapping.jar:/u01/app/26.4.0/grid/jlib/orai18n-utility.jar:/u01/app/26.4.0/grid/jlib/orai18n-translation.jar:/u01/app/26.4.0/grid/jlib/jwc-cred.jar:/u01/app/26.4.0/grid/jlib/AHFInstall.jar:/u01/app/26.4.0/grid/jlib/netcfg.jar:/u01/app/26.4.0/grid/jlib/slf4j-api.jar:/u01/app/26.4.0/grid/jlib/slf4j-jdk14.jar:/u01/app/26.4.0/grid/jlib/sshd-cli.jar:/u01/app/26.4.0/grid/jlib/sshd-common.jar:/u01/app/26.4.0/grid/jlib/sshd-mina.jar:/u01/app/26.4.0/grid/jlib/sshd-core.jar:/u01/app/26.4.0/grid/jlib/sshd-sftp.jar:/u01/app/26.4.0/grid/jlib/ewt3.jar:/u01/app/26.4.0/grid/jlib/help-share.jar:/u01/app/26.4.0/grid/jlib/jewt4.jar:/u01/app/26.4.0/grid/jlib/ohj.jar:/u01/app/26.4.0/grid/jlib/olaf2.jar:/u01/app/26.4.0/grid/jlib/oracle_ice.jar:/u01/app/26.4.0/grid/jlib/share.jar:/u01/app/26.4.0/grid/jlib/ojmisc.jar:/u01/app/26.4.0/grid/lib/xml.jar:/u01/app/26.4.0/grid/lib/xmlparserv2.jar:/u01/app/26.4.0/grid/jdbc/lib/ojdbc8.jar:/u01/app/26.4.0/grid/OPatch/jlib/opatchsdk.jar:/u01/app/26.4.0/grid/OPatch/jlib/opatch.jar:/u01/app/26.4.0/grid/oui/jlib/OraPrereqChecks.jar:/u01/app/26.4.0/grid/oui/jlib/prov_fixup.jar:/u01/app/26.4.0/grid/oui/jlib/OraPrereq.jar:/u01/app/26.4.0/grid/oui/jlib/InstHelp.jar:/u01/app/26.4.0/grid/oui/jlib/InstHelp_de.jar:/u01/app/26.4.0/grid/oui/jlib/InstHelp_es.jar:/u01/app/26.4.0/grid/oui/jlib/InstHelp_fr.jar:/u01/app/26.4.0/grid/oui/jlib/InstHelp_it.jar:/u01/app/26.4.0/grid/oui/jlib/InstHelp_ja.jar:/u01/app/26.4.0/grid/oui/jlib/InstHelp_ko.jar:/u01/app/26.4.0/grid/oui/jlib/InstHelp_pt_BR.jar:/u01/app/26.4.0/grid/oui/jlib/InstHelp_zh_CN.jar:/u01/app/26.4.0/grid/oui/jlib/InstHelp_zh_TW.jar:/u01/app/26.4.0/grid/oui/jlib/InstImages.jar:/u01/app/26.4.0/grid/oui/jlib/OraCheckPoint.jar:/u01/app/26.4.0/grid/oui/jlib/OraInstaller.jar:/u01/app/26.4.0/grid/oui/jlib/OraInstallerNet.jar:/u01/app/26.4.0/grid/oui/jlib/OraSuiteInstaller.jar:/u01/app/26.4.0/grid/oui/jlib/com.oracle.glcm.patch.opatch-common-api-interfaces_13.9.5.0.jar:/u01/app/26.4.0/grid/oui/jlib/com.oracle.glcm.patch.opatch-common-api-schema_13.9.5.0.jar:/u01/app/26.4.0/grid/oui/jlib/com.oracle.glcm.patch.opatch-common-api_13.9.5.0.jar:/u01/app/26.4.0/grid/oui/jlib/emCfg.jar:/u01/app/26.4.0/grid/oui/jlib/filesList.jar:/u01/app/26.4.0/grid/oui/jlib/oneclick.jar:/u01/app/26.4.0/grid/oui/jlib/oui.jar -XX:-OmitStackTraceInFastThrow -XX:CompileCommand=quiet -XX:CompileCommand=exclude,javax/swing/text/GlyphView,getBreakSpot -Doracle.installer.library_loc=/u01/app/26.4.0/grid/oui/lib/linux64 -Djava.io.tmpdir=/tmp/GridSetupActions2026-11-17_10-59-07AM -Doracle.installer.timestamp=2026-11-17_10-59-07AM -Doracle.installer.tempLogDir=/tmp/GridSetupActions2026-11-17_10-59-07AM -Doracle.installer.scratchPath=/tmp/GridSetupActions2026-11-17_10-59-07AM/scratch -Djdk.module.illegalAccess=deny -DORACLE_HOME=/u01/app/26.4.0/grid -DCVU_OS_SETTINGS=SHELL_NOFILE_SOFT_LIMIT:1024,SHELL_STACK_SOFT_LIMIT:8192,SHELL_UMASK:0022 -Xms150m -Xmx2048m -Xdebug oracle.install.ivw.crs.driver.CRSConfigWizard -printtime ORACLE_HOME=/u01/app/26.4.0/grid -switchGridHome root 28060 3042 0 11:07 pts/0 00:00:00 grep --color=auto -i asm [root@ora26 ~]# ps -ef|grep -i smon root 28063 3042 0 11:07 pts/0 00:00:00 grep --color=auto -i smon [root@ora26 ~]#/u01/app/26.4.0/grid/OPatch/opatch lspatches 38743682;MICRONAUT RELEASE UPDATE 23.26.1.0.0 (GOLD IMAGE) (38743682) Gold Image 38743695;RHP RELEASE UPDATE 23.26.1.0.0 (GOLD IMAGE) (38743695) Gold Image 38743706;ACFS RELEASE UPDATE 23.26.1.0.0 (GOLD IMAGE) (38743706) Gold Image 38743688;OCW RELEASE UPDATE 23.26.1.0.0 (GOLD IMAGE) (38743688) Gold Image 38743669;Database Release Update : 23.26.1.0.0 (38743669) Gold Image OPatch succeeded.
after switch /u01/app/26.4.0/grid/bin/srvctl config asm ASM is running on ora26 ASM home: <CRS home> Password file: +DATA/orapwasm Backup of Password file: ASM listener: LISTENER Spfile: +DATA/ASM/ASMPARAMETERFILE/registry.253.1248964561 ASM diskgroup discovery string: /dev/sd*
Patch 40014665: GI RELEASE UPDATE 23.26.4.0.0 (GOLD IMAGE)
[grid@ora26 ~]$ ls -lh p40014665_230000_Linux-x86-64.zip -rw-r--r--. 1 grid oinstall 1.1G Nov 8 07:38 p40014665_230000_Linux-x86-64.zip [grid@ora26 ~]$Patch 40014665 - Grid Infrastructure Release Update Gold Image 23.26.4.0.0
This document is accurate at the time of release. For any changes and additional information regarding Grid Infrastructure Release Update Gold Image 23.26.4.0.0, see these related documents that are available at My Oracle Support (
http://support.oracle.com/):
Document KB929627 Oracle AI Database 23.26.4.0.0 Known Issues
This document includes the following sections:
1 Patch Information
Grid Infrastructure Release Update 23.26.4.0.0 patches are cumulative. That is, the content of all previous Grid Infrastructure bundles is included in the latest Grid Infrastructure bundle patch.
This GIRU contains the following CORE DST patches:
| Patch Numbers | Patches |
|---|---|
| 36260493 | DSTV43 UPDATE - TZDATA2024A |
| 37537949 | DSTV44 UPDATE - TZDATA2025A |
| 39070269 | DSTV45 UPDATE - TZDATA2026A |
| 39938301 | DSTV46 UPDATE - TZDATA2026B & TZDATA2026C |
2 Prerequisites
To ensure there is enough space available, out-of-place patching adds a new Oracle home next to the existing Oracle home. For further information, refer to My Oracle Support document KB137807 How to Perform ORACLE_HOME Backup?.
For opatch utility, refer to Oracle document Single-Instance Oracle Database Maintenance with OPatch.
3 Installation
These instructions are for all Oracle AI Database installations.
Before you install Grid Infrastructure Release Update 23.26.4.0.0, refer to document KB135057 How to Use the My Oracle Support Conflict Checker Tool for Patches Installed with OPatch for additional information on how to check the environment and how to detect and resolve any interim patch conflicts.
You can install Oracle Grid Infrastructure Patch in one of two ways:
Patch Installation Instructions for Grid Home Using Oracle FPP
Patch Installation Instructions for Grid Home Using gridSetup
3.1 Patch Installation Instructions for Grid Home Using Oracle FPP
To prepare for the software update, download the Oracle Fleet Patching and Provisioning (Oracle FPP) Gold Image:
Download the Gold Image that you have built to your system. As Grid user, deploy a new target software home using the following Oracle FPP command:
$ cd <gi_home>/bin
$ rhpctl deploy home -path dest_path -zip gold_image.zipWhere
dest_pathis the destination path for the new empty pre-created directory for the new Grid home, andgold_imageis the image name.Run precheck for the Apply software update. To prevent issues during the patch operation, run a precheck evaluation for moving Oracle Grid Infrastructure to the new software home using the following Oracle FPP command:
$ rhpctl move gihome -eval -sourcehome gi_home -desthome dest_pathWhere
gi_homeis the source Grid home anddest_pathis the target Grid home.For details about the
move ... -evalcommand options for Oracle Grid Infrastructure, refer to the Oracle Fleet Patching and Provisioning Administrator's Guide.Apply the RU update, moving the Oracle Grid Infrastructure to the new home. Move Oracle Grid Infrastructure to the new software home using the following Oracle FPP command:
$ rhptl move gihome -sourcehome gi_home -desthome dest_pathWhere
gi_homeis the source Grid home anddest_pathis the target Grid home.For Oracle RAC environments, refer to the instructions in the Oracle AI Database Recommended Patch Maintenance for Oracle Real Application Clusters.
3.2 Patch Installation Instructions for Grid Home Using gridSetup
Create a new directory for the Target Grid Home on Node 1.
Download and unzip the Gold Image file
p40014665_230000_Linux-x86-64.zipto the Target Grid Home directory<TARGET_GRID_HOME>on Node 1. This directory must be empty and cannot be/tmp.The directory should have read permission for the
ORA_INSTALLgroup.Run the following commands:
$ cd <TARGET_GRID_HOME>
$ unzip p40014665_230000_Linux-x86-64.zipTo install software only on Grid home, run:
$ <TARGET_GRID_HOME>/gridSetup.shTo switch the Grid services from the source home to the target home, run:
$ <TARGET_GRID_HOME>/gridSetup.sh -switchgridhome
4 Deinstallation
These instructions apply if you need to deinstall the patch.
You can deinstall Oracle Grid Infrastructure Patch in one of two ways:
Patch Deinstallation Instructions for Grid Home Using Oracle FPP
Patch Deinstallation Instructions for Grid Home Using gridSetup
4.1 Patch Deinstallation Instructions for Grid Home Using Oracle FPP
To deinstall Grid home, run the following command:
$ <grid_home>/bin/rhpctl move gihome -sourcehome source_home -desthome dest_path
Where dest_path is the recently patched Grid home and source_home is the original Grid home to where you want to move the GI stack back to. (Note: This is applicable after a successful Grid Infrastructure patch has been done and you want to rollback to the previous Grid home.)
For Oracle Real Application Clusters database patch rollback, refer to document Oracle AI Database Recommended Patch Maintenance for Oracle Real Application Clusters.
5 Known Issues
For information about OPatch issues, see My Oracle Support document KB133615 Primary Note For OPatch.
For issues documented after the release of this patch, see My Oracle Support document KB929627 Oracle AI Database 23.26.4.0.0 Known Issues.
6 References
The following documents are references for this patch.
Document KB929627 Oracle AI Database 23.26.4.0.0 Known Issues.
7 Bugs Fixed by This Patch
See My Oracle Support document KB781900 Database 26ai Release Updates Bugs Fixed Lists for the list of bugs fixed in this patch.
8 Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id-docacc.
Access to Oracle Support
Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Oracle DBA
anuj blog Archive
- ► 2011 (362)
