Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Connect internal without password

Re: Connect internal without password

From: Pete Finnigan <pete_at_peterfinnigan.demon.co.uk>
Date: Tue, 14 Aug 2001 14:49:37 +0100
Message-ID: <zNXpLNAxxSe7Ewix@peterfinnigan.demon.co.uk>

Hi

you say it doesnt work when the user is in the Unix group dba?. I have had an issue the same on solaris 6 on an E4500 and oracle 8.0.6 where i got prompted for the password even when the non oracle user was in the group dba. I spoke to support at the time and they told me to make the dba group for this user the primary group and not a secondary group as i had it. Not sure why now what the reason was as it was a long time ago, and it wasnt the same versions, but you could try it

cheers

Pete Finnigan
www.pentest-limited.com

In article <FkYd7.100295$EP6.25482470_at_news1.rdc2.pa.home.com>, Robert Fazio <rfazio_at_home.com.nospam> writes
>Exactly that. If you are a member of the DBA group you are set. Just
>remember 9i says goodbye to internal.
>
>
>--
>Robert Fazio
>Senior Technical Analyst
>dbabob_at_yahoo.com
>
>"news" <martian_at_visi.com> wrote in message
>news:9KXd7.5480$x84.1768517_at_ruti.visi.com...
>> I'm sure someone knows the exact right answer, but I know in NT there is a
>> oracle dba group. All you have to do is add the user name to that group
 and
>> they don't need the internal password. I assume there is something
 simliar
>> in unix.
>>
>> MD
>>
>> "Mike Brodbelt" <m.brodbelt@_NO_SPAM_PLEASE_acu.ac.uk> wrote in message
>> news:3b780b44.29326419_at_news.claranews.com...
>> > Hi,
>> >
>> > Hoping for some help on this one... I need to be able to connect
>> > internal to Oracle using svrmgrl, and currently I can only do so when
>> > logged in as the oracle user.
>> >
>> > I have a (non-root) userid under which my backup software runs
>> > nightly. This user needs to have the privileges tp shut down the
>> > database instances before the backup job goes through, and to restart
>> > same after the backups have completed. The scripts that run the backup
>> > job call scripts to enumerate all the database instances listed in my
>> > oratab file, and shut down/restart them appropriately. They need to be
>> > able to connect internal to do this.
>> >
>> > I don't want to embed passwords in the scripts, and I can't su to the
>> > oracle user within the scripts (as this is a non-root user doing the
>> > backups).
>> >
>> > I've read various FAQ's and such, and have tried:-
>> >
>> > creating an ops$ user account for the user under which the backups
>> > run, and granting it the dba role.
>> >
>> > Adding the user to the Unix dba group.
>> >
>> > I'm still prompted for a password when I try to connect internal. I'd
>> > appreciate any help - I can't find any definive description of what
>> > Oracle used to decide whether a password is required for this
>> > process...
>> >
>> > FWIW, Oracle 8.1.5.0.0 on Solaris 7 on a sparc.
>> >
>> > Mike.
>>
>>
>
>
 

-- 
Pete Finnigan
Received on Tue Aug 14 2001 - 08:49:37 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US