Re: OEM: Can't connect to database as sysdba

Hi Mike,

To obtain the very powerful SYSDBA privilege, Oracle can use two methods of authentication, OS authentication or Oracle Password file authentication.

When using OS authentication, Oracle checks out your OS user details and verifies you are a member of the appropriate OS group (eg. dba in unix, ora_dba in windows). You have the correct OS authentication, you get sysdba.

However, on OEM you don't connect to the database via the server but via a client. Therefore Oracle has no way of authenticating you via the O/S method. Therefore it can only use Password authentication and check your db user to ensure it has been granted sysdba privileges and has been added to the password file. For remote authentication, you have no choice but to use password authentication.

Cheers

Richard

Mike Dwyer wrote:
>
> Do I have to do this even though I'm using 9.2? I didn't see anything
> in the documentation for OEM regarding this. But I'll give it a
> whirl.
>
> On Mon, 19 Aug 2002 11:34:20 +1000, Richard Foote
> <Richard.Foote_at_bigpond.com> wrote:
>
> >Hi ABC,
> >
> >Have you created a password file (orapwd utility) ?
> >
> >Have you granted to user sysdba privileges (grant sysdba to scott)
> >
> >Is your parameter remote_login_passwordfile=exclusive (or is it none) ?
> >
> >Do the above and you should be hunky dory.
> >
> >Cheers
> >
> >Richard
> >
> >abc_at_iom.com wrote:
> >>
> >> I'm using Oracle 9.2 on NT. I have OEM installed and am unable to
> >> connect up to databases as sysdba. I log into OEM as systman. I can
> >> see my nodes and the databases on those nodes. I can connect to these
> >> databases and look at the objects but I cannot connect as sysdba. For
> >> example, I can log in to a database as SYSTEM/manager using the
> >> setting "Normal". If I change it to SYSDBA, I get the message
> >> "Insufficient Privileges". I have set the prefered credentials for
> >> the node as well as the databases and set them to the proper
> >> passwords. I've set them to log in as sysdba, but to no avail.
> >>
> >> Any thoughts on this problem?
Received on Mon Aug 19 2002 - 02:56:08 CDT