Additional remote access privilages to ora<SID>

[Former Member]

Hi,

currently i can connect sucessfully to databse using ora<sid> user with sysdba privilages.

oraprd>sqlplus /nolog

SQL*Plus: Release 9.2.0.4.0 - Production on Sun Nov 12 14:05:33 2006

Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.

SQL> connect /as sysdba

Connected.

SQL>

but when i tried to connect remote login

SQL> connect orapms/prd90fcp@PRD

ERROR:

ORA-01017: invalid username/password; logon denied

SQL>

but to solve my problem , i need also to create oraprd user in internal db.and assign dba privilages.

Can we create this user ? is it will conflict with OPS$ORAPRD ?

any idea?

Thanks

Lisa

[lbreddemann]

Hi Lisa,

ok, let's lighten this up.

Are you really using OPS$ when doing a connect /as sysdba?

Nope you are not.

What happens with a "

/as sysdba

" or a "

/as sysoper

" connect ist the following:

1. Check if the OS-User issuing this connect clause is in the appropriate OS-group (dba or oper).

2. If yes, then:

IF "as sysdba" then connect as SYS

ELSEIF "as sysoper" then connect as PUBLIC

(feel free to check this by typing in show user after you used such a connect)

Well I said, it does not use the / at all... try to connect with

foo/bar as sysdba

.

As long as your current OS-user is in the dba group this will still work.

Ok, so you want to be able to do a "

/@PRD as sysdba

" ? Well that's perfectly possible. Set remote_os_authenticaten=TRUE and add the OS User you want to use for this into the dba-group. That's all.

Since usually the ora<sid> user does not have a password on the db, you will usually get the ORA-01017 error (beside, you can either use os-authenticated OR password for a specific db-user).

So to sum that up:

You may want to remote connect to your db as sysdba or sysoper, yes.

You don't want to connect as orapms remotely (what for?).

Anyhow, if you <b>are</b> the same OS-user on a different machine (let's say an application server, there's nothing more to do. It already works!).

Hope that clarifies a bit. A good overall presentation can be found here.

<a href="https://websmp110.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=562863&_NLANG=E">#562863 - FAQ: Logon mechanisms</a>

KR Lars

p.s.

do yourself a favour: install the current patchset 9.2.0.7 (or 9.2.0.8 if available yet on your platform). 9.2.0.4 is years old...

[Former Member]

Your OPS$ account is tied to the O.S. account with the same name -- in this case it looks like you have an account name oraprd as the ora<SID> user.

The orapms account (if you were to create it ) would be a different account.

These are 2 distinctly different accounts and will have different privileges (based on the Oracle role you assign the user).

Maybe a statement of the error/issue that you're trying to solve will help us better answer the question?

By the way, I hope that is not your real orapms password that you posted...