Re: connect as sysdba

It's the same mechanism with SYSOPER:

sys@ORA9I> drop user foo;

User dropped.

sys@ORA9I> grant create session, sysoper to foo identified by bar;

Grant succeeded.

sys@ORA9I> conn foo/bar as sysoper
Connected.
sys@ORA9I> show user
USER is "PUBLIC"
sys@ORA9I>



you'll always end up as PUBLIC, no matter what login/password you'll be
using.

Stefan



On 8/15/06, Reidy, Ron <Ron.Reidy@xxxxxxxxxxxxxxxxxx> wrote: 

Because when one connects as SYSDBA, they are SYS.

rr

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Joe Smith
Sent: Tuesday, August 15, 2006 7:42 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: connect as sysdba

List,

I have created a separate user, call it USER granted:

sql>grant connect, resource, dba to USER;

then

sql>grant sysdba to USER;

I can query v$pwfile_users  and see USER in there as sysdba.

So why is it whenyou connect as sysdba:

connect USER/pwd as sysdba

that when I type

sql>show user

it returns

user is "SYS"

?

thanks.

Can't you configure an account to act as sysdba , without using the
"SYS'
account?

thanks.

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's
FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

--
http://www.freelists.org/webpage/oracle-l



This electronic message transmission is a PRIVATE communication which
contains
information which may be confidential or privileged. The information is
intended
to be for the use of the individual or entity named above. If you are not
the
intended recipient, please be aware that any disclosure, copying,
distribution
or use of the contents of this information is prohibited. Please notify
the
sender  of the delivery error by replying to this message, or notify us by
telephone (877-633-2436, ext. 0), and then delete it from your system.

--
http://www.freelists.org/webpage/oracle-l



Other related posts: