Re: sysdba

From: MacGregor, Ian A. <ian_at_slac.stanford.edu>
Date: Thu, 16 Oct 2014 17:56:24 +0000
Message-ID: <69903BAB-988D-46CE-97EB-A810FACA2507_at_slac.stanford.edu>

This has nothing to do with the user you created. You could just as well have tried

connect nonsense/monsense as sysdba

and would have been successfully connected.

When you installed Oracle, you indicated which OS groups could obtain roles. The current logged on system user belongs to the group which can obtain the sysdba role.

Ian MacGregor
SLAC National Accelerator Laboratory
On Oct 16, 2014, at 10:41 AM, Joshua Collier <jcoll1970_at_gmail.com> wrote:

> I must have missed something in my years as a DBA, such a basic thing as understanding this.
>
> 1. 11.2.4
> 2. logged on as oracle on the database host machine ( oracle home and binaries OS owner)
>
> sqlplus /nolog
> connect /as sysdba
> create user test identified by test;
> grant create session to test;
> connect test/test as sysdba;
> connected
>
> I am not sure I understand why this user can connect as sysdba without having been explicitly granted the SYSDBA power? Is it because I am logged on to the server as Oracle? Is there a machine setting to change this? documentation is proving sparse on this subject, or my googlefoo has been found lacking.
>
> thanks for your time,
>
> Josh C.

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

Received on Thu Oct 16 2014 - 19:56:24 CEST