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.
>
>
Received on Mon Aug 13 2001 - 17:16:05 CDT
