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

Post a Comment

Popular posts from this blog

Warning Message When Creating A Keystore

  Warning Message When Creating A Keystore When we try to list the contents of the keystore, using the below command, keytool -list -v -keystore adkeystore.dat Enter keystore password: Keystore type: JKS Keystore provider: SUN Your keystore contains 1 entry Alias name: prod_apps002 Creation date: Jan 26, 2012 Entry type: PrivateKeyEntry Certificate chain length: 1 Certificate[1]: Owner: CN=PROD_apps002, OU=apps, O=apps002, C=US Issuer: CN=PROD_apps002, OU=apps, O=apps002, C=US Serial number: 4f208085 Valid from: Thu Jan 26 01:21:57 AST 2012 until: Tue Jan 16 01:21:57 AST 2052 Certificate fingerprints:          MD5:  XX: XX XX XX          SHA1:  XX: XX XX XX          SHA256:  XX: XX XX XX Signature algorithm name: SHA1withDSA Subject Public Key Algorithm: 1024-bit DSA key Version: 3 ******************************************* ******************************************* Warning: The JKS keystore...
Post a Comment
Read more

CLEARING an ADOP patching session

In some case adop prepare phase fails due to some issues and if you wish to apply any patch in hotpatch mode, it will fail with below errors [STATEMENT] There is already a session which is incomplete. Details are: [STATEMENT]     Session Id: 2 [STATEMENT]     Prepare phase status: R [STATEMENT]     Apply phase status: N [STATEMENT]     Cutover  phase status: N [STATEMENT]     Abort phase status: N [STATEMENT]     Session status: F [ERROR]     Cannot apply hotpatch as another online patching cycle is going on [ERROR]     Unrecoverable error occured. Exiting the current session. [STATEMENT] [START 2019/10/22 16:13:00] Unlocking sessions table [STATEMENT] [END   2019/10/22 16:13:00] Unlocking sessions table [STATEMENT] Log file: /adop_20191022_161221.log [STATEMENT] [START 2019/10/22 16:13:02] Unlocking sessions table [STATEMENT] [E...
4 comments
Read more

XX_XXXXXXX is not a valid responsibility for the current user. Please contact your System Administrator.

  XX_XXXXXXX is not a valid responsibility for the current user. Please contact your System Administrator. Issue : When user logs into EBS, he gets the following Error :  xx_XXXXX  is not a valid responsibility for the current user. Please contact your System Administrator. Solution: 1. Check if the responsibility is end dated.  Extend the end-date if required and try to login again.  2. Check the profile option  Applications Start Page for the user ( User Level). If there is any value defined, remove it and save it. Try to login again and it worked in our case.  Before: After:
Post a Comment
Read more