Environment: Current Database: Oracle Restart Database 19.14 (Standalone Grid Infrastructure) Operating System : AIX 7.3 64 Bit Error: CRS-6706: Oracle Clusterware Release patch level ('1211422631') does not match Software patch level ('2018016837'). Oracle Clusterware cannot be started. CRS-4000: Command Start failed, or completed with errors. Change: Oracle 19.25 Grid Patches were applied to GRID HOME. Issue Description: There were no errors in Patching log file. Patches were applied successfully to the GRID HOME. When tried to lock the GRID HOME binaries after patching activity, HAS was failed to start with above error messages. After patching activiyt, by root user, below lock comamnd was executed. root@testdb:/u01/app/grid/19.0.0/grid/crs/install >ls -ltr *root*.sh -rwxr-x--- 1 grid oinstall 8051 Jun 19 17:20 rootcrs.sh -rwxr-x--- 1 grid oinstall 3931 Jun 19 17:20 roothas.sh root@testdb:/u01/app/grid/19.0.0/grid/crs/install >./roothas.sh -lock Using configuration parameter file: /u01/app/grid/19.0.0/grid/crs/install/crsconfig_params The log of current session can be found at: /u01/app/grid/crsdata/testdb/crsconfig/halock__2025-06-23_12-04-35AM.log 2025/06/23 12:04:36 CLSRSC-329: Replacing Clusterware entries in file '/etc/inittab' When checked, the PMON and d.bin processes were not started automatically. grid@testdb:/home/grid >ps -ef | grep pmon grid 6160860 22872420 0 12:05:08 pts/0 0:00 grep pmon grid@testdb:/home/grid >ps -ef | grep d.bin grid 25821454 22872420 0 12:05:12 pts/0 0:00 grep d.bin Then, tried to start HAS manually and below error messages were observed. grid@testdb:/home/grid >./crsctl start has CRS-6706: Oracle Clusterware Release patch level ('1211422631') does not match Software patch level ('2018016837'). Oracle Clusterware cannot be started. CRS-4000: Command Start failed, or completed with errors. Solution: Step 1: Execute below command to fix the issue. root@testdb:> cd /u01/app/grid/19.0.0/grid/bin root@testdb:/u01/app/grid/19.0.0/grid/bin >./clscfg -localpatch clscfg: EXISTING configuration version 0 detected. Creating OCR keys for user 'root', privgrp 'system'.. Operation successful. Step 2: Now try to start HAS service by grid user. You can see now DB and ASM are started successfully. grid@testdb:/home/grid >crsctl start has CRS-4123: Oracle High Availability Services has been started. grid@testdb:/home/grid >ps -ef | grep pmon grid 25821606 1 0 12:11:59 - 0:00 asm_pmon_+ASM grid 29294998 22872442 0 12:12:26 pts/0 0:00 grep pmon grid 33358106 1 0 12:12:22 - 0:00 ora_pmon_oemdb Login as oracle user and check the DB status: root@testdb:/u01/app/grid/19.0.0/grid/bin >su - oracle oracle@testdb:/home/oracle >sqlplus / as sysdba SQL*Plus: Release 19.0.0.0.0 - Production on Mon Jun 23 12:14:29 2025 Version 19.14.1.0.0 Copyright (c) 1982, 2021, Oracle. All rights reserved. Connected to: Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production Version 19.14.1.0.0 SQL> select name,open_mode from v$database; NAME OPEN_MODE --------- ------------ OEMDB READ WRITE |
Thanks for reading this post ! Please comment if you like this post ! Click FOLLOW to get future blog updates !
Thank you for visiting my blog ! Thanks for your comment !