Re: As oracle/dba still need internal passwd.. why?

From: Niall Litchfield <n-litchfield_at_audit-commission.gov.uk>
Date: Mon, 12 Feb 2001 12:05:23 -0000
Message-ID: <968ji4$116$1@soap.pipex.net>

I see no-one else has responded yet. in order to connect with sysdba privileges you are authenticated to oracle in one of two ways. Your system looks to be set up for password file authentication eg in your init.ora you have the line

remote_login_passwordfile=exclusive.

the alternative is to allow operating system authentication of sysdba users. this is done by setting

remote_login_passwordfile=none

My reading of the documentation suggests that the exclusive setting is preferred by oracle since you would then need to know two passwords (an os one and an oracle one) in order to perform sysdba type actions. This seems pretty reasonable to me.

--
Niall Litchfield
Oracle DBA
Audit Commission UK
"Tony Adolph" <tony.adolph_at_viaginterkom.de> wrote in message
news:95ugre$tbk$1_at_nnrp1.deja.com...


> Hello All,

>

> I am building a new database (Ora 8i) on Solaris 2.6.  I have used the

> db assistant to create the create scripts and I have set ORACLE_HOME

> and ORACLE_SID to the new values.  But I have a problem: from the

> oracle account (with dba group) I cannot connect internal using SVRMGRL

> without a password.  I used orapwd to create a password and it works.

> But why do I need the password when I'm logged in as oracle and am a

> member of the dba group?

>

> Any clues folks?

>

> Cheers

> Tony.

>

>

> Sent via Deja.com

> http://www.deja.com/

Received on Mon Feb 12 2001 - 06:05:23 CST