Skip to main content

Grid Patching fails to start CRS

 

Latest CPU Patching on the 19c Grid home fails with below errors:


OPATCHAUTO-68061: The orchestration engine failed.

OPATCHAUTO-68061: The orchestration engine failed with return code 1

OPATCHAUTO-68061: Check the log for more details.

OPatchAuto failed.

Also it mentions to solve the issue and do opathauto resume. 


Solution:

Verify the patches have been applied on both the nodes:

cd /u01/app/19.3.0/grid/bin


 [root@DC2-GTDB-V-01 bin]# ./kfod op=patches

---------------

List of Patches

===============

29340594

32218454

32218663

32222571

32240590

[root@DC2-GTDB-V-01 bin]#


[root@DC2-GTDB-V-02 bin]# ./kfod op=patches

---------------

List of Patches

===============

29340594

32218454

32218663

32222571

32240590

[root@DC2-GTDB-V-02 bin]# 


The perform the following steps 

as root

cd $GI_HOME/bin


clscfg -localpatch

clscfg -patch


After this restart the CRS and verify if its started properly.

Comments

Post a Comment

Popular posts from this blog

RW-50010: Error: - script has returned an error: 2 (Executing cr9idata.pl) During R12.2 Installation on Oracle Linux 8

Problem Faced below error while Installing 12.2 on Linux 8. Unable to execute cr9idata.pl Executing cr9idata.pl Executing: perl /u01/oracle/DEV/12.1.0/nls/data/old/cr9idata.pl Unable to execute cr9idata.pl RW-50010: Error: - script has returned an error:   2 RW-50004: Error code received when running external process.  Check log file for details. Running Database Install Driver for DEV instance Solution: I have installed the following rpms: Install the following rpm  [root@dev02 DEV_dev2]# yum list perl-File-CheckTree* Available Packages perl-File-CheckTree.noarch                                                                         4.42-303.el8                                        ...
1 comment
Read more

Health Check Script

Oracle Database Health Check Script Run this script has sysdba user or any user having DBA Role Change the spool file patch to correct directory. In this example it is set to  /export/home/oraprod/ $ cat Health_Check_Script.sql set pagesize 1100 SET MARKUP HTML ON SPOOL ON spool /export/home/oraprod/health_check_new.html set feedback off set linesize 200; set pages 50 set lines 1000 set pages 70 set heading on PROMPT================================================================ prompt PROMPT PROMPT Daily_Monitoring Checkup Report prompt ================================================================================================================================================= PROMPT REPORT DATE select to_char(sysdate,'DD-MON-YYYY:HH:MI:SS') "Report Run Date" from dual; prompt DATABASE NAME PROMPT ============== select instance_name,host_name,version,status from gv$instance ,v$database a; PROMPT DATABASE INFO PROMPT =============...
1 comment
Read more

12.1.0 Grid Installation on Solaris 11.3 fails with ASM failed to start

Issue Description  We faced one issue, while installing the GI 12.1.0.1.0 on Solaris 11.3  ASM failed to start. Check /u01/app/grid/cfgtoollogs/asmca/asmca-201202PM061908.log for details. 2020/12/02 18:19:17 CLSRSC-184: Configuration of ASM failed 2020/12/02 18:19:17 CLSRSC-258: Failed to configure and start ASM Died at /u01/app/12.1.0/grid_1/crs/install/crsinstall.pm line 1976. The command '/u01/app/12.1.0/grid_1/perl/bin/perl -I/u01/app/12.1.0/grid_1/perl/lib -I/u01/app/12.1.0/grid_1/crs/install /u01/app/12.1.0/grid_1/crs/install/rootcrs.pl ' execution failed This error is coming during root.sh execution on primary node. After checking the asmca logs, the error seen is as below: ========================== [main] [ 2020-12-02 17:00:49.575 AST ] [UsmcaLogger.logException:156] SEVERE:method oracle.sysman.assistants.usmca.backend.USMInstance:configureLocalASM [main] [ 2020-12-02 17:00:49.575 AST ] [UsmcaLogger.logException:157] ORA-27122: unable to protect memory [main] [ 2020-1...
Post a Comment
Read more