on 09-15-2009 1:31 PM
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
it depends on what version your system was installed. if it was built on BASIS/WAS 6.20, then this is expected.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Check the following notes. It will be of great help to you.
Note 562863 - FAQ: Logon mechanisms
Note 361641 - Creating OPS$ users on UNIX
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
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.
User | Count |
---|---|
83 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.