cancel
Showing results for 
Search instead for 
Did you mean: 

sapinst database instance RAC on ASM

nicola_blasi
Active Participant
0 Kudos

Hy

i'm installing a database instance on oracle 11.2.0.4.5 RAC on ASM with GRID.

We have two nodes . Grid is installed each node in local while oracle 11204 is shared .

Both database are patched with last bundle and grid patches .

During the sapinst installation we have the following problem when it asked us the database grid software parameters:

after inserting the right oracle home it goes in error:

Database Instance( Last error reported by the step: Assertion failed: OraQuery3 constructor: Argument context has to be a valid OraSqlContext.)

Analyzing the sapinst_dev.log i think to have found the probably error :

******************

NWUsers.getAccountData(): {

  role:ORACLE

  type:USER

  systems:os

  id:

  name:oracle

  comment:Oracle System Administrator

  home:/oracle/ORAGRID

  shell:/bin/csh

  privileges:

  exists:false

  client:

  host:undefined

  instancenumber:undefined

  locked:false

  chownHomeDir:true

  password:XXXXXX

  groups:oinstall,sapinst,dba,oper,asmoper,asmdba,asmadmin

}

TRACE      2015-03-27 14:53:06.705

OraCom(selectASMDiskGroup() start: false

TRACE      2015-03-27 14:53:06.705

T_ORAASMDG.remove(WHERE 1=1)

ERROR      2015-03-27 14:53:06.705 [CInstallerCallBackImpl.cpp:228]

CJS-00030  Assertion failed: OraQuery3 constructor: Argument context has to be a valid OraSqlContext.

TRACE      2015-03-27 14:53:06.705 [JSExtension.hpp:145]

           JSExceptionHandler::setJSException()

Member function 'Installer.abortInstallation()' has thrown ESAPinstException. Converting to JavaScript exception EJS::Exception.

*********************

i think the problem is the following:

Grid and DB were installed with user oragrid and not with oracle user.

Anyway it should create that user or not...Do you think is this the problem? Is it some workaround to solve this problem?

Thanks

Nick

Accepted Solutions (1)

Accepted Solutions (1)

nicola_blasi
Active Participant
0 Kudos

Hi

The problem occurs because grid and oracle engine were installed using a different user instead of "oracle" that is mandatory for SAP.

Anyway we have bypassed the problem in this manner.

First of all we changed the keydb.xml from "error" to "ok" to go next step ...after putting all informations requested in other slides , the database instance installation starts creating the user oracle with defined associated groups.

We stopped the installation after create users step, and restart from scratch the entire database instance. Sapinst, finding the user oracle, it passed the step descripted in the main message doing the select on oracle grid and go on. Obviously , you can create the user oracle before all the installations.

This is not enough ....to avoid "permission denied" during installation it was very useful the oss note

1915317 - Migrating Software Owner to 'oracle'

that calls the note where scripts are

1983457 - Oracle Home Cloning on Unix and Linux  .


This is only a workaround when you are in a customer where who manages unix doesn't want have to do with SAP rules and SAP technic specific.

Thanks

Nick

former_member185954
Active Contributor
0 Kudos

Hello Nicola,

We managed to avoid this issue by pushing our DBA team to quit their standards and create a new standard in order for us to use 'oracle' as username for installation of Grid

Regards,

Siddhesh

Answers (1)

Answers (1)

0 Kudos

Hello Nicola,

"Assertion failed" errors come out when configurations are different from what they should be. According to Note 1977393 the setup of Oracle RAC is now integrated in SWPM, probably in your scenario some steps were done manually.

The best option is to follow Note 1977393 and the installation guide, there are specific sections for Oracle ASM. To make an example, oracle user is created by SWPM.

Regards,

Valerio