RE: sysdba

From: Matthew Parker <dimensional.dba_at_comcast.net>
Date: Thu, 16 Oct 2014 10:50:52 -0700
Message-ID: <002d01cfe969$c1ca9230$455fb690$_at_comcast.net>

It is because you are logged in as the OS user that started the database and is the security owner of the oracle executable.

The new model is not to allow users to become the oracle OS owner user, except during patching.      

From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Joshua Collier Sent: Thursday, October 16, 2014 10:42 AM To: oracle-l_at_freelists.org
Subject: sysdba  

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:50:52 CEST