Exadata Deployment[Solaris] With OneCommand Fails At Step 16 [Gridrootscripts] (Doc ID 1388177.1)

Last updated on AUGUST 04, 2014

Applies to:

Oracle Exadata Hardware - Version and later
Information in this document applies to any platform.
***Checked for relevance on 04-Aug-2014***


Exadata installation (Solaris OS) via onecommand fails at step 16 (GridRootScripts)

./deploy112.sh -s 16

The error message is as follows and it is due to ASM could not start.
Reviewing the relevant logs and identifying information

<logs have been trimmed to relevant sections only >

INFO: Logging all actions in /opt/oracle.SupportTools/onecommand/tmp/STEP-16-20111220123021.log and traces in /opt/oracle.SupportTools/onecommand/tmp/STEP-16-20111220123021.trc
INFO: Loading configuration file /opt/oracle.SupportTools/onecommand/onecommand.params...
INFO: Creating nodelist files...
INFO: 2011-12-20 12:30:21
INFO: Step 16 GridRootScripts
INFO: Validating VIP's...
SUCCESS: VIP ex0101-vip is not on the network. Check passed
SUCCESS: VIP ex0102-vip is not on the network. Check passed
INFO: Time spent in step 16 GridRootScripts is 4 seconds.
ERROR: unable to locate string 'Configure Oracle Grid Infrastructure for a Cluster ... succeeded' in output file /u01/app/; COUNT=0 #Step 16#
INFO: Time spent in step 16 GridRootScripts is 198 seconds.

The ASM log

SQL*Plus: Release Production

[main] [ 2011-12-20 12:32:03.372 MYT ] [OracleHome.getVersion:1019] Current version from sqlplus:
[main] [ 2011-12-20 12:32:03.372 MYT ] [UsmcaLogger.logInfo:142] Role SYSASM
[main] [ 2011-12-20 12:32:03.372 MYT ] [UsmcaLogger.logInfo:142] OS Auth true
[main] [ 2011-12-20 12:32:03.766 MYT ] [SQLEngine.done:2167] Done called
[main] [ 2011-12-20 12:32:03.766 MYT ] [USMInstance.configureLocalASM:3057] ORA-27102: out of memory


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms