SAP Database installation on Oracle ASM database

[#1]

Hi Experts,

I have successfully installed the oracle software 11g of oracle ASM database and its been installed as per my previous oracle softwares with oracle:oinstall user and group.

Now I am installing the DB instance before that I am performing ASM preparation. As a part of that I have choseen the general options ->

oracle-> DB tools->

RAC/ASM/EXadata database isntance preparation ABAP - Kernel 7.4X ->

Database identification section given the new DB sid and selected the single instance on Oracle ASM ->

DB administration (OS User) password given ->

home directory somehow choosen as /home/orasid - but changed manually it to /home/oracle/ but we do not have any user called orasid in server. we have only oracle and sidadm of system.

we have started installing with root user but really wondering how it got it picked up orasid. 

Apart from this in SWPM Sp08 there is one option to choose to install with orasid/oracle - so we can choose with oracle but in SWPM SP17 there is no option such like this.

We cant use SWPM SP08 as we need Kernel 7.4X which was not appearing in SWPM SP8.

Kindly suggest me here ?

Your kind help much appreciated.

Thanks

Pavan

[Former Member]

Okay. In our scenario, we have already installed the oracle software with oracle user id. Now we are performing with ASM preparation with SWPM-root user id.

We wanted SWPM to provide us the option to perform the activity w with oracle user id which is not and automatically picked up orasid user.  Due to this reason we got to change permissions of /oracle/home.

Now again I am confused, we should use root user id for ASM preparation and DB instance instillation. But SWPM has some issue 

[Former Member]

we have already installed the oracle software with oracle user id.

I guess you mean you have installed GRID software using oracle user.
Now you can try the same oracle user to install database software (using RUNINSTALLER and appropriate patches) beforehand the SWPM startup,and skip the prepiration step at all.

I prefere in your case to test that somewhere on empty system, but it should work well.
Loks like "preparation" and "DB refresh" only affected by the bug, at least it will be good in your case.

BR, Sergo.