Re: sysdba

  • From: Jack Applewhite <jack.applewhite@xxxxxxxxxxxxx>
  • To: "ian@xxxxxxxxxxxxxxxxx" <ian@xxxxxxxxxxxxxxxxx>, "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>, "Sweetser, Joe" <JSweetser@xxxxxxxx>
  • Date: Thu, 16 Oct 2014 18:57:17 +0000

+1 on that.
We include that line, along with a few others, in every 
$ORACLE_HOME/sqlplus/admin/glogin.sql file in our little world, so it gets 
executed every time we launch sqlplus.

FAR more than useful. Kept me from screwing up more than once.
----
Jack C. Applewhite - Database Administrator
Austin I.S.D. - MIS Department
512.414.9250 (wk)

________________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx <oracle-l-bounce@xxxxxxxxxxxxx> on behalf 
of Sweetser, Joe <JSweetser@xxxxxxxx>
Sent: Thursday, October 16, 2014 1:01 PM
To: ian@xxxxxxxxxxxxxxxxx; oracle-l@xxxxxxxxxxxxx
Subject: RE: sysdba

Another way to check/see who are connected is by using a login.sql file with 
this in it:  SET SQLPROMPT "_USER'@'_CONNECT_IDENTIFIER> "

I have found that useful at times.

-joe

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On 
Behalf Of MacGregor, Ian A.
Sent: Thursday, October 16, 2014 11:56 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: Re: sysdba

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@xxxxxxxxx> 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.

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


Confidentiality Notice: This email message, including all attachments, is for 
the sole use of the intended recipient(s) and may contain confidential student 
and/or employee information. Unauthorized use of disclosure is prohibited under 
the federal Family Educational Rights & Privacy Act (20 U.S.C. §1232g, 34 CFR 
Part 99, 19 TAC 247.2, Gov’t Code 552.023, Educ. Code 21.355, 29 CFR 
1630.14(b)(c)). If you are not the intended recipient, you may not use, 
disclose, copy or disseminate this information. Please call the sender 
immediately or reply by email and destroy all copies of the original message, 
including attachments.

Other related posts:

  1. Home
  2. oracle-l
  3. Archive
  4. 10-2014