cancel
Showing results for 
Search instead for 
Did you mean: 

OPS$<SID>ADM where SID is SR3???

Former Member
0 Kudos

Hello,

I was upgrading my kernel last week and when i checked my dba_roles... i find an ops$sr3adm....and not a ops$<sid>adm...

Can somebody tell me why? 'Cause i had always see a ops$<SID>adm.

When you drop this user (SR3) and you create an other one with the good name and the same rights, it made an error.

Thanks in advance for helping me.

Florent

Accepted Solutions (1)

Accepted Solutions (1)

former_member204746
Active Contributor
0 Kudos

it depends on what version your system was installed. if it was built on BASIS/WAS 6.20, then this is expected.

Answers (1)

Answers (1)

Former Member
0 Kudos

Check the following notes. It will be of great help to you.

Note 562863 - FAQ: Logon mechanisms

Note 361641 - Creating OPS$ users on UNIX

Former Member
0 Kudos

I already read these notes and a lot about "ops$"...

It doesn't explain why there is an ops$sr3adm....i agree that you have a SAPSR3 user by default by this is not a SID...so why SR3 in the ops$???

And my system is NW2004 WAS 700.

former_member204746
Active Contributor
0 Kudos

why? because SAP decided so!

Former Member
0 Kudos

Ok but when you install don't you have to specify the SID and in the installation SAP or Oracle create the ops$ with the good sid?

former_member204746
Active Contributor
0 Kudos

SAP use SAPSR3 as the schema, whatever the SID you have chosen while installation.

There is a way to bypass this while installing. Personally, When asked for schema, I replaced SAPSR3 with SAPR3 (like the good old pre-4.6c systems).

unfortunately, once this is installed, it is really hard to change this.

Former Member
0 Kudos

Thanks for the response it's helping me to understand.

Former Member
0 Kudos

Hi Eric. I am seeing the same OPS$SR3ADM Oracle User as you had, in some of our newer JAVA Stack systems and I am wondering:

a) Where does it come from?

b) Why is there no OPS$<SID>ADM user?

c) What you did to resolve it.

We have no SID = SR3 anywhere in our environment.

Our unix id's are <sid>adm and ora<sid> as per standard.

We do have an OPS$ORA<SID> in the database, as expected.

Naturally, some things to not function as expected from our <sid>adm Unix user, since there is no corresponding OPS$ Oracle user.

Any thoughts are appreciated.

former_member204746
Active Contributor
0 Kudos

one quick answer:

since Netweaver '04, the default SAP schema is always SAPSR3 for ABAP stack, regardless of your SID... unless you changed that during installation.

for JAVA stack, default schema is SAPSR3DB.