These two steps (performed in reverse order) did the trick. Thanks.
Pete Sharman <psharman_at_us.oracle.com> wrote in message
news:37CEDAD5.B5504CAF_at_us.oracle.com...
> OK, there are two different issues here.
>
> 1. The insufficient privileges error means you need to connect as
internal to
> perform the grant.
>
> 2. The ORA-01994 is because the remote_login_paswordfile parameter is
either
> not set or set to SHARED in your init.ora. Change it to EXCLUSIVE, bounce
the
> database, and you should be OK.
>
> HTH.
>
> Pete
>
> John Haskins wrote:
>
> > Thanks for the reply, Pete. When I perform the "grant sysdba to <user>"
> > command as SYS, I get this:
> > ERROR at line 1:
> > ORA-01031: insufficient privileges
> >
> > That was on the NT server. Then I tried it on the Unix box, via svrmgrl
> > connected as internal. That produced this message:
> > ORA-01994: GRANT failed: cannot add users to public password file
> >
> > Even for Oracle, the masters of obtuse documentation, I'm surprised that
> > getting the basic ability to bounce a database via OEM is proving so
hard to
> > achieve.
> >
> > I appreciate any assistance you can provide in working past the above
> > problems.
> >
> > Pete Sharman <psharman_at_us.oracle.com> wrote in message
> > news:37CD4C6B.16FD6339_at_us.oracle.com...
> > > What error are you getting? Have you done a "grant sysdba to <user>"
as
> > SYS?
> > > Have a look at v$pwfile_users to see if it's succeeded. If not, send
us
> > any
> > > error message you might be getting on the grant.
> > >
> > > Pete
> > >
> > > John Haskins wrote:
> > >
> > > > John,
> > > > Thanks for the reply. The steps you detail here are all in the
docs,
> > and I
> > > > took all of them before posting my question to the group. The
problem
> > I'm
> > > > seeing is that there is no SYSDBA role to assign to myself. Any
> > thoughts?
> > > >
> > > > John van der Steen <steenjoh_at_iquip.nl> wrote in message
> > > > news:37CC1EB8.32A832DE_at_iquip.nl...
> > > > > Hi John,
> > > > >
> > > > > On your database server you have to create a password file and you
> > must
> > > > add a
> > > > > parameter in your init<sid>.ora:
> > > > >
> > > > > Enter the following line at the UNIX operating system prompt:
> > > > > orapwd file=$ORACLE_HOME/dbs/orapw$ORACLE_SID password=manager
> > > > >
> > > > > Then add to your init<sid>.ora:
> > > > > REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE
> > > > >
> > > > > restart database
> > > > >
> > > > > To remotely shutdown the database you need to have the SYSDBA
role,
> > > > > To startup also but you also must have a locally saved
init<sid>.ora
> > > > otherwise
> > > > > you won't be able to start an instance.
> > > > >
> > > > > Regards,
> > > > >
> > > > > John van der Steen
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > John Haskins wrote:
> > > > >
> > > > > > I'm setting up Oracle Enterprise Manager to control three
servers
> > under
> > > > my
> > > > > > pervue. I have them "found" in OEM, but cannot execute
> > shutdown/startup
> > > > > > because I cannot log in using the SYSDBA or SYSOPER role. When
I
> > try to
> > > > do
> > > > > > so, it tells me that the user/pw combination is invalid, even
though
> > it
> > > > is
> > > > > > the same one I use when loggin in for standard DBA duties.
> > > > > >
> > > > > > How do I make this work? Being able to bounce an instance
without
> > > > having to
> > > > > > go into the server room would be handy.
> > > > >
> > >
>
Received on Thu Sep 09 1999 - 12:32:00 CDT
