Oracle is started with sidadm instead of orasid

[Former Member]

Hi, all.

We are running on oracle 11.2.0.2. After the upgrade from 10g, I noticed that oracle(like pmon, smon, etc) are started by sidadm instead of orasid. Do you know how to rectify the issue? I have a hard time tracing the startsap script, still trying though. Anybody ran into this issue?

By the way, the database did function properly though.

Thanks,

Jonathan.

[Former Member]

Hi, all.

That is what the oss note 206916 is suggesting ... the oracle process is running under "effective user" orasid even though ps -ef shows sideam. However, the OSS note did not tell us the command to see the RUSER. I have been searching on google and haven't seen much useful information. Can you please help?

Thanks,

Jonathan.

[former_member182307]

Hello,

I' ve found an interesting thread about this :

http://scn.sap.com/thread/819041

You should have a look at these answers from Joe BO :

I partly disagree. You have to keep in mind XPG4 ps and UNIX95 ps.
look at this on one of our systems:
16:50:50 hostx sh # ps -ef | grep ora_lgwr_FOO | grep -v grep
fooadm  4928     1  0  Mar 26  ?         4:54 ora_lgwr_FOO
16:51:00 hostx sh # UNIX95= ps -ef | grep ora_lgwr_FOO | grep -v grep
orafoo    4928     1  0  Mar 26  ?           04:54 ora_lgwr_FOO
16:51:08 hostx sh # 
regards

I disagree.
It's ok. We too are running SAP on Oracle and HP-UX IA 64.
You have to distinguish between real user id (sidadm in this case) and effective user id (orasid in this case case). For some reason HP's ps command by default shows real user id, that is the user id who started Oracle. Nevertheless effective user id is orasid.
There is a way how you can make ps to show the effective user id; I don't rember the details now. (But reading the manuals will help for sure.)
regards

Maybe this is your "problem".

and the last post says :

Thank you all, I was able to isolate this issue by adding the “oper” group which had to include the sidadm and orasid accounts.

Best regards,

Steve.

[Former Member]

It's interesting, thanks for the link Steve.

[Former Member]

Hi, Ratnajit.

Here is the output after I run dbstart with sidadm:

stld7501:oradxi 5> ps -ef|grep pmon

  dxiadm 11462     1  0 23:40:04 ?         0:00 ora_pmon_DXI

stld7501:oradxi 6> pwd

/oracle/DXI/11203_64/bin

stld7501:oradxi 7> ls -l oracle

-rwsr-s--x   1 oradxi     dba        553661464 Jun 18 17:41 oracle

If you run dbstart with sidadm on your system, do you see the orasid starting the pmon process?

Thanks,

Jonathan.

[Former Member]

@Ratnajit

There is no switch to ora<sid> while executing the startdb script.

There is a switch permission on oracle executables to switch the users in the group, script calls the user to execute the command (Ex: br* tools have 4775 permissions for switching)

@Jonathan

If it is all about only with PMON, yes pmon runs with sidadm by default (Script calls the executable with sidadm).

Regards,

Nick Loy

[Former Member]

Hi all

Thank you for all your posts. Here are the answers to your quesiton:

1) root.sh has already been run, same for saproot and oraroot

2) I have checked 583861 and 206916 already. I don't see any obvious error on the db, except the db is not started by orasid

3) Starting orasid and then run startsap works fine. But startsap is supposed to start the db too.

4) I don't know the syntax to see the RUSER field in the "ps" command as what note 206916 suggests. We are running on HPUX. Would you have any input?

Finally, I am wondering how does the startsap starts oracle with orasid. I am guessing at some point it has to switch to orasid and start oracle with sqlplus. But I couldn't find where the "switch" happens. Do you have any input?

Thanks,

Jonathan.

[former_member189725]

There is no switch to ora<sid> while executing the startdb script.

It is the permission of the oracle executable that starts the processes with the owner as ora<sid>.

Regards

Ratnajit

[Former Member]

after upgrade from 10g to 11g u change script .csh at oracle home directory

pls refere oracle upgrade note.

also see this script

dbenv.sh

.dbenv.csh

.dbenv_*.sh

  .dbenv_*.csh

Regards,

kaushal jani

[former_member182307]

Hi Jonathan,

This can be due to wrong users rights / ownership set on the Oracle binaries.

You should have a look at the following notes to fix this if needed :

583861 : shows how the user rights / ownership should be set.

592393 ( point 31 )  : states that this may not be a problem as long as the oracle binary has the right authorizations ( see note 583861 ).

You can also have a look at  Note 206916 - Oracle processes run under "incorrect" user .

In the end this may not be a real problem as long as the rights are set correctly.

Best regards,

Steve.

[Former Member]

Did you try this:

Start Oracle with orasid then start sap with sidadm...if it is working fine then the issue is with permissions or startup scripts.

Regards,

Nick Loy

[former_member189725]

Can you check the shell of your <sid>adm user .

Also check the startdb.log .

Regards

Ratnajit

[Former Member]

Hi Jonthan,

Did you executed root.sh script after installation?

Best regards,

Orkun Gedik

[former_member189725]

Check the permission of oracle executable under $ORACLE_HOME/bin

It should -rwsr-s--x .

login as ora<sid>

go to directory $ORACLE_HOME/bin

Execute

chmod 6751 oracle

Then restart the sap and oracle using stopsap and startsap.

Regards

Ratnajit

[Former Member]

Hi, Ratnajit.

The oracle executable is already -rwsr-s--x. Any other idea?

Thanks,

Jonathan.