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

Hi John,
Here's the scenario assuming you are using the passwordfile mechanism. The remote_login_passwordfile init<sid>.ora parameter has three possible values
- none : the default, only internal has SYSDBA and SYSOPER privilege. (It's not a role, it's a privilege!)
- shared: internal and SYS have SYSDBA and SYSOPER   important note: if the password of SYS doesn't equal the internal password, SYS doesn't have privilige
(ran into that many, many times, again today) - exclusive: accounts designated by the user can have SYSDBA and SYSOPER privilege.
What you need evidently is either shared or exclusive. Personally I like to use a distinct account for OEM and SYSDBA purposes other than SYS. It's just too easy to guess. If you take the provisions outlined here and save your init<sid>.ora parameters to the OEM console using Instance Manager, you could bounce an instance 6000 miles away within a few whistles. No need to catch a plane.

Hth,

--
Sybrand Bakker, Oracle DBA

John Haskins <76054.334SPAMBEGONE_at_compuserve.com> wrote in message news:ijUy3.368$%m1.12990_at_dfiatx1-snr1.gtei.net...
> 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 Tue Aug 31 1999 - 13:10:23 CDT