Re: Cannot log in as SYSDBA or SYSOPER - why?

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 Wed Sep 01 1999 - 10:55:23 CDT