Skip to main content

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-12-02 17:00:49.576 AST ] [UsmcaLogger.logException:158] oracle.sysman.assistants.util.sqlEngine.SQLFatalErrorException: ORA-27122: unable to protect memory

oracle.sysman.assistants.util.sqlEngine.SQLEngine.executeImpl(SQLEngine.java:1713)
oracle.sysman.assistants.util.sqlEngine.SQLEngine.startup(SQLEngine.java:2146)
oracle.sysman.assistants.usmca.backend.USMInstance.configureLocalASM(USMInstance.java:3155)
oracle.sysman.assistants.usmca.service.UsmcaService.configureLocalASM(UsmcaService.java:1012)
oracle.sysman.assistants.usmca.model.UsmcaModel.performConfigureLocalASM(UsmcaModel.java:951)
oracle.sysman.assistants.usmca.model.UsmcaModel.performOperation(UsmcaModel.java:814)
oracle.sysman.assistants.usmca.Usmca.execute(Usmca.java:213)
oracle.sysman.assistants.usmca.Usmca.main(Usmca.java:503)
[main] [ 2020-12-02 17:00:49.576 AST ] [UsmcaLogger.logInfo:128] ASM failed to start. Check /u01/app/grid/cfgtoollogs/asmca/asmca-201202PM050039.log for details.
[main] [ 2020-12-02 17:00:49.577 AST ] [UsmcaLogger.logInfo:128] Instance running false
[main] [ 2020-12-02 17:00:49.577 AST ] [UsmcaLogger.logInfo:128] ASM failed to start. Check /u01/app/grid/cfgtoollogs/asmca/asmca-201202PM050039.log for details.

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


Cause of the Error:

This is due to the known bug on 12.1.0 as per the Oracle Note. 2118379.1

The issue is addressed in unpublished
Bug 22500861 - CONSOLIDATE TXN FOR LARGE PAGESIZE SUPPORT OSM

The bug is fixed in 12.1.0.2.

As per bug report, the database start up failure was due to OSM (Optimized Shared Memory) segment. There were some transactions missing in 12.1.0.1 with respect to Solaris OS which leads to this failure. It will affect Solaris 11 latest updates.


SOLUTION

To solve the issue, use any of below alternatives:

  • Apply patch set 12.1.0.2

    - OR -

  • Apply interim patch 22500861, if available for your platform and Oracle version.

Cancel the GI installer, then apply the patch on both nodes
after the patches are successfully installed, perform the below steps to clean up and restart the configuration


1. cd $GI_HOME/crs/install/

./rootcrs.pl -deconfig -force 

Run this clean up on both nodes

2. Re-run the Configuration from vnc

cd /u01/app/12.1.0/grid_1/crs/config

./config.sh 


This will successfully complete the GI Installation 

Comments

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                                        ...

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 =============...